DNS response history for ns.primegate.co.jp

ns.primegate.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 764 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.primegate.co.jp.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

764 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

61.195.157.170

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 ns.primegate.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:42 639232576780683689
729 ms 61.195.157.170
36 2026-08-25 12:25 639232566381512620
740 ms 61.195.157.170
35 2026-08-25 12:08 639232556111768563
768 ms 61.195.157.170
34 2026-08-25 11:51 639232545839529039
489 ms 61.195.157.170
33 2026-08-25 11:33 639232535349285207
707 ms 61.195.157.170
32 2026-08-25 11:16 639232524938080723
709 ms 61.195.157.170
31 2026-08-25 10:22 639232492740373468
713 ms 61.195.157.170
30 2026-08-25 10:05 639232482235303141
745 ms 61.195.157.170
29 2026-08-25 09:47 639232471861770303
774 ms 61.195.157.170
28 2026-08-25 09:30 639232461630217327
876 ms 61.195.157.170
27 2026-08-25 09:13 639232451282965990
717 ms 61.195.157.170
26 2026-08-25 08:56 639232440814614938
735 ms 61.195.157.170
25 2026-08-25 08:38 639232430410720425
479 ms 61.195.157.170
24 2026-08-25 08:21 639232420003096185
748 ms 61.195.157.170
23 2026-08-25 08:04 639232409467287444
983 ms 61.195.157.170
22 2026-08-25 07:46 639232399077195997
714 ms 61.195.157.170
21 2026-08-25 07:29 639232388731528337
729 ms 61.195.157.170
20 2026-08-25 07:12 639232378288598612
714 ms 61.195.157.170
19 2026-08-25 06:18 639232346196373643
1085 ms 61.195.157.170
18 2026-08-25 06:01 639232336112370741
726 ms 61.195.157.170
17 2026-08-25 05:44 639232326146508970
2272 ms 61.195.157.170
16 2026-08-25 05:28 639232316189381720
5 ms 61.195.157.170
15 2026-08-25 05:11 639232306217998913
2 ms 61.195.157.170
14 2026-08-25 04:54 639232296255744174
719 ms 61.195.157.170
13 2026-08-25 04:38 639232286095760789
492 ms 61.195.157.170
12 2026-08-25 04:21 639232276086186273
3 ms 61.195.157.170
11 2026-08-25 04:04 639232265900986425
716 ms 61.195.157.170
10 2026-08-25 03:47 639232255723518075
721 ms 61.195.157.170
9 2026-08-25 03:30 639232245484452890
2288 ms 61.195.157.170
8 2026-08-25 03:13 639232235157175331
528 ms 61.195.157.170
7 2026-08-25 02:19 639232203197189095
995 ms 61.195.157.170
6 2026-08-25 02:03 639232192844564298
755 ms 61.195.157.170
5 2026-08-25 01:45 639232182496008942
745 ms 61.195.157.170
4 2026-08-25 01:28 639232172197053132
862 ms 61.195.157.170
3 2026-08-25 00:34 639232140250307418
740 ms 61.195.157.170
2 2026-08-25 00:18 639232129927860324
818 ms 61.195.157.170
1 2026-08-25 00:00 639232119551972438
714 ms 61.195.157.170