DNS response history for ns2.doory.net

ns2.doory.net 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 37 DNS check records, 37 successful responses, 0 failed responses, and 255 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.doory.net.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

255 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

198.175.150.98

Most recently resolved hosting IP on selected date

Successful Responses

37

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.doory.net

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
37 2026-08-26 12:24 639233434974187439
27 ms 198.175.150.98
36 2026-08-26 12:06 639233424567558554
2031 ms 198.175.150.98
35 2026-08-26 11:49 639233414056832719
132 ms 198.175.150.98
34 2026-08-26 11:31 639233403515141099
15 ms 198.175.150.98
33 2026-08-26 10:36 639233370841350248
28 ms 198.175.150.98
32 2026-08-26 10:19 639233360361507238
39 ms 198.175.150.98
31 2026-08-26 10:02 639233350067824371
2058 ms 198.175.150.98
30 2026-08-26 09:45 639233339545274518
30 ms 198.175.150.98
29 2026-08-26 09:27 639233329214918079
24 ms 198.175.150.98
28 2026-08-26 09:10 639233318749762337
18 ms 198.175.150.98
27 2026-08-26 08:53 639233308387917838
114 ms 198.175.150.98
26 2026-08-26 08:35 639233297961740122
24 ms 198.175.150.98
25 2026-08-26 08:18 639233287487159094
45 ms 198.175.150.98
24 2026-08-26 08:00 639233276995531707
111 ms 198.175.150.98
23 2026-08-26 07:43 639233266521568229
45 ms 198.175.150.98
22 2026-08-26 07:25 639233256081047431
21 ms 198.175.150.98
21 2026-08-26 06:31 639233223620132921
32 ms 198.175.150.98
20 2026-08-26 06:14 639233213287814244
24 ms 198.175.150.98
19 2026-08-26 05:57 639233202925983161
115 ms 198.175.150.98
18 2026-08-26 05:40 639233192644780696
9 ms 198.175.150.98
17 2026-08-26 05:22 639233182401183833
45 ms 198.175.150.98
16 2026-08-26 05:05 639233172074181051
4 ms 198.175.150.98
15 2026-08-26 04:48 639233161808421455
9 ms 198.175.150.98
14 2026-08-26 04:31 639233151357344052
18 ms 198.175.150.98
13 2026-08-26 04:14 639233141034116946
2039 ms 198.175.150.98
12 2026-08-26 03:57 639233130828334142
47 ms 198.175.150.98
11 2026-08-26 03:39 639233120373450007
56 ms 198.175.150.98
10 2026-08-26 03:22 639233110066216193
38 ms 198.175.150.98
9 2026-08-26 02:29 639233078065410564
7 ms 198.175.150.98
8 2026-08-26 02:12 639233067787457832
48 ms 198.175.150.98
7 2026-08-26 01:54 639233057501801162
8 ms 198.175.150.98
6 2026-08-26 01:37 639233047089431703
40 ms 198.175.150.98
5 2026-08-26 01:20 639233036754790688
40 ms 198.175.150.98
4 2026-08-26 01:03 639233026412602472
28 ms 198.175.150.98
3 2026-08-26 00:45 639233016064066127
2047 ms 198.175.150.98
2 2026-08-26 00:28 639233005922655772
7 ms 198.175.150.98
1 2026-08-26 00:11 639232995672256907
9 ms 198.175.150.98