DNS response history for ns2.sync.co.kr

ns2.sync.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 33 DNS check records, 33 successful responses, 0 failed responses, and 1108 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.sync.co.kr.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

1108 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:29

All timestamps shown in UTC

Latest Resolved IP on Selected Date

121.78.127.249

Most recently resolved hosting IP on selected date

Successful Responses

33

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.sync.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
33 2026-08-26 10:29 639233360361507238
1087 ms 121.78.127.249
32 2026-08-26 10:11 639233350067824371
1057 ms 121.78.127.249
31 2026-08-26 09:54 639233339545274518
2 ms 121.78.127.249
30 2026-08-26 09:36 639233329214918079
5 ms 121.78.127.249
29 2026-08-26 09:19 639233318749762337
20 ms 121.78.127.249
28 2026-08-26 09:02 639233308387917838
1632 ms 121.78.127.249
27 2026-08-26 08:44 639233297961740122
1099 ms 121.78.127.249
26 2026-08-26 08:27 639233287487159094
3834 ms 121.78.127.249
25 2026-08-26 08:10 639233276995531707
1614 ms 121.78.127.249
24 2026-08-26 07:52 639233266521568229
487 ms 121.78.127.249
23 2026-08-26 07:35 639233256081047431
436 ms 121.78.127.249
22 2026-08-26 06:40 639233223620132921
454 ms 121.78.127.249
21 2026-08-26 06:23 639233213287814244
439 ms 121.78.127.249
20 2026-08-26 06:06 639233202925983161
458 ms 121.78.127.249
19 2026-08-26 05:49 639233192644780696
4 ms 121.78.127.249
18 2026-08-26 05:32 639233182401183833
2300 ms 121.78.127.249
17 2026-08-26 05:15 639233172074181051
4 ms 121.78.127.249
16 2026-08-26 04:57 639233161808421455
1540 ms 121.78.127.249
15 2026-08-26 04:40 639233151357344052
512 ms 121.78.127.249
14 2026-08-26 04:23 639233141034116946
1633 ms 121.78.127.249
13 2026-08-26 04:06 639233130828334142
1044 ms 121.78.127.249
12 2026-08-26 03:48 639233120373450007
425 ms 121.78.127.249
11 2026-08-26 03:31 639233110066216193
1039 ms 121.78.127.249
10 2026-08-26 02:38 639233078065410564
4587 ms 121.78.127.249
9 2026-08-26 02:21 639233067787457832
1650 ms 121.78.127.249
8 2026-08-26 02:03 639233057501801162
426 ms 121.78.127.249
7 2026-08-26 01:46 639233047089431703
431 ms 121.78.127.249
6 2026-08-26 01:29 639233036754790688
431 ms 121.78.127.249
5 2026-08-26 01:12 639233026412602472
427 ms 121.78.127.249
4 2026-08-26 00:54 639233016064066127
1658 ms 121.78.127.249
3 2026-08-26 00:37 639233005922655772
1616 ms 121.78.127.249
2 2026-08-26 00:20 639232995672256907
436 ms 121.78.127.249
1 2026-08-26 00:03 639232985300872416
3785 ms 121.78.127.249