DNS response history for ns2.maincube.net

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

34

Historical checks stored for this nameserver on selected date

Average Latency

45 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

77.78.99.45

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

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:03 639231765923559455
23 ms 77.78.99.45
33 2026-08-24 13:46 639231755868832964
50 ms 77.78.99.45
32 2026-08-24 13:29 639231745628278877
53 ms 77.78.99.45
31 2026-08-24 13:12 639231735407682062
33 ms 77.78.99.45
30 2026-08-24 12:19 639231703815441688
12 ms 77.78.99.45
29 2026-08-24 12:02 639231693747052549
40 ms 77.78.99.45
28 2026-08-24 11:45 639231683712487276
44 ms 77.78.99.45
27 2026-08-24 11:29 639231673513573868
7 ms 77.78.99.45
26 2026-08-24 10:36 639231641791249939
36 ms 77.78.99.45
25 2026-08-24 10:19 639231631866211033
36 ms 77.78.99.45
24 2026-08-24 10:02 639231621644955316
47 ms 77.78.99.45
23 2026-08-24 09:45 639231611478799259
186 ms 77.78.99.45
22 2026-08-24 08:53 639231579923718211
6 ms 77.78.99.45
21 2026-08-24 08:36 639231569810702936
35 ms 77.78.99.45
20 2026-08-24 08:19 639231559762411619
4 ms 77.78.99.45
19 2026-08-24 08:02 639231549663595407
7 ms 77.78.99.45
18 2026-08-24 07:10 639231518076817246
8 ms 77.78.99.45
17 2026-08-24 06:53 639231508078650885
112 ms 77.78.99.45
16 2026-08-24 06:36 639231498210697093
25 ms 77.78.99.45
15 2026-08-24 06:20 639231488109699360
51 ms 77.78.99.45
14 2026-08-24 05:27 639231456772510692
32 ms 77.78.99.45
13 2026-08-24 05:11 639231447084631185
3 ms 77.78.99.45
12 2026-08-24 04:55 639231437208519473
5 ms 77.78.99.45
11 2026-08-24 04:38 639231427209627490
41 ms 77.78.99.45
10 2026-08-24 03:46 639231395791246644
16 ms 77.78.99.45
9 2026-08-24 03:29 639231386075551458
36 ms 77.78.99.45
8 2026-08-24 03:13 639231376208713791
299 ms 77.78.99.45
7 2026-08-24 02:56 639231366170589276
38 ms 77.78.99.45
6 2026-08-24 02:04 639231334732159368
11 ms 77.78.99.45
5 2026-08-24 01:48 639231325035670078
28 ms 77.78.99.45
4 2026-08-24 01:31 639231315132253837
5 ms 77.78.99.45
3 2026-08-24 01:14 639231305014280808
2 ms 77.78.99.45
2 2026-08-24 00:22 639231273779380675
37 ms 77.78.99.45
1 2026-08-24 00:06 639231264180839154
153 ms 77.78.99.45