DNS response history for ns.paycoms.co.kr

ns.paycoms.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-25. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 355 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 ns.paycoms.co.kr.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

355 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

211.234.99.131

Most recently resolved hosting IP on selected date

Successful Responses

32

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 ns.paycoms.co.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
32 2026-08-25 11:15 639232524938080723
595 ms 211.234.99.131
31 2026-08-25 10:22 639232492740373468
5 ms 211.234.99.131
30 2026-08-25 10:04 639232482235303141
596 ms 211.234.99.131
29 2026-08-25 09:47 639232471861770303
621 ms 211.234.99.131
28 2026-08-25 09:30 639232461630217327
4 ms 211.234.99.131
27 2026-08-25 09:13 639232451282965990
5 ms 211.234.99.131
26 2026-08-25 08:55 639232440814614938
831 ms 211.234.99.131
25 2026-08-25 08:38 639232430410720425
851 ms 211.234.99.131
24 2026-08-25 08:20 639232420003096185
579 ms 211.234.99.131
23 2026-08-25 08:03 639232409467287444
4 ms 211.234.99.131
22 2026-08-25 07:46 639232399077195997
4 ms 211.234.99.131
21 2026-08-25 07:28 639232388731528337
580 ms 211.234.99.131
20 2026-08-25 07:11 639232378288598612
596 ms 211.234.99.131
19 2026-08-25 06:17 639232346196373643
616 ms 211.234.99.131
18 2026-08-25 06:00 639232336112370741
37 ms 211.234.99.131
17 2026-08-25 05:44 639232326146508970
595 ms 211.234.99.131
16 2026-08-25 05:27 639232316189381720
604 ms 211.234.99.131
15 2026-08-25 05:11 639232306217998913
590 ms 211.234.99.131
14 2026-08-25 04:54 639232296255744174
3 ms 211.234.99.131
13 2026-08-25 04:37 639232286095760789
2 ms 211.234.99.131
12 2026-08-25 04:20 639232276086186273
3 ms 211.234.99.131
11 2026-08-25 04:03 639232265900986425
594 ms 211.234.99.131
10 2026-08-25 03:47 639232255723518075
595 ms 211.234.99.131
9 2026-08-25 03:29 639232245484452890
3 ms 211.234.99.131
8 2026-08-25 03:12 639232235157175331
589 ms 211.234.99.131
7 2026-08-25 02:19 639232203197189095
601 ms 211.234.99.131
6 2026-08-25 02:02 639232192844564298
2 ms 211.234.99.131
5 2026-08-25 01:45 639232182496008942
2 ms 211.234.99.131
4 2026-08-25 01:27 639232172197053132
4 ms 211.234.99.131
3 2026-08-25 00:34 639232140250307418
610 ms 211.234.99.131
2 2026-08-25 00:17 639232129927860324
632 ms 211.234.99.131
1 2026-08-25 00:00 639232119551972438
3 ms 211.234.99.131