DNS response history for ns2.museumnews.kr

ns2.museumnews.kr 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-26. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 1150 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.museumnews.kr.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

1150 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:02

All timestamps shown in UTC

Latest Resolved IP on Selected Date

218.145.65.144

Most recently resolved hosting IP on selected date

Successful Responses

28

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.museumnews.kr

Showing DNS history for 2026-08-26 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
28 2026-08-26 09:02 639233308387917838
1511 ms 218.145.65.144
27 2026-08-26 08:45 639233297961740122
1060 ms 218.145.65.144
26 2026-08-26 08:28 639233287487159094
1269 ms 218.145.65.144
25 2026-08-26 08:10 639233276995531707
1168 ms 218.145.65.144
24 2026-08-26 07:53 639233266521568229
864 ms 218.145.65.144
23 2026-08-26 07:35 639233256081047431
1161 ms 218.145.65.144
22 2026-08-26 06:41 639233223620132921
1156 ms 218.145.65.144
21 2026-08-26 06:24 639233213287814244
1127 ms 218.145.65.144
20 2026-08-26 06:07 639233202925983161
1074 ms 218.145.65.144
19 2026-08-26 05:49 639233192644780696
1453 ms 218.145.65.144
18 2026-08-26 05:32 639233182401183833
1053 ms 218.145.65.144
17 2026-08-26 05:15 639233172074181051
1154 ms 218.145.65.144
16 2026-08-26 04:58 639233161808421455
871 ms 218.145.65.144
15 2026-08-26 04:41 639233151357344052
1164 ms 218.145.65.144
14 2026-08-26 04:23 639233141034116946
1137 ms 218.145.65.144
13 2026-08-26 04:06 639233130828334142
1438 ms 218.145.65.144
12 2026-08-26 03:49 639233120373450007
1147 ms 218.145.65.144
11 2026-08-26 03:32 639233110066216193
1141 ms 218.145.65.144
10 2026-08-26 02:38 639233078065410564
1013 ms 218.145.65.144
9 2026-08-26 02:21 639233067787457832
2544 ms 218.145.65.144
8 2026-08-26 02:04 639233057501801162
1134 ms 218.145.65.144
7 2026-08-26 01:47 639233047089431703
1153 ms 218.145.65.144
6 2026-08-26 01:30 639233036754790688
1146 ms 218.145.65.144
5 2026-08-26 01:12 639233026412602472
2 ms 218.145.65.144
4 2026-08-26 00:55 639233016064066127
1030 ms 218.145.65.144
3 2026-08-26 00:38 639233005922655772
1008 ms 218.145.65.144
2 2026-08-26 00:21 639232995672256907
1108 ms 218.145.65.144
1 2026-08-26 00:04 639232985300872416
1128 ms 218.145.65.144