DNS response history for ns.seo-kk.jp

ns.seo-kk.jp 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 385 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.seo-kk.jp.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

385 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:56

All timestamps shown in UTC

Latest Resolved IP on Selected Date

203.137.115.95

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.seo-kk.jp

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:56 639233414056832719
491 ms 203.137.115.95
35 2026-08-26 11:39 639233403515141099
512 ms 203.137.115.95
34 2026-08-26 10:44 639233370841350248
246 ms 203.137.115.95
33 2026-08-26 10:27 639233360361507238
489 ms 203.137.115.95
32 2026-08-26 10:10 639233350067824371
504 ms 203.137.115.95
31 2026-08-26 09:52 639233339545274518
485 ms 203.137.115.95
30 2026-08-26 09:35 639233329214918079
247 ms 203.137.115.95
29 2026-08-26 09:18 639233318749762337
499 ms 203.137.115.95
28 2026-08-26 09:00 639233308387917838
511 ms 203.137.115.95
27 2026-08-26 08:43 639233297961740122
249 ms 203.137.115.95
26 2026-08-26 08:25 639233287487159094
504 ms 203.137.115.95
25 2026-08-26 08:08 639233276995531707
247 ms 203.137.115.95
24 2026-08-26 07:51 639233266521568229
494 ms 203.137.115.95
23 2026-08-26 07:33 639233256081047431
504 ms 203.137.115.95
22 2026-08-26 06:39 639233223620132921
5 ms 203.137.115.95
21 2026-08-26 06:22 639233213287814244
250 ms 203.137.115.95
20 2026-08-26 06:04 639233202925983161
252 ms 203.137.115.95
19 2026-08-26 05:47 639233192644780696
490 ms 203.137.115.95
18 2026-08-26 05:30 639233182401183833
246 ms 203.137.115.95
17 2026-08-26 05:13 639233172074181051
10 ms 203.137.115.95
16 2026-08-26 04:56 639233161808421455
304 ms 203.137.115.95
15 2026-08-26 04:39 639233151357344052
333 ms 203.137.115.95
14 2026-08-26 04:21 639233141034116946
253 ms 203.137.115.95
13 2026-08-26 04:04 639233130828334142
506 ms 203.137.115.95
12 2026-08-26 03:47 639233120373450007
514 ms 203.137.115.95
11 2026-08-26 03:30 639233110066216193
488 ms 203.137.115.95
10 2026-08-26 02:36 639233078065410564
246 ms 203.137.115.95
9 2026-08-26 02:19 639233067787457832
766 ms 203.137.115.95
8 2026-08-26 02:02 639233057501801162
506 ms 203.137.115.95
7 2026-08-26 01:45 639233047089431703
244 ms 203.137.115.95
6 2026-08-26 01:28 639233036754790688
488 ms 203.137.115.95
5 2026-08-26 01:10 639233026412602472
488 ms 203.137.115.95
4 2026-08-26 00:53 639233016064066127
499 ms 203.137.115.95
3 2026-08-26 00:36 639233005922655772
502 ms 203.137.115.95
2 2026-08-26 00:19 639232995672256907
247 ms 203.137.115.95
1 2026-08-26 00:02 639232985300872416
246 ms 203.137.115.95