DNS response history for fitdns02.fitnessfactory.tw

fitdns02.fitnessfactory.tw is a DNS nameserver monitored by NameServerHistory. This page provides historical DNS response-time data, nameserver uptime signals, DNS latency observations, resolved IP history, successful response counts, failed response counts, and reliability indicators for this nameserver.

The selected UTC date is 2026-08-27. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 753 ms average response time. Current selected-date status: At least one successful DNS response was recorded for the selected date.

  • Use this report to investigate historical DNS uptime and nameserver reliability.
  • Compare DNS latency changes, failed DNS checks, and response behavior over time.
  • Review the latest resolved IP address and raw DNS check history for fitdns02.fitnessfactory.tw.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

753 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

60.248.59.75

Most recently resolved hosting IP on selected date

Successful Responses

35

Checks that returned a measurable response

Failed Responses

0

Checks with no response or no returned latency

Failure Rate

0%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for fitdns02.fitnessfactory.tw

Showing DNS history for 2026-08-27 UTC. Newest records appear first.

Latency bars are scaled to a maximum of 5000 ms for quick visual comparison.

# Query Time (UTC) Correlation ID Latency Response IP Address
35 2026-08-27 11:16 639234253963286387
4 ms 60.248.59.75
34 2026-08-27 10:59 639234243654907465
300 ms 60.248.59.75
33 2026-08-27 10:42 639234233269654413
3 ms 60.248.59.75
32 2026-08-27 10:25 639234222943951923
293 ms 60.248.59.75
31 2026-08-27 10:07 639234212558002823
295 ms 60.248.59.75
30 2026-08-27 09:50 639234202117531850
297 ms 60.248.59.75
29 2026-08-27 09:33 639234191649612722
599 ms 60.248.59.75
28 2026-08-27 09:15 639234181105879568
311 ms 60.248.59.75
27 2026-08-27 08:58 639234170713214496
310 ms 60.248.59.75
26 2026-08-27 08:40 639234160341037652
291 ms 60.248.59.75
25 2026-08-27 08:23 639234149799404224
606 ms 60.248.59.75
24 2026-08-27 08:05 639234139553286469
609 ms 60.248.59.75
23 2026-08-27 07:12 639234107183588293
297 ms 60.248.59.75
22 2026-08-27 06:55 639234096905435724
289 ms 60.248.59.75
21 2026-08-27 06:37 639234086579410775
296 ms 60.248.59.75
20 2026-08-27 06:20 639234076291157956
307 ms 60.248.59.75
19 2026-08-27 06:03 639234065981939454
310 ms 60.248.59.75
18 2026-08-27 05:46 639234055548642997
4663 ms 60.248.59.75
17 2026-08-27 05:28 639234045267979603
294 ms 60.248.59.75
16 2026-08-27 05:11 639234034999717463
609 ms 60.248.59.75
15 2026-08-27 04:54 639234024739225358
607 ms 60.248.59.75
14 2026-08-27 04:37 639234014311170162
307 ms 60.248.59.75
13 2026-08-27 04:20 639234003806017640
888 ms 60.248.59.75
12 2026-08-27 04:02 639233993356203030
299 ms 60.248.59.75
11 2026-08-27 03:09 639233961301716608
802 ms 60.248.59.75
10 2026-08-27 02:51 639233950834200647
308 ms 60.248.59.75
9 2026-08-27 02:34 639233940431849026
314 ms 60.248.59.75
8 2026-08-27 02:17 639233930110596398
4883 ms 60.248.59.75
7 2026-08-27 01:59 639233919705434540
320 ms 60.248.59.75
6 2026-08-27 01:42 639233909452807845
637 ms 60.248.59.75
5 2026-08-27 01:25 639233899096420820
4506 ms 60.248.59.75
4 2026-08-27 01:08 639233888707824939
295 ms 60.248.59.75
3 2026-08-27 00:50 639233878461203802
585 ms 60.248.59.75
2 2026-08-27 00:33 639233868060868209
308 ms 60.248.59.75
1 2026-08-27 00:16 639233857450922991
318 ms 60.248.59.75