DNS response history for ns2.metro.seoul.kr

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

39

Historical checks stored for this nameserver on selected date

Average Latency

648 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 16:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

115.84.166.9

Most recently resolved hosting IP on selected date

Successful Responses

39

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.metro.seoul.kr

Showing DNS history for 2026-08-28 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
39 2026-08-28 16:40 639235312230592801
4 ms 115.84.166.9
38 2026-08-28 16:23 639235301738139314
630 ms 115.84.166.9
37 2026-08-28 16:05 639235291168160936
602 ms 115.84.166.9
36 2026-08-28 15:11 639235258803654519
625 ms 115.84.166.9
35 2026-08-28 14:54 639235248596087996
617 ms 115.84.166.9
34 2026-08-28 14:37 639235238225955920
620 ms 115.84.166.9
33 2026-08-28 14:19 639235227727862105
627 ms 115.84.166.9
32 2026-08-28 13:25 639235195230848570
636 ms 115.84.166.9
31 2026-08-28 13:08 639235184840503274
603 ms 115.84.166.9
30 2026-08-28 12:51 639235174453894956
635 ms 115.84.166.9
29 2026-08-28 12:33 639235163898672622
620 ms 115.84.166.9
28 2026-08-28 11:40 639235132147470568
637 ms 115.84.166.9
27 2026-08-28 11:23 639235121907744088
598 ms 115.84.166.9
26 2026-08-28 11:06 639235111428014262
618 ms 115.84.166.9
25 2026-08-28 10:48 639235100921813626
304 ms 115.84.166.9
24 2026-08-28 09:54 639235068670703481
616 ms 115.84.166.9
23 2026-08-28 09:37 639235058337459445
593 ms 115.84.166.9
22 2026-08-28 09:20 639235047825109146
625 ms 115.84.166.9
21 2026-08-28 09:02 639235037383229033
614 ms 115.84.166.9
20 2026-08-28 08:09 639235005619242711
666 ms 115.84.166.9
19 2026-08-28 07:52 639234995310346584
2007 ms 115.84.166.9
18 2026-08-28 07:35 639234984946548933
12 ms 115.84.166.9
17 2026-08-28 07:17 639234974608077290
3 ms 115.84.166.9
16 2026-08-28 06:24 639234942529845595
637 ms 115.84.166.9
15 2026-08-28 06:07 639234932259126627
625 ms 115.84.166.9
14 2026-08-28 05:50 639234921916735988
599 ms 115.84.166.9
13 2026-08-28 05:32 639234911470038027
615 ms 115.84.166.9
12 2026-08-28 04:39 639234879588411654
608 ms 115.84.166.9
11 2026-08-28 04:22 639234869341589104
2009 ms 115.84.166.9
10 2026-08-28 04:05 639234859012216675
625 ms 115.84.166.9
9 2026-08-28 03:48 639234848695364934
896 ms 115.84.166.9
8 2026-08-28 02:55 639234816952458162
608 ms 115.84.166.9
7 2026-08-28 02:38 639234806773081598
610 ms 115.84.166.9
6 2026-08-28 02:21 639234796382955255
625 ms 115.84.166.9
5 2026-08-28 02:03 639234786015782563
637 ms 115.84.166.9
4 2026-08-28 01:10 639234753811917646
598 ms 115.84.166.9
3 2026-08-28 00:52 639234743739767811
831 ms 115.84.166.9
2 2026-08-28 00:36 639234733372362811
620 ms 115.84.166.9
1 2026-08-28 00:18 639234723048550337
613 ms 115.84.166.9