DNS response history for ns2.dingfod.com

ns2.dingfod.com 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-28. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 621 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 ns2.dingfod.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

621 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 14:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.180.146.146

Most recently resolved hosting IP on selected date

Successful Responses

33

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 ns2.dingfod.com

Showing DNS history for 2026-08-28 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
33 2026-08-28 14:20 639235227727862105
506 ms 66.180.146.146
32 2026-08-28 13:26 639235195230848570
493 ms 66.180.146.146
31 2026-08-28 13:09 639235184840503274
489 ms 66.180.146.146
30 2026-08-28 12:52 639235174453894956
2841 ms 66.180.146.146
29 2026-08-28 12:34 639235163898672622
491 ms 66.180.146.146
28 2026-08-28 11:41 639235132147470568
3 ms 66.180.146.146
27 2026-08-28 11:24 639235121907744088
488 ms 66.180.146.146
26 2026-08-28 11:07 639235111428014262
502 ms 66.180.146.146
25 2026-08-28 10:49 639235100921813626
485 ms 66.180.146.146
24 2026-08-28 09:55 639235068670703481
10 ms 66.180.146.146
23 2026-08-28 09:38 639235058337459445
511 ms 66.180.146.146
22 2026-08-28 09:21 639235047825109146
491 ms 66.180.146.146
21 2026-08-28 09:03 639235037383229033
487 ms 66.180.146.146
20 2026-08-28 08:10 639235005619242711
4 ms 66.180.146.146
19 2026-08-28 07:53 639234995310346584
490 ms 66.180.146.146
18 2026-08-28 07:36 639234984946548933
492 ms 66.180.146.146
17 2026-08-28 07:18 639234974608077290
503 ms 66.180.146.146
16 2026-08-28 06:25 639234942529845595
488 ms 66.180.146.146
15 2026-08-28 06:08 639234932259126627
500 ms 66.180.146.146
14 2026-08-28 05:51 639234921916735988
3 ms 66.180.146.146
13 2026-08-28 05:33 639234911470038027
522 ms 66.180.146.146
12 2026-08-28 04:40 639234879588411654
2424 ms 66.180.146.146
11 2026-08-28 04:23 639234869341589104
1066 ms 66.180.146.146
10 2026-08-28 04:06 639234859012216675
502 ms 66.180.146.146
9 2026-08-28 03:48 639234848695364934
494 ms 66.180.146.146
8 2026-08-28 02:55 639234816952458162
1653 ms 66.180.146.146
7 2026-08-28 02:39 639234806773081598
509 ms 66.180.146.146
6 2026-08-28 02:21 639234796382955255
509 ms 66.180.146.146
5 2026-08-28 02:04 639234786015782563
505 ms 66.180.146.146
4 2026-08-28 01:10 639234753811917646
514 ms 66.180.146.146
3 2026-08-28 00:53 639234743739767811
506 ms 66.180.146.146
2 2026-08-28 00:36 639234733372362811
512 ms 66.180.146.146
1 2026-08-28 00:19 639234723048550337
512 ms 66.180.146.146