DNS response history for ns2.nextdaywatches.com

ns2.nextdaywatches.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-24. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 1639 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.nextdaywatches.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

1639 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:12

All timestamps shown in UTC

Latest Resolved IP on Selected Date

65.98.52.178

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

Showing DNS history for 2026-08-24 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-24 14:12 639231765923559455
2229 ms 65.98.52.178
33 2026-08-24 13:55 639231755868832964
3 ms 65.98.52.178
32 2026-08-24 13:38 639231745628278877
2165 ms 65.98.52.178
31 2026-08-24 13:21 639231735407682062
3900 ms 65.98.52.178
30 2026-08-24 12:28 639231703815441688
5 ms 65.98.52.178
29 2026-08-24 12:12 639231693747052549
4 ms 65.98.52.178
28 2026-08-24 11:55 639231683712487276
3 ms 65.98.52.178
27 2026-08-24 11:38 639231673513573868
3838 ms 65.98.52.178
26 2026-08-24 10:45 639231641791249939
3 ms 65.98.52.178
25 2026-08-24 10:29 639231631866211033
4008 ms 65.98.52.178
24 2026-08-24 10:12 639231621644955316
3792 ms 65.98.52.178
23 2026-08-24 09:55 639231611478799259
3827 ms 65.98.52.178
22 2026-08-24 09:02 639231579923718211
2007 ms 65.98.52.178
21 2026-08-24 08:45 639231569810702936
2190 ms 65.98.52.178
20 2026-08-24 08:28 639231559762411619
3904 ms 65.98.52.178
19 2026-08-24 08:12 639231549663595407
4 ms 65.98.52.178
18 2026-08-24 07:18 639231518076817246
3 ms 65.98.52.178
17 2026-08-24 07:02 639231508078650885
4158 ms 65.98.52.178
16 2026-08-24 06:46 639231498210697093
3 ms 65.98.52.178
15 2026-08-24 06:29 639231488109699360
3801 ms 65.98.52.178
14 2026-08-24 05:36 639231456772510692
2008 ms 65.98.52.178
13 2026-08-24 05:20 639231447084631185
3672 ms 65.98.52.178
12 2026-08-24 05:04 639231437208519473
3 ms 65.98.52.178
11 2026-08-24 04:48 639231427209627490
3811 ms 65.98.52.178
10 2026-08-24 03:54 639231395791246644
3 ms 65.98.52.178
9 2026-08-24 03:38 639231386075551458
2 ms 65.98.52.178
8 2026-08-24 03:22 639231376208713791
5 ms 65.98.52.178
7 2026-08-24 03:06 639231366170589276
4 ms 65.98.52.178
6 2026-08-24 02:13 639231334732159368
2202 ms 65.98.52.178
5 2026-08-24 01:57 639231325035670078
3 ms 65.98.52.178
4 2026-08-24 01:40 639231315132253837
2 ms 65.98.52.178
3 2026-08-24 01:24 639231305014280808
4155 ms 65.98.52.178
2 2026-08-24 00:31 639231273779380675
2 ms 65.98.52.178
1 2026-08-24 00:15 639231264180839154
4 ms 65.98.52.178