DNS response history for ns2nd.seoul.co.kr

ns2nd.seoul.co.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 37 DNS check records, 37 successful responses, 0 failed responses, and 431 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 ns2nd.seoul.co.kr.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

431 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.98.140.150

Most recently resolved hosting IP on selected date

Successful Responses

37

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 ns2nd.seoul.co.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
37 2026-08-26 12:14 639233424567558554
252 ms 210.98.140.150
36 2026-08-26 11:57 639233414056832719
285 ms 210.98.140.150
35 2026-08-26 11:39 639233403515141099
307 ms 210.98.140.150
34 2026-08-26 10:45 639233370841350248
2286 ms 210.98.140.150
33 2026-08-26 10:27 639233360361507238
285 ms 210.98.140.150
32 2026-08-26 10:10 639233350067824371
284 ms 210.98.140.150
31 2026-08-26 09:53 639233339545274518
296 ms 210.98.140.150
30 2026-08-26 09:35 639233329214918079
579 ms 210.98.140.150
29 2026-08-26 09:18 639233318749762337
295 ms 210.98.140.150
28 2026-08-26 09:01 639233308387917838
294 ms 210.98.140.150
27 2026-08-26 08:43 639233297961740122
576 ms 210.98.140.150
26 2026-08-26 08:26 639233287487159094
285 ms 210.98.140.150
25 2026-08-26 08:08 639233276995531707
281 ms 210.98.140.150
24 2026-08-26 07:51 639233266521568229
570 ms 210.98.140.150
23 2026-08-26 07:33 639233256081047431
310 ms 210.98.140.150
22 2026-08-26 06:39 639233223620132921
289 ms 210.98.140.150
21 2026-08-26 06:22 639233213287814244
299 ms 210.98.140.150
20 2026-08-26 06:05 639233202925983161
293 ms 210.98.140.150
19 2026-08-26 05:48 639233192644780696
611 ms 210.98.140.150
18 2026-08-26 05:30 639233182401183833
589 ms 210.98.140.150
17 2026-08-26 05:13 639233172074181051
281 ms 210.98.140.150
16 2026-08-26 04:56 639233161808421455
584 ms 210.98.140.150
15 2026-08-26 04:39 639233151357344052
312 ms 210.98.140.150
14 2026-08-26 04:22 639233141034116946
590 ms 210.98.140.150
13 2026-08-26 04:04 639233130828334142
594 ms 210.98.140.150
12 2026-08-26 03:47 639233120373450007
301 ms 210.98.140.150
11 2026-08-26 03:30 639233110066216193
284 ms 210.98.140.150
10 2026-08-26 02:37 639233078065410564
259 ms 210.98.140.150
9 2026-08-26 02:20 639233067787457832
574 ms 210.98.140.150
8 2026-08-26 02:02 639233057501801162
616 ms 210.98.140.150
7 2026-08-26 01:45 639233047089431703
298 ms 210.98.140.150
6 2026-08-26 01:28 639233036754790688
221 ms 210.98.140.150
5 2026-08-26 01:11 639233026412602472
292 ms 210.98.140.150
4 2026-08-26 00:53 639233016064066127
602 ms 210.98.140.150
3 2026-08-26 00:36 639233005922655772
312 ms 210.98.140.150
2 2026-08-26 00:19 639232995672256907
279 ms 210.98.140.150
1 2026-08-26 00:02 639232985300872416
286 ms 210.98.140.150