DNS response history for ns.s-max.co.jp

ns.s-max.co.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 34 DNS check records, 34 successful responses, 0 failed responses, and 592 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.s-max.co.jp.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

592 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.164.113.234

Most recently resolved hosting IP on selected date

Successful Responses

34

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.s-max.co.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
34 2026-08-26 10:46 639233370841350248
613 ms 210.164.113.234
33 2026-08-26 10:28 639233360361507238
707 ms 210.164.113.234
32 2026-08-26 10:11 639233350067824371
284 ms 210.164.113.234
31 2026-08-26 09:54 639233339545274518
518 ms 210.164.113.234
30 2026-08-26 09:36 639233329214918079
297 ms 210.164.113.234
29 2026-08-26 09:19 639233318749762337
543 ms 210.164.113.234
28 2026-08-26 09:02 639233308387917838
531 ms 210.164.113.234
27 2026-08-26 08:44 639233297961740122
543 ms 210.164.113.234
26 2026-08-26 08:27 639233287487159094
532 ms 210.164.113.234
25 2026-08-26 08:09 639233276995531707
816 ms 210.164.113.234
24 2026-08-26 07:52 639233266521568229
646 ms 210.164.113.234
23 2026-08-26 07:34 639233256081047431
599 ms 210.164.113.234
22 2026-08-26 06:40 639233223620132921
831 ms 210.164.113.234
21 2026-08-26 06:23 639233213287814244
520 ms 210.164.113.234
20 2026-08-26 06:06 639233202925983161
535 ms 210.164.113.234
19 2026-08-26 05:49 639233192644780696
557 ms 210.164.113.234
18 2026-08-26 05:31 639233182401183833
528 ms 210.164.113.234
17 2026-08-26 05:14 639233172074181051
537 ms 210.164.113.234
16 2026-08-26 04:57 639233161808421455
537 ms 210.164.113.234
15 2026-08-26 04:40 639233151357344052
526 ms 210.164.113.234
14 2026-08-26 04:23 639233141034116946
535 ms 210.164.113.234
13 2026-08-26 04:05 639233130828334142
527 ms 210.164.113.234
12 2026-08-26 03:48 639233120373450007
547 ms 210.164.113.234
11 2026-08-26 03:31 639233110066216193
595 ms 210.164.113.234
10 2026-08-26 02:38 639233078065410564
558 ms 210.164.113.234
9 2026-08-26 02:21 639233067787457832
552 ms 210.164.113.234
8 2026-08-26 02:03 639233057501801162
778 ms 210.164.113.234
7 2026-08-26 01:46 639233047089431703
545 ms 210.164.113.234
6 2026-08-26 01:29 639233036754790688
821 ms 210.164.113.234
5 2026-08-26 01:12 639233026412602472
921 ms 210.164.113.234
4 2026-08-26 00:54 639233016064066127
628 ms 210.164.113.234
3 2026-08-26 00:37 639233005922655772
556 ms 210.164.113.234
2 2026-08-26 00:20 639232995672256907
820 ms 210.164.113.234
1 2026-08-26 00:03 639232985300872416
559 ms 210.164.113.234