DNS response history for ns1.megapluskorea.com

ns1.megapluskorea.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-30. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 902 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 ns1.megapluskorea.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

902 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 10:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

49.247.9.37

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 ns1.megapluskorea.com

Showing DNS history for 2026-08-30 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-30 10:31 639236817708615077
893 ms 49.247.9.37
31 2026-08-30 09:37 639236785770651804
878 ms 49.247.9.37
30 2026-08-30 09:21 639236775820686373
1126 ms 49.247.9.37
29 2026-08-30 09:04 639236765768339082
866 ms 49.247.9.37
28 2026-08-30 08:47 639236755602384085
855 ms 49.247.9.37
27 2026-08-30 08:30 639236745600094925
884 ms 49.247.9.37
26 2026-08-30 08:14 639236735311262753
878 ms 49.247.9.37
25 2026-08-30 07:56 639236724996745235
566 ms 49.247.9.37
24 2026-08-30 07:39 639236714839899761
799 ms 49.247.9.37
23 2026-08-30 07:22 639236704748431488
883 ms 49.247.9.37
22 2026-08-30 07:06 639236694430128550
854 ms 49.247.9.37
21 2026-08-30 06:48 639236684143292417
865 ms 49.247.9.37
20 2026-08-30 06:31 639236673972499943
821 ms 49.247.9.37
19 2026-08-30 05:38 639236642126522802
867 ms 49.247.9.37
18 2026-08-30 05:21 639236632183518198
826 ms 49.247.9.37
17 2026-08-30 05:05 639236622289312589
804 ms 49.247.9.37
16 2026-08-30 04:48 639236612490676525
866 ms 49.247.9.37
15 2026-08-30 04:32 639236602582494852
541 ms 49.247.9.37
14 2026-08-30 04:15 639236592511706469
870 ms 49.247.9.37
13 2026-08-30 03:58 639236582441006869
548 ms 49.247.9.37
12 2026-08-30 03:42 639236572478785089
878 ms 49.247.9.37
11 2026-08-30 03:25 639236562556749999
892 ms 49.247.9.37
10 2026-08-30 03:09 639236552353482281
867 ms 49.247.9.37
9 2026-08-30 02:51 639236542188881607
849 ms 49.247.9.37
8 2026-08-30 02:34 639236531885440105
866 ms 49.247.9.37
7 2026-08-30 01:41 639236499922985383
872 ms 49.247.9.37
6 2026-08-30 01:24 639236489713594431
893 ms 49.247.9.37
5 2026-08-30 01:07 639236479750443901
2813 ms 49.247.9.37
4 2026-08-30 00:51 639236469719936375
860 ms 49.247.9.37
3 2026-08-30 00:34 639236459579244885
838 ms 49.247.9.37
2 2026-08-30 00:17 639236449582837549
878 ms 49.247.9.37
1 2026-08-30 00:00 639236439461653110
875 ms 49.247.9.37