DNS response history for ns2.doodco.com

ns2.doodco.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-26. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 424 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.doodco.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

424 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

107.172.38.219

Most recently resolved hosting IP on selected date

Successful Responses

38

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.doodco.com

Showing DNS history for 2026-08-26 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
38 2026-08-26 12:31 639233434974187439
357 ms 107.172.38.219
37 2026-08-26 12:13 639233424567558554
235 ms 107.172.38.219
36 2026-08-26 11:56 639233414056832719
358 ms 107.172.38.219
35 2026-08-26 11:38 639233403515141099
247 ms 107.172.38.219
34 2026-08-26 10:44 639233370841350248
333 ms 107.172.38.219
33 2026-08-26 10:27 639233360361507238
232 ms 107.172.38.219
32 2026-08-26 10:09 639233350067824371
2244 ms 107.172.38.219
31 2026-08-26 09:52 639233339545274518
356 ms 107.172.38.219
30 2026-08-26 09:34 639233329214918079
357 ms 107.172.38.219
29 2026-08-26 09:17 639233318749762337
357 ms 107.172.38.219
28 2026-08-26 09:00 639233308387917838
237 ms 107.172.38.219
27 2026-08-26 08:43 639233297961740122
233 ms 107.172.38.219
26 2026-08-26 08:25 639233287487159094
363 ms 107.172.38.219
25 2026-08-26 08:08 639233276995531707
345 ms 107.172.38.219
24 2026-08-26 07:50 639233266521568229
246 ms 107.172.38.219
23 2026-08-26 07:33 639233256081047431
236 ms 107.172.38.219
22 2026-08-26 06:39 639233223620132921
235 ms 107.172.38.219
21 2026-08-26 06:21 639233213287814244
342 ms 107.172.38.219
20 2026-08-26 06:04 639233202925983161
3 ms 107.172.38.219
19 2026-08-26 05:47 639233192644780696
4 ms 107.172.38.219
18 2026-08-26 05:30 639233182401183833
2010 ms 107.172.38.219
17 2026-08-26 05:13 639233172074181051
236 ms 107.172.38.219
16 2026-08-26 04:55 639233161808421455
3 ms 107.172.38.219
15 2026-08-26 04:38 639233151357344052
338 ms 107.172.38.219
14 2026-08-26 04:21 639233141034116946
2 ms 107.172.38.219
13 2026-08-26 04:04 639233130828334142
233 ms 107.172.38.219
12 2026-08-26 03:47 639233120373450007
374 ms 107.172.38.219
11 2026-08-26 03:29 639233110066216193
2277 ms 107.172.38.219
10 2026-08-26 02:36 639233078065410564
369 ms 107.172.38.219
9 2026-08-26 02:19 639233067787457832
351 ms 107.172.38.219
8 2026-08-26 02:02 639233057501801162
350 ms 107.172.38.219
7 2026-08-26 01:45 639233047089431703
361 ms 107.172.38.219
6 2026-08-26 01:27 639233036754790688
237 ms 107.172.38.219
5 2026-08-26 01:10 639233026412602472
285 ms 107.172.38.219
4 2026-08-26 00:53 639233016064066127
305 ms 107.172.38.219
3 2026-08-26 00:36 639233005922655772
358 ms 107.172.38.219
2 2026-08-26 00:18 639232995672256907
355 ms 107.172.38.219
1 2026-08-26 00:01 639232985300872416
351 ms 107.172.38.219