DNS response history for ns2.paxnews.co.kr

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

29

Historical checks stored for this nameserver on selected date

Average Latency

919 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

116.126.85.98

Most recently resolved hosting IP on selected date

Successful Responses

29

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.paxnews.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
29 2026-08-26 09:19 639233318749762337
591 ms 116.126.85.98
28 2026-08-26 09:01 639233308387917838
606 ms 116.126.85.98
27 2026-08-26 08:44 639233297961740122
590 ms 116.126.85.98
26 2026-08-26 08:27 639233287487159094
616 ms 116.126.85.98
25 2026-08-26 08:09 639233276995531707
303 ms 116.126.85.98
24 2026-08-26 07:52 639233266521568229
1227 ms 116.126.85.98
23 2026-08-26 07:34 639233256081047431
605 ms 116.126.85.98
22 2026-08-26 06:40 639233223620132921
610 ms 116.126.85.98
21 2026-08-26 06:23 639233213287814244
598 ms 116.126.85.98
20 2026-08-26 06:06 639233202925983161
623 ms 116.126.85.98
19 2026-08-26 05:49 639233192644780696
5473 ms 116.126.85.98
18 2026-08-26 05:31 639233182401183833
597 ms 116.126.85.98
17 2026-08-26 05:14 639233172074181051
588 ms 116.126.85.98
16 2026-08-26 04:57 639233161808421455
610 ms 116.126.85.98
15 2026-08-26 04:40 639233151357344052
1705 ms 116.126.85.98
14 2026-08-26 04:22 639233141034116946
1215 ms 116.126.85.98
13 2026-08-26 04:05 639233130828334142
610 ms 116.126.85.98
12 2026-08-26 03:48 639233120373450007
618 ms 116.126.85.98
11 2026-08-26 03:31 639233110066216193
2280 ms 116.126.85.98
10 2026-08-26 02:38 639233078065410564
583 ms 116.126.85.98
9 2026-08-26 02:20 639233067787457832
592 ms 116.126.85.98
8 2026-08-26 02:03 639233057501801162
576 ms 116.126.85.98
7 2026-08-26 01:46 639233047089431703
601 ms 116.126.85.98
6 2026-08-26 01:29 639233036754790688
609 ms 116.126.85.98
5 2026-08-26 01:12 639233026412602472
592 ms 116.126.85.98
4 2026-08-26 00:54 639233016064066127
628 ms 116.126.85.98
3 2026-08-26 00:37 639233005922655772
599 ms 116.126.85.98
2 2026-08-26 00:20 639232995672256907
1214 ms 116.126.85.98
1 2026-08-26 00:03 639232985300872416
603 ms 116.126.85.98