DNS response history for ns2.syct.co.kr

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

35

Historical checks stored for this nameserver on selected date

Average Latency

646 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

211.63.185.168

Most recently resolved hosting IP on selected date

Successful Responses

35

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.syct.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
35 2026-08-26 11:40 639233403515141099
903 ms 211.63.185.168
34 2026-08-26 10:46 639233370841350248
889 ms 211.63.185.168
33 2026-08-26 10:28 639233360361507238
608 ms 211.63.185.168
32 2026-08-26 10:11 639233350067824371
755 ms 211.63.185.168
31 2026-08-26 09:54 639233339545274518
891 ms 211.63.185.168
30 2026-08-26 09:36 639233329214918079
612 ms 211.63.185.168
29 2026-08-26 09:19 639233318749762337
5 ms 211.63.185.168
28 2026-08-26 09:01 639233308387917838
951 ms 211.63.185.168
27 2026-08-26 08:44 639233297961740122
1128 ms 211.63.185.168
26 2026-08-26 08:27 639233287487159094
602 ms 211.63.185.168
25 2026-08-26 08:09 639233276995531707
762 ms 211.63.185.168
24 2026-08-26 07:52 639233266521568229
1152 ms 211.63.185.168
23 2026-08-26 07:34 639233256081047431
905 ms 211.63.185.168
22 2026-08-26 06:40 639233223620132921
588 ms 211.63.185.168
21 2026-08-26 06:23 639233213287814244
5 ms 211.63.185.168
20 2026-08-26 06:06 639233202925983161
896 ms 211.63.185.168
19 2026-08-26 05:49 639233192644780696
1071 ms 211.63.185.168
18 2026-08-26 05:31 639233182401183833
878 ms 211.63.185.168
17 2026-08-26 05:14 639233172074181051
4 ms 211.63.185.168
16 2026-08-26 04:57 639233161808421455
887 ms 211.63.185.168
15 2026-08-26 04:40 639233151357344052
4 ms 211.63.185.168
14 2026-08-26 04:23 639233141034116946
889 ms 211.63.185.168
13 2026-08-26 04:05 639233130828334142
595 ms 211.63.185.168
12 2026-08-26 03:48 639233120373450007
612 ms 211.63.185.168
11 2026-08-26 03:31 639233110066216193
896 ms 211.63.185.168
10 2026-08-26 02:38 639233078065410564
3 ms 211.63.185.168
9 2026-08-26 02:20 639233067787457832
832 ms 211.63.185.168
8 2026-08-26 02:03 639233057501801162
598 ms 211.63.185.168
7 2026-08-26 01:46 639233047089431703
2 ms 211.63.185.168
6 2026-08-26 01:29 639233036754790688
868 ms 211.63.185.168
5 2026-08-26 01:12 639233026412602472
876 ms 211.63.185.168
4 2026-08-26 00:54 639233016064066127
605 ms 211.63.185.168
3 2026-08-26 00:37 639233005922655772
587 ms 211.63.185.168
2 2026-08-26 00:20 639232995672256907
2 ms 211.63.185.168
1 2026-08-26 00:03 639232985300872416
754 ms 211.63.185.168