DNS response history for ns2.darrylpolo.tech

ns2.darrylpolo.tech 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 34 DNS check records, 34 successful responses, 0 failed responses, and 511 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.darrylpolo.tech.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

511 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 14:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.81.250.230

Most recently resolved hosting IP on selected date

Successful Responses

34

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.darrylpolo.tech

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
34 2026-08-28 14:31 639235238225955920
192 ms 51.81.250.230
33 2026-08-28 14:14 639235227727862105
333 ms 51.81.250.230
32 2026-08-28 13:20 639235195230848570
343 ms 51.81.250.230
31 2026-08-28 13:02 639235184840503274
332 ms 51.81.250.230
30 2026-08-28 12:45 639235174453894956
328 ms 51.81.250.230
29 2026-08-28 12:27 639235163898672622
357 ms 51.81.250.230
28 2026-08-28 11:34 639235132147470568
353 ms 51.81.250.230
27 2026-08-28 11:17 639235121907744088
2230 ms 51.81.250.230
26 2026-08-28 11:00 639235111428014262
202 ms 51.81.250.230
25 2026-08-28 10:42 639235100921813626
347 ms 51.81.250.230
24 2026-08-28 09:49 639235068670703481
343 ms 51.81.250.230
23 2026-08-28 09:31 639235058337459445
358 ms 51.81.250.230
22 2026-08-28 09:14 639235047825109146
337 ms 51.81.250.230
21 2026-08-28 08:56 639235037383229033
365 ms 51.81.250.230
20 2026-08-28 08:03 639235005619242711
324 ms 51.81.250.230
19 2026-08-28 07:47 639234995310346584
2174 ms 51.81.250.230
18 2026-08-28 07:29 639234984946548933
333 ms 51.81.250.230
17 2026-08-28 07:12 639234974608077290
362 ms 51.81.250.230
16 2026-08-28 06:18 639234942529845595
10 ms 51.81.250.230
15 2026-08-28 06:01 639234932259126627
2175 ms 51.81.250.230
14 2026-08-28 05:44 639234921916735988
187 ms 51.81.250.230
13 2026-08-28 05:27 639234911470038027
335 ms 51.81.250.230
12 2026-08-28 04:34 639234879588411654
327 ms 51.81.250.230
11 2026-08-28 04:16 639234869341589104
332 ms 51.81.250.230
10 2026-08-28 03:59 639234859012216675
2164 ms 51.81.250.230
9 2026-08-28 03:42 639234848695364934
328 ms 51.81.250.230
8 2026-08-28 02:49 639234816952458162
363 ms 51.81.250.230
7 2026-08-28 02:32 639234806773081598
2 ms 51.81.250.230
6 2026-08-28 02:15 639234796382955255
4 ms 51.81.250.230
5 2026-08-28 01:57 639234786015782563
327 ms 51.81.250.230
4 2026-08-28 01:04 639234753811917646
332 ms 51.81.250.230
3 2026-08-28 00:47 639234743739767811
354 ms 51.81.250.230
2 2026-08-28 00:30 639234733372362811
181 ms 51.81.250.230
1 2026-08-28 00:13 639234723048550337
346 ms 51.81.250.230