DNS response history for ns3.bdpos.kr

ns3.bdpos.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 34 DNS check records, 34 successful responses, 0 failed responses, and 520 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.bdpos.kr.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

520 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

222.122.85.109

Most recently resolved hosting IP on selected date

Successful Responses

34

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.bdpos.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
34 2026-08-26 10:45 639233370841350248
579 ms 222.122.85.109
33 2026-08-26 10:28 639233360361507238
591 ms 222.122.85.109
32 2026-08-26 10:10 639233350067824371
581 ms 222.122.85.109
31 2026-08-26 09:53 639233339545274518
561 ms 222.122.85.109
30 2026-08-26 09:35 639233329214918079
572 ms 222.122.85.109
29 2026-08-26 09:18 639233318749762337
601 ms 222.122.85.109
28 2026-08-26 09:01 639233308387917838
604 ms 222.122.85.109
27 2026-08-26 08:43 639233297961740122
591 ms 222.122.85.109
26 2026-08-26 08:26 639233287487159094
586 ms 222.122.85.109
25 2026-08-26 08:09 639233276995531707
573 ms 222.122.85.109
24 2026-08-26 07:51 639233266521568229
582 ms 222.122.85.109
23 2026-08-26 07:34 639233256081047431
601 ms 222.122.85.109
22 2026-08-26 06:40 639233223620132921
582 ms 222.122.85.109
21 2026-08-26 06:22 639233213287814244
567 ms 222.122.85.109
20 2026-08-26 06:05 639233202925983161
583 ms 222.122.85.109
19 2026-08-26 05:48 639233192644780696
584 ms 222.122.85.109
18 2026-08-26 05:31 639233182401183833
564 ms 222.122.85.109
17 2026-08-26 05:14 639233172074181051
3 ms 222.122.85.109
16 2026-08-26 04:56 639233161808421455
2 ms 222.122.85.109
15 2026-08-26 04:39 639233151357344052
598 ms 222.122.85.109
14 2026-08-26 04:22 639233141034116946
577 ms 222.122.85.109
13 2026-08-26 04:05 639233130828334142
583 ms 222.122.85.109
12 2026-08-26 03:48 639233120373450007
565 ms 222.122.85.109
11 2026-08-26 03:30 639233110066216193
844 ms 222.122.85.109
10 2026-08-26 02:37 639233078065410564
575 ms 222.122.85.109
9 2026-08-26 02:20 639233067787457832
591 ms 222.122.85.109
8 2026-08-26 02:03 639233057501801162
578 ms 222.122.85.109
7 2026-08-26 01:46 639233047089431703
557 ms 222.122.85.109
6 2026-08-26 01:28 639233036754790688
563 ms 222.122.85.109
5 2026-08-26 01:11 639233026412602472
3 ms 222.122.85.109
4 2026-08-26 00:54 639233016064066127
3 ms 222.122.85.109
3 2026-08-26 00:36 639233005922655772
582 ms 222.122.85.109
2 2026-08-26 00:19 639232995672256907
575 ms 222.122.85.109
1 2026-08-26 00:02 639232985300872416
575 ms 222.122.85.109