DNS response history for ns.sanritsu-c.com

ns.sanritsu-c.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-26. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 505 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.sanritsu-c.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

505 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:35

All timestamps shown in UTC

Latest Resolved IP on Selected Date

153.123.9.155

Most recently resolved hosting IP on selected date

Successful Responses

30

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.sanritsu-c.com

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
30 2026-08-26 09:35 639233329214918079
554 ms 153.123.9.155
29 2026-08-26 09:18 639233318749762337
271 ms 153.123.9.155
28 2026-08-26 09:01 639233308387917838
795 ms 153.123.9.155
27 2026-08-26 08:43 639233297961740122
540 ms 153.123.9.155
26 2026-08-26 08:26 639233287487159094
558 ms 153.123.9.155
25 2026-08-26 08:08 639233276995531707
558 ms 153.123.9.155
24 2026-08-26 07:51 639233266521568229
554 ms 153.123.9.155
23 2026-08-26 07:33 639233256081047431
530 ms 153.123.9.155
22 2026-08-26 06:39 639233223620132921
564 ms 153.123.9.155
21 2026-08-26 06:22 639233213287814244
3 ms 153.123.9.155
20 2026-08-26 06:05 639233202925983161
7 ms 153.123.9.155
19 2026-08-26 05:48 639233192644780696
534 ms 153.123.9.155
18 2026-08-26 05:30 639233182401183833
3 ms 153.123.9.155
17 2026-08-26 05:13 639233172074181051
531 ms 153.123.9.155
16 2026-08-26 04:56 639233161808421455
539 ms 153.123.9.155
15 2026-08-26 04:39 639233151357344052
3 ms 153.123.9.155
14 2026-08-26 04:22 639233141034116946
813 ms 153.123.9.155
13 2026-08-26 04:04 639233130828334142
550 ms 153.123.9.155
12 2026-08-26 03:47 639233120373450007
549 ms 153.123.9.155
11 2026-08-26 03:30 639233110066216193
533 ms 153.123.9.155
10 2026-08-26 02:37 639233078065410564
793 ms 153.123.9.155
9 2026-08-26 02:20 639233067787457832
537 ms 153.123.9.155
8 2026-08-26 02:02 639233057501801162
801 ms 153.123.9.155
7 2026-08-26 01:45 639233047089431703
540 ms 153.123.9.155
6 2026-08-26 01:28 639233036754790688
529 ms 153.123.9.155
5 2026-08-26 01:11 639233026412602472
534 ms 153.123.9.155
4 2026-08-26 00:53 639233016064066127
548 ms 153.123.9.155
3 2026-08-26 00:36 639233005922655772
547 ms 153.123.9.155
2 2026-08-26 00:19 639232995672256907
558 ms 153.123.9.155
1 2026-08-26 00:02 639232985300872416
778 ms 153.123.9.155