DNS response history for ns2.migannews.com

ns2.migannews.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 32 DNS check records, 32 successful responses, 0 failed responses, and 303 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.migannews.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

303 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:28

All timestamps shown in UTC

Latest Resolved IP on Selected Date

77.68.20.251

Most recently resolved hosting IP on selected date

Successful Responses

32

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.migannews.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
32 2026-08-24 13:28 639231745628278877
36 ms 77.68.20.251
31 2026-08-24 13:11 639231735407682062
71 ms 77.68.20.251
30 2026-08-24 12:18 639231703815441688
32 ms 77.68.20.251
29 2026-08-24 12:02 639231693747052549
57 ms 77.68.20.251
28 2026-08-24 11:45 639231683712487276
71 ms 77.68.20.251
27 2026-08-24 11:28 639231673513573868
73 ms 77.68.20.251
26 2026-08-24 10:35 639231641791249939
61 ms 77.68.20.251
25 2026-08-24 10:19 639231631866211033
105 ms 77.68.20.251
24 2026-08-24 10:02 639231621644955316
52 ms 77.68.20.251
23 2026-08-24 09:45 639231611478799259
72 ms 77.68.20.251
22 2026-08-24 08:52 639231579923718211
32 ms 77.68.20.251
21 2026-08-24 08:35 639231569810702936
61 ms 77.68.20.251
20 2026-08-24 08:18 639231559762411619
37 ms 77.68.20.251
19 2026-08-24 08:02 639231549663595407
216 ms 77.68.20.251
18 2026-08-24 07:09 639231518076817246
4 ms 77.68.20.251
17 2026-08-24 06:52 639231508078650885
65 ms 77.68.20.251
16 2026-08-24 06:36 639231498210697093
32 ms 77.68.20.251
15 2026-08-24 06:19 639231488109699360
63 ms 77.68.20.251
14 2026-08-24 05:27 639231456772510692
60 ms 77.68.20.251
13 2026-08-24 05:11 639231447084631185
2021 ms 77.68.20.251
12 2026-08-24 04:54 639231437208519473
42 ms 77.68.20.251
11 2026-08-24 04:37 639231427209627490
77 ms 77.68.20.251
10 2026-08-24 03:45 639231395791246644
13 ms 77.68.20.251
9 2026-08-24 03:29 639231386075551458
68 ms 77.68.20.251
8 2026-08-24 03:13 639231376208713791
2007 ms 77.68.20.251
7 2026-08-24 02:56 639231366170589276
2071 ms 77.68.20.251
6 2026-08-24 02:03 639231334732159368
8 ms 77.68.20.251
5 2026-08-24 01:47 639231325035670078
22 ms 77.68.20.251
4 2026-08-24 01:31 639231315132253837
88 ms 77.68.20.251
3 2026-08-24 01:14 639231305014280808
2035 ms 77.68.20.251
2 2026-08-24 00:22 639231273779380675
33 ms 77.68.20.251
1 2026-08-24 00:06 639231264180839154
3 ms 77.68.20.251