DNS response history for ns2.pulcma.co.kr

ns2.pulcma.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 542 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.pulcma.co.kr.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

542 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

219.251.156.125

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.pulcma.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:20 639233318749762337
4 ms 219.251.156.125
28 2026-08-26 09:02 639233308387917838
586 ms 219.251.156.125
27 2026-08-26 08:45 639233297961740122
858 ms 219.251.156.125
26 2026-08-26 08:27 639233287487159094
708 ms 219.251.156.125
25 2026-08-26 08:10 639233276995531707
593 ms 219.251.156.125
24 2026-08-26 07:52 639233266521568229
582 ms 219.251.156.125
23 2026-08-26 07:35 639233256081047431
1222 ms 219.251.156.125
22 2026-08-26 06:41 639233223620132921
597 ms 219.251.156.125
21 2026-08-26 06:24 639233213287814244
3 ms 219.251.156.125
20 2026-08-26 06:06 639233202925983161
594 ms 219.251.156.125
19 2026-08-26 05:49 639233192644780696
598 ms 219.251.156.125
18 2026-08-26 05:32 639233182401183833
587 ms 219.251.156.125
17 2026-08-26 05:15 639233172074181051
596 ms 219.251.156.125
16 2026-08-26 04:58 639233161808421455
584 ms 219.251.156.125
15 2026-08-26 04:41 639233151357344052
586 ms 219.251.156.125
14 2026-08-26 04:23 639233141034116946
583 ms 219.251.156.125
13 2026-08-26 04:06 639233130828334142
3 ms 219.251.156.125
12 2026-08-26 03:49 639233120373450007
584 ms 219.251.156.125
11 2026-08-26 03:32 639233110066216193
586 ms 219.251.156.125
10 2026-08-26 02:38 639233078065410564
579 ms 219.251.156.125
9 2026-08-26 02:21 639233067787457832
597 ms 219.251.156.125
8 2026-08-26 02:04 639233057501801162
594 ms 219.251.156.125
7 2026-08-26 01:47 639233047089431703
582 ms 219.251.156.125
6 2026-08-26 01:29 639233036754790688
592 ms 219.251.156.125
5 2026-08-26 01:12 639233026412602472
593 ms 219.251.156.125
4 2026-08-26 00:55 639233016064066127
581 ms 219.251.156.125
3 2026-08-26 00:38 639233005922655772
573 ms 219.251.156.125
2 2026-08-26 00:21 639232995672256907
584 ms 219.251.156.125
1 2026-08-26 00:04 639232985300872416
3 ms 219.251.156.125