DNS response history for ns2.sysauto.co.kr

ns2.sysauto.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-29. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 659 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.sysauto.co.kr.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

659 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-29 10:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

49.247.135.69

Most recently resolved hosting IP on selected date

Successful Responses

30

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.sysauto.co.kr

Showing DNS history for 2026-08-29 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
30 2026-08-29 10:51 639235966864596836
523 ms 49.247.135.69
29 2026-08-29 10:34 639235956590882003
530 ms 49.247.135.69
28 2026-08-29 09:41 639235924465736791
534 ms 49.247.135.69
27 2026-08-29 09:24 639235914430611197
502 ms 49.247.135.69
26 2026-08-29 09:07 639235904343784853
538 ms 49.247.135.69
25 2026-08-29 08:50 639235894201078068
522 ms 49.247.135.69
24 2026-08-29 08:33 639235884233447452
1457 ms 49.247.135.69
23 2026-08-29 08:17 639235874142207309
537 ms 49.247.135.69
22 2026-08-29 08:00 639235863974652466
480 ms 49.247.135.69
21 2026-08-29 07:43 639235853716243436
1008 ms 49.247.135.69
20 2026-08-29 07:26 639235843614494759
550 ms 49.247.135.69
19 2026-08-29 07:09 639235833401459551
277 ms 49.247.135.69
18 2026-08-29 06:52 639235823220464528
531 ms 49.247.135.69
17 2026-08-29 06:35 639235812997510905
530 ms 49.247.135.69
16 2026-08-29 05:41 639235781101962521
519 ms 49.247.135.69
15 2026-08-29 05:25 639235771207673260
2252 ms 49.247.135.69
14 2026-08-29 05:08 639235761047429642
491 ms 49.247.135.69
13 2026-08-29 04:51 639235750964347246
507 ms 49.247.135.69
12 2026-08-29 04:34 639235740923490874
514 ms 49.247.135.69
11 2026-08-29 04:18 639235730842894399
547 ms 49.247.135.69
10 2026-08-29 04:01 639235720760084717
514 ms 49.247.135.69
9 2026-08-29 03:44 639235710843666743
2316 ms 49.247.135.69
8 2026-08-29 03:28 639235700733510561
4 ms 49.247.135.69
7 2026-08-29 03:11 639235690509906192
509 ms 49.247.135.69
6 2026-08-29 02:53 639235680156673501
523 ms 49.247.135.69
5 2026-08-29 02:36 639235669720606443
512 ms 49.247.135.69
4 2026-08-29 01:42 639235637451417084
490 ms 49.247.135.69
3 2026-08-29 01:25 639235627307383453
537 ms 49.247.135.69
2 2026-08-29 01:08 639235616906386856
518 ms 49.247.135.69
1 2026-08-29 00:51 639235606582912691
510 ms 49.247.135.69