DNS response history for ns.citywaste.or.kr

ns.citywaste.or.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-24. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 359 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 ns.citywaste.or.kr.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

359 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:37

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.104.107.130

Most recently resolved hosting IP on selected date

Successful Responses

32

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 ns.citywaste.or.kr

Showing DNS history for 2026-08-24 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
32 2026-08-24 13:37 639231745628278877
590 ms 210.104.107.130
31 2026-08-24 13:20 639231735407682062
3 ms 210.104.107.130
30 2026-08-24 12:27 639231703815441688
4 ms 210.104.107.130
29 2026-08-24 12:10 639231693747052549
5 ms 210.104.107.130
28 2026-08-24 11:53 639231683712487276
617 ms 210.104.107.130
27 2026-08-24 11:36 639231673513573868
607 ms 210.104.107.130
26 2026-08-24 10:43 639231641791249939
6 ms 210.104.107.130
25 2026-08-24 10:27 639231631866211033
606 ms 210.104.107.130
24 2026-08-24 10:10 639231621644955316
617 ms 210.104.107.130
23 2026-08-24 09:53 639231611478799259
612 ms 210.104.107.130
22 2026-08-24 09:00 639231579923718211
5 ms 210.104.107.130
21 2026-08-24 08:44 639231569810702936
874 ms 210.104.107.130
20 2026-08-24 08:27 639231559762411619
873 ms 210.104.107.130
19 2026-08-24 08:10 639231549663595407
857 ms 210.104.107.130
18 2026-08-24 07:17 639231518076817246
622 ms 210.104.107.130
17 2026-08-24 07:01 639231508078650885
646 ms 210.104.107.130
16 2026-08-24 06:44 639231498210697093
3 ms 210.104.107.130
15 2026-08-24 06:27 639231488109699360
5 ms 210.104.107.130
14 2026-08-24 05:35 639231456772510692
605 ms 210.104.107.130
13 2026-08-24 05:19 639231447084631185
840 ms 210.104.107.130
12 2026-08-24 05:02 639231437208519473
12 ms 210.104.107.130
11 2026-08-24 04:46 639231427209627490
2 ms 210.104.107.130
10 2026-08-24 03:53 639231395791246644
3 ms 210.104.107.130
9 2026-08-24 03:37 639231386075551458
623 ms 210.104.107.130
8 2026-08-24 03:21 639231376208713791
2 ms 210.104.107.130
7 2026-08-24 03:04 639231366170589276
3 ms 210.104.107.130
6 2026-08-24 02:12 639231334732159368
2 ms 210.104.107.130
5 2026-08-24 01:55 639231325035670078
611 ms 210.104.107.130
4 2026-08-24 01:39 639231315132253837
3 ms 210.104.107.130
3 2026-08-24 01:22 639231305014280808
633 ms 210.104.107.130
2 2026-08-24 00:30 639231273779380675
605 ms 210.104.107.130
1 2026-08-24 00:14 639231264180839154
3 ms 210.104.107.130