DNS response history for ns2.main-node.com

ns2.main-node.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 33 DNS check records, 33 successful responses, 0 failed responses, and 88 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.main-node.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

88 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

116.203.123.135

Most recently resolved hosting IP on selected date

Successful Responses

33

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.main-node.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
33 2026-08-24 13:42 639231755868832964
50 ms 116.203.123.135
32 2026-08-24 13:25 639231745628278877
17 ms 116.203.123.135
31 2026-08-24 13:08 639231735407682062
10 ms 116.203.123.135
30 2026-08-24 12:15 639231703815441688
36 ms 116.203.123.135
29 2026-08-24 11:58 639231693747052549
29 ms 116.203.123.135
28 2026-08-24 11:42 639231683712487276
54 ms 116.203.123.135
27 2026-08-24 11:25 639231673513573868
23 ms 116.203.123.135
26 2026-08-24 10:32 639231641791249939
20 ms 116.203.123.135
25 2026-08-24 10:15 639231631866211033
13 ms 116.203.123.135
24 2026-08-24 09:58 639231621644955316
31 ms 116.203.123.135
23 2026-08-24 09:41 639231611478799259
15 ms 116.203.123.135
22 2026-08-24 08:49 639231579923718211
24 ms 116.203.123.135
21 2026-08-24 08:32 639231569810702936
13 ms 116.203.123.135
20 2026-08-24 08:15 639231559762411619
110 ms 116.203.123.135
19 2026-08-24 07:58 639231549663595407
57 ms 116.203.123.135
18 2026-08-24 07:06 639231518076817246
15 ms 116.203.123.135
17 2026-08-24 06:49 639231508078650885
31 ms 116.203.123.135
16 2026-08-24 06:32 639231498210697093
10 ms 116.203.123.135
15 2026-08-24 06:16 639231488109699360
15 ms 116.203.123.135
14 2026-08-24 05:23 639231456772510692
6 ms 116.203.123.135
13 2026-08-24 05:07 639231447084631185
10 ms 116.203.123.135
12 2026-08-24 04:51 639231437208519473
40 ms 116.203.123.135
11 2026-08-24 04:34 639231427209627490
13 ms 116.203.123.135
10 2026-08-24 03:42 639231395791246644
9 ms 116.203.123.135
9 2026-08-24 03:26 639231386075551458
24 ms 116.203.123.135
8 2026-08-24 03:09 639231376208713791
41 ms 116.203.123.135
7 2026-08-24 02:52 639231366170589276
9 ms 116.203.123.135
6 2026-08-24 02:00 639231334732159368
2044 ms 116.203.123.135
5 2026-08-24 01:44 639231325035670078
31 ms 116.203.123.135
4 2026-08-24 01:27 639231315132253837
42 ms 116.203.123.135
3 2026-08-24 01:11 639231305014280808
11 ms 116.203.123.135
2 2026-08-24 00:18 639231273779380675
8 ms 116.203.123.135
1 2026-08-24 00:02 639231264180839154
49 ms 116.203.123.135