DNS response history for ns2.dildns.com

ns2.dildns.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 29 DNS check records, 29 successful responses, 0 failed responses, and 537 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.dildns.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

537 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 12:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.157.83.3

Most recently resolved hosting IP on selected date

Successful Responses

29

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.dildns.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
29 2026-08-28 12:31 639235163898672622
142 ms 202.157.83.3
28 2026-08-28 11:38 639235132147470568
373 ms 202.157.83.3
27 2026-08-28 11:21 639235121907744088
194 ms 202.157.83.3
26 2026-08-28 11:04 639235111428014262
146 ms 202.157.83.3
25 2026-08-28 10:46 639235100921813626
357 ms 202.157.83.3
24 2026-08-28 09:52 639235068670703481
196 ms 202.157.83.3
23 2026-08-28 09:35 639235058337459445
214 ms 202.157.83.3
22 2026-08-28 09:18 639235047825109146
2011 ms 202.157.83.3
21 2026-08-28 09:00 639235037383229033
179 ms 202.157.83.3
20 2026-08-28 08:07 639235005619242711
143 ms 202.157.83.3
19 2026-08-28 07:50 639234995310346584
369 ms 202.157.83.3
18 2026-08-28 07:33 639234984946548933
357 ms 202.157.83.3
17 2026-08-28 07:16 639234974608077290
190 ms 202.157.83.3
16 2026-08-28 06:22 639234942529845595
2284 ms 202.157.83.3
15 2026-08-28 06:05 639234932259126627
311 ms 202.157.83.3
14 2026-08-28 05:48 639234921916735988
327 ms 202.157.83.3
13 2026-08-28 05:31 639234911470038027
366 ms 202.157.83.3
12 2026-08-28 04:37 639234879588411654
310 ms 202.157.83.3
11 2026-08-28 04:20 639234869341589104
274 ms 202.157.83.3
10 2026-08-28 04:03 639234859012216675
500 ms 202.157.83.3
9 2026-08-28 03:46 639234848695364934
343 ms 202.157.83.3
8 2026-08-28 02:53 639234816952458162
2315 ms 202.157.83.3
7 2026-08-28 02:36 639234806773081598
9 ms 202.157.83.3
6 2026-08-28 02:19 639234796382955255
182 ms 202.157.83.3
5 2026-08-28 02:01 639234786015782563
330 ms 202.157.83.3
4 2026-08-28 01:08 639234753811917646
322 ms 202.157.83.3
3 2026-08-28 00:51 639234743739767811
351 ms 202.157.83.3
2 2026-08-28 00:34 639234733372362811
135 ms 202.157.83.3
1 2026-08-28 00:16 639234723048550337
2350 ms 202.157.83.3