DNS response history for ns.say19.co.kr

ns.say19.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 36 DNS check records, 36 successful responses, 0 failed responses, and 419 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.say19.co.kr.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

419 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:58

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.109.103.137

Most recently resolved hosting IP on selected date

Successful Responses

36

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.say19.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
36 2026-08-26 11:58 639233414056832719
555 ms 210.109.103.137
35 2026-08-26 11:40 639233403515141099
237 ms 210.109.103.137
34 2026-08-26 10:45 639233370841350248
536 ms 210.109.103.137
33 2026-08-26 10:28 639233360361507238
235 ms 210.109.103.137
32 2026-08-26 10:11 639233350067824371
460 ms 210.109.103.137
31 2026-08-26 09:53 639233339545274518
233 ms 210.109.103.137
30 2026-08-26 09:36 639233329214918079
554 ms 210.109.103.137
29 2026-08-26 09:19 639233318749762337
525 ms 210.109.103.137
28 2026-08-26 09:01 639233308387917838
520 ms 210.109.103.137
27 2026-08-26 08:44 639233297961740122
543 ms 210.109.103.137
26 2026-08-26 08:27 639233287487159094
238 ms 210.109.103.137
25 2026-08-26 08:09 639233276995531707
458 ms 210.109.103.137
24 2026-08-26 07:52 639233266521568229
562 ms 210.109.103.137
23 2026-08-26 07:34 639233256081047431
549 ms 210.109.103.137
22 2026-08-26 06:40 639233223620132921
230 ms 210.109.103.137
21 2026-08-26 06:23 639233213287814244
520 ms 210.109.103.137
20 2026-08-26 06:05 639233202925983161
537 ms 210.109.103.137
19 2026-08-26 05:48 639233192644780696
232 ms 210.109.103.137
18 2026-08-26 05:31 639233182401183833
536 ms 210.109.103.137
17 2026-08-26 05:14 639233172074181051
539 ms 210.109.103.137
16 2026-08-26 04:57 639233161808421455
535 ms 210.109.103.137
15 2026-08-26 04:40 639233151357344052
520 ms 210.109.103.137
14 2026-08-26 04:22 639233141034116946
232 ms 210.109.103.137
13 2026-08-26 04:05 639233130828334142
261 ms 210.109.103.137
12 2026-08-26 03:48 639233120373450007
234 ms 210.109.103.137
11 2026-08-26 03:31 639233110066216193
542 ms 210.109.103.137
10 2026-08-26 02:37 639233078065410564
229 ms 210.109.103.137
9 2026-08-26 02:20 639233067787457832
459 ms 210.109.103.137
8 2026-08-26 02:03 639233057501801162
526 ms 210.109.103.137
7 2026-08-26 01:46 639233047089431703
526 ms 210.109.103.137
6 2026-08-26 01:29 639233036754790688
226 ms 210.109.103.137
5 2026-08-26 01:11 639233026412602472
539 ms 210.109.103.137
4 2026-08-26 00:54 639233016064066127
541 ms 210.109.103.137
3 2026-08-26 00:37 639233005922655772
226 ms 210.109.103.137
2 2026-08-26 00:20 639232995672256907
312 ms 210.109.103.137
1 2026-08-26 00:03 639232985300872416
365 ms 210.109.103.137