DNS response history for ns1.sacom.co.jp

ns1.sacom.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-25. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 449 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 ns1.sacom.co.jp.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

449 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

153.122.10.22

Most recently resolved hosting IP on selected date

Successful Responses

37

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 ns1.sacom.co.jp

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
37 2026-08-25 12:59 639232587225721862
296 ms 153.122.10.22
36 2026-08-25 12:41 639232576780683689
288 ms 153.122.10.22
35 2026-08-25 12:24 639232566381512620
284 ms 153.122.10.22
34 2026-08-25 12:07 639232556111768563
554 ms 153.122.10.22
33 2026-08-25 11:50 639232545839529039
818 ms 153.122.10.22
32 2026-08-25 11:32 639232535349285207
12 ms 153.122.10.22
31 2026-08-25 11:15 639232524938080723
547 ms 153.122.10.22
30 2026-08-25 10:21 639232492740373468
285 ms 153.122.10.22
29 2026-08-25 10:04 639232482235303141
563 ms 153.122.10.22
28 2026-08-25 09:46 639232471861770303
304 ms 153.122.10.22
27 2026-08-25 09:29 639232461630217327
543 ms 153.122.10.22
26 2026-08-25 09:12 639232451282965990
606 ms 153.122.10.22
25 2026-08-25 08:55 639232440814614938
577 ms 153.122.10.22
24 2026-08-25 08:37 639232430410720425
546 ms 153.122.10.22
23 2026-08-25 08:20 639232420003096185
546 ms 153.122.10.22
22 2026-08-25 08:03 639232409467287444
816 ms 153.122.10.22
21 2026-08-25 07:45 639232399077195997
9 ms 153.122.10.22
20 2026-08-25 07:28 639232388731528337
277 ms 153.122.10.22
19 2026-08-25 07:10 639232378288598612
551 ms 153.122.10.22
18 2026-08-25 06:17 639232346196373643
3 ms 153.122.10.22
17 2026-08-25 06:00 639232336112370741
545 ms 153.122.10.22
16 2026-08-25 05:43 639232326146508970
3 ms 153.122.10.22
15 2026-08-25 05:26 639232316189381720
3 ms 153.122.10.22
14 2026-08-25 05:10 639232306217998913
4 ms 153.122.10.22
13 2026-08-25 04:53 639232296255744174
538 ms 153.122.10.22
12 2026-08-25 04:37 639232286095760789
276 ms 153.122.10.22
11 2026-08-25 04:20 639232276086186273
300 ms 153.122.10.22
10 2026-08-25 04:03 639232265900986425
633 ms 153.122.10.22
9 2026-08-25 03:46 639232255723518075
552 ms 153.122.10.22
8 2026-08-25 03:29 639232245484452890
576 ms 153.122.10.22
7 2026-08-25 03:12 639232235157175331
277 ms 153.122.10.22
6 2026-08-25 02:18 639232203197189095
546 ms 153.122.10.22
5 2026-08-25 02:01 639232192844564298
575 ms 153.122.10.22
4 2026-08-25 01:44 639232182496008942
546 ms 153.122.10.22
3 2026-08-25 01:27 639232172197053132
280 ms 153.122.10.22
2 2026-08-25 00:33 639232140250307418
271 ms 153.122.10.22
1 2026-08-25 00:17 639232129927860324
2258 ms 153.122.10.22