DNS response history for ns1.bdpos.kr

ns1.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-25. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 451 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 ns1.bdpos.kr.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

451 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:04

All timestamps shown in UTC

Latest Resolved IP on Selected Date

222.122.85.100

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 ns1.bdpos.kr

Showing DNS history for 2026-08-25 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-25 10:04 639232482235303141
583 ms 222.122.85.100
28 2026-08-25 09:47 639232471861770303
577 ms 222.122.85.100
27 2026-08-25 09:29 639232461630217327
293 ms 222.122.85.100
26 2026-08-25 09:12 639232451282965990
575 ms 222.122.85.100
25 2026-08-25 08:55 639232440814614938
633 ms 222.122.85.100
24 2026-08-25 08:38 639232430410720425
601 ms 222.122.85.100
23 2026-08-25 08:20 639232420003096185
285 ms 222.122.85.100
22 2026-08-25 08:03 639232409467287444
281 ms 222.122.85.100
21 2026-08-25 07:45 639232399077195997
570 ms 222.122.85.100
20 2026-08-25 07:28 639232388731528337
839 ms 222.122.85.100
19 2026-08-25 07:11 639232378288598612
586 ms 222.122.85.100
18 2026-08-25 06:17 639232346196373643
578 ms 222.122.85.100
17 2026-08-25 06:00 639232336112370741
579 ms 222.122.85.100
16 2026-08-25 05:43 639232326146508970
4 ms 222.122.85.100
15 2026-08-25 05:27 639232316189381720
563 ms 222.122.85.100
14 2026-08-25 05:10 639232306217998913
572 ms 222.122.85.100
13 2026-08-25 04:54 639232296255744174
574 ms 222.122.85.100
12 2026-08-25 04:37 639232286095760789
3 ms 222.122.85.100
11 2026-08-25 04:20 639232276086186273
3 ms 222.122.85.100
10 2026-08-25 04:03 639232265900986425
577 ms 222.122.85.100
9 2026-08-25 03:46 639232255723518075
288 ms 222.122.85.100
8 2026-08-25 03:29 639232245484452890
290 ms 222.122.85.100
7 2026-08-25 03:12 639232235157175331
281 ms 222.122.85.100
6 2026-08-25 02:19 639232203197189095
287 ms 222.122.85.100
5 2026-08-25 02:02 639232192844564298
604 ms 222.122.85.100
4 2026-08-25 01:44 639232182496008942
583 ms 222.122.85.100
3 2026-08-25 01:27 639232172197053132
605 ms 222.122.85.100
2 2026-08-25 00:34 639232140250307418
587 ms 222.122.85.100
1 2026-08-25 00:17 639232129927860324
284 ms 222.122.85.100