DNS response history for ns3.daejeoncitytour.co.kr

ns3.daejeoncitytour.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-09-01. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 753 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 ns3.daejeoncitytour.co.kr.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

753 ms

Calculated from available response records

Latest Check on Selected Date

2026-09-01 12:48

All timestamps shown in UTC

Latest Resolved IP on Selected Date

116.126.143.225

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 ns3.daejeoncitytour.co.kr

Showing DNS history for 2026-09-01 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-09-01 12:48 639238628486902752
300 ms 116.126.143.225
36 2026-09-01 12:31 639238617906743100
285 ms 116.126.143.225
35 2026-09-01 12:13 639238607506044626
289 ms 116.126.143.225
34 2026-09-01 11:56 639238597040761406
281 ms 116.126.143.225
33 2026-09-01 11:38 639238586261546969
294 ms 116.126.143.225
32 2026-09-01 11:21 639238575587642333
580 ms 116.126.143.225
31 2026-09-01 10:26 639238543127398267
566 ms 116.126.143.225
30 2026-09-01 10:09 639238532668234016
1134 ms 116.126.143.225
29 2026-09-01 09:51 639238522029321761
569 ms 116.126.143.225
28 2026-09-01 09:34 639238511519050351
872 ms 116.126.143.225
27 2026-09-01 09:16 639238500942239673
391 ms 116.126.143.225
26 2026-09-01 08:58 639238490412377398
1383 ms 116.126.143.225
25 2026-09-01 08:41 639238479833203021
533 ms 116.126.143.225
24 2026-09-01 08:23 639238469140507479
572 ms 116.126.143.225
23 2026-09-01 08:05 639238458443560361
592 ms 116.126.143.225
22 2026-09-01 07:48 639238447694851502
1151 ms 116.126.143.225
21 2026-09-01 07:30 639238436624109087
1131 ms 116.126.143.225
20 2026-09-01 07:11 639238425565611335
1157 ms 116.126.143.225
19 2026-09-01 06:15 639238392250222581
1179 ms 116.126.143.225
18 2026-09-01 05:57 639238381322537831
582 ms 116.126.143.225
17 2026-09-01 05:39 639238370248186084
582 ms 116.126.143.225
16 2026-09-01 05:21 639238359264687845
858 ms 116.126.143.225
15 2026-09-01 05:02 639238348534621818
569 ms 116.126.143.225
14 2026-09-01 04:44 639238337725739433
1154 ms 116.126.143.225
13 2026-09-01 04:26 639238326844749368
570 ms 116.126.143.225
12 2026-09-01 04:08 639238315792024737
1168 ms 116.126.143.225
11 2026-09-01 03:50 639238304931064768
789 ms 116.126.143.225
10 2026-09-01 03:32 639238294131483803
530 ms 116.126.143.225
9 2026-09-01 03:14 639238283314985519
968 ms 116.126.143.225
8 2026-09-01 02:56 639238272374093187
1050 ms 116.126.143.225
7 2026-09-01 02:02 639238240032549922
523 ms 116.126.143.225
6 2026-09-01 01:44 639238229204177368
1043 ms 116.126.143.225
5 2026-09-01 01:26 639238218326150282
532 ms 116.126.143.225
4 2026-09-01 01:08 639238207574700853
792 ms 116.126.143.225
3 2026-09-01 00:50 639238196660283915
1046 ms 116.126.143.225
2 2026-09-01 00:31 639238185782358546
1045 ms 116.126.143.225
1 2026-09-01 00:13 639238175054391781
789 ms 116.126.143.225