DNS response history for ns.seiko-p.net

ns.seiko-p.net 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 579 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.seiko-p.net.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

579 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:57

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.32.142.136

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.seiko-p.net

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:57 639233414056832719
529 ms 202.32.142.136
35 2026-08-26 11:40 639233403515141099
530 ms 202.32.142.136
34 2026-08-26 10:45 639233370841350248
523 ms 202.32.142.136
33 2026-08-26 10:28 639233360361507238
529 ms 202.32.142.136
32 2026-08-26 10:11 639233350067824371
535 ms 202.32.142.136
31 2026-08-26 09:53 639233339545274518
531 ms 202.32.142.136
30 2026-08-26 09:36 639233329214918079
521 ms 202.32.142.136
29 2026-08-26 09:19 639233318749762337
513 ms 202.32.142.136
28 2026-08-26 09:01 639233308387917838
524 ms 202.32.142.136
27 2026-08-26 08:44 639233297961740122
532 ms 202.32.142.136
26 2026-08-26 08:26 639233287487159094
518 ms 202.32.142.136
25 2026-08-26 08:09 639233276995531707
521 ms 202.32.142.136
24 2026-08-26 07:51 639233266521568229
523 ms 202.32.142.136
23 2026-08-26 07:34 639233256081047431
522 ms 202.32.142.136
22 2026-08-26 06:40 639233223620132921
538 ms 202.32.142.136
21 2026-08-26 06:23 639233213287814244
524 ms 202.32.142.136
20 2026-08-26 06:05 639233202925983161
547 ms 202.32.142.136
19 2026-08-26 05:48 639233192644780696
518 ms 202.32.142.136
18 2026-08-26 05:31 639233182401183833
531 ms 202.32.142.136
17 2026-08-26 05:14 639233172074181051
531 ms 202.32.142.136
16 2026-08-26 04:57 639233161808421455
522 ms 202.32.142.136
15 2026-08-26 04:40 639233151357344052
516 ms 202.32.142.136
14 2026-08-26 04:22 639233141034116946
529 ms 202.32.142.136
13 2026-08-26 04:05 639233130828334142
532 ms 202.32.142.136
12 2026-08-26 03:48 639233120373450007
517 ms 202.32.142.136
11 2026-08-26 03:31 639233110066216193
545 ms 202.32.142.136
10 2026-08-26 02:37 639233078065410564
532 ms 202.32.142.136
9 2026-08-26 02:20 639233067787457832
528 ms 202.32.142.136
8 2026-08-26 02:03 639233057501801162
514 ms 202.32.142.136
7 2026-08-26 01:46 639233047089431703
527 ms 202.32.142.136
6 2026-08-26 01:28 639233036754790688
540 ms 202.32.142.136
5 2026-08-26 01:11 639233026412602472
525 ms 202.32.142.136
4 2026-08-26 00:54 639233016064066127
2302 ms 202.32.142.136
3 2026-08-26 00:37 639233005922655772
617 ms 202.32.142.136
2 2026-08-26 00:20 639232995672256907
531 ms 202.32.142.136
1 2026-08-26 00:03 639232985300872416
518 ms 202.32.142.136