DNS response history for ns10.seoul24.com

ns10.seoul24.com 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 31 DNS check records, 31 successful responses, 0 failed responses, and 537 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 ns10.seoul24.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

537 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

34.97.161.176

Most recently resolved hosting IP on selected date

Successful Responses

31

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 ns10.seoul24.com

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
31 2026-08-25 11:14 639232524938080723
683 ms 34.97.161.176
30 2026-08-25 10:21 639232492740373468
664 ms 34.97.161.176
29 2026-08-25 10:04 639232482235303141
671 ms 34.97.161.176
28 2026-08-25 09:46 639232471861770303
676 ms 34.97.161.176
27 2026-08-25 09:29 639232461630217327
337 ms 34.97.161.176
26 2026-08-25 09:12 639232451282965990
4 ms 34.97.161.176
25 2026-08-25 08:54 639232440814614938
3 ms 34.97.161.176
24 2026-08-25 08:37 639232430410720425
660 ms 34.97.161.176
23 2026-08-25 08:20 639232420003096185
663 ms 34.97.161.176
22 2026-08-25 08:02 639232409467287444
669 ms 34.97.161.176
21 2026-08-25 07:45 639232399077195997
671 ms 34.97.161.176
20 2026-08-25 07:27 639232388731528337
663 ms 34.97.161.176
19 2026-08-25 07:10 639232378288598612
331 ms 34.97.161.176
18 2026-08-25 06:16 639232346196373643
660 ms 34.97.161.176
17 2026-08-25 06:00 639232336112370741
290 ms 34.97.161.176
16 2026-08-25 05:43 639232326146508970
8 ms 34.97.161.176
15 2026-08-25 05:26 639232316189381720
373 ms 34.97.161.176
14 2026-08-25 05:10 639232306217998913
660 ms 34.97.161.176
13 2026-08-25 04:53 639232296255744174
678 ms 34.97.161.176
12 2026-08-25 04:36 639232286095760789
652 ms 34.97.161.176
11 2026-08-25 04:19 639232276086186273
664 ms 34.97.161.176
10 2026-08-25 04:03 639232265900986425
667 ms 34.97.161.176
9 2026-08-25 03:46 639232255723518075
667 ms 34.97.161.176
8 2026-08-25 03:29 639232245484452890
325 ms 34.97.161.176
7 2026-08-25 03:12 639232235157175331
662 ms 34.97.161.176
6 2026-08-25 02:18 639232203197189095
326 ms 34.97.161.176
5 2026-08-25 02:01 639232192844564298
658 ms 34.97.161.176
4 2026-08-25 01:44 639232182496008942
662 ms 34.97.161.176
3 2026-08-25 01:26 639232172197053132
663 ms 34.97.161.176
2 2026-08-25 00:33 639232140250307418
666 ms 34.97.161.176
1 2026-08-25 00:16 639232129927860324
667 ms 34.97.161.176