DNS response history for ns1.go5.jp

ns1.go5.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 577 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.go5.jp.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

577 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

49.212.125.38

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.go5.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
543 ms 49.212.125.38
36 2026-08-25 12:25 639232566381512620
543 ms 49.212.125.38
35 2026-08-25 12:07 639232556111768563
559 ms 49.212.125.38
34 2026-08-25 11:50 639232545839529039
561 ms 49.212.125.38
33 2026-08-25 11:33 639232535349285207
567 ms 49.212.125.38
32 2026-08-25 11:16 639232524938080723
535 ms 49.212.125.38
31 2026-08-25 10:22 639232492740373468
542 ms 49.212.125.38
30 2026-08-25 10:05 639232482235303141
818 ms 49.212.125.38
29 2026-08-25 09:47 639232471861770303
558 ms 49.212.125.38
28 2026-08-25 09:30 639232461630217327
553 ms 49.212.125.38
27 2026-08-25 09:13 639232451282965990
542 ms 49.212.125.38
26 2026-08-25 08:56 639232440814614938
569 ms 49.212.125.38
25 2026-08-25 08:38 639232430410720425
562 ms 49.212.125.38
24 2026-08-25 08:21 639232420003096185
2276 ms 49.212.125.38
23 2026-08-25 08:03 639232409467287444
549 ms 49.212.125.38
22 2026-08-25 07:46 639232399077195997
560 ms 49.212.125.38
21 2026-08-25 07:29 639232388731528337
545 ms 49.212.125.38
20 2026-08-25 07:11 639232378288598612
553 ms 49.212.125.38
19 2026-08-25 06:17 639232346196373643
551 ms 49.212.125.38
18 2026-08-25 06:01 639232336112370741
543 ms 49.212.125.38
17 2026-08-25 05:44 639232326146508970
539 ms 49.212.125.38
16 2026-08-25 05:27 639232316189381720
553 ms 49.212.125.38
15 2026-08-25 05:11 639232306217998913
563 ms 49.212.125.38
14 2026-08-25 04:54 639232296255744174
545 ms 49.212.125.38
13 2026-08-25 04:37 639232286095760789
538 ms 49.212.125.38
12 2026-08-25 04:20 639232276086186273
566 ms 49.212.125.38
11 2026-08-25 04:04 639232265900986425
298 ms 49.212.125.38
10 2026-08-25 03:47 639232255723518075
540 ms 49.212.125.38
9 2026-08-25 03:30 639232245484452890
558 ms 49.212.125.38
8 2026-08-25 03:13 639232235157175331
586 ms 49.212.125.38
7 2026-08-25 02:19 639232203197189095
279 ms 49.212.125.38
6 2026-08-25 02:02 639232192844564298
281 ms 49.212.125.38
5 2026-08-25 01:45 639232182496008942
550 ms 49.212.125.38
4 2026-08-25 01:28 639232172197053132
566 ms 49.212.125.38
3 2026-08-25 00:34 639232140250307418
555 ms 49.212.125.38
2 2026-08-25 00:17 639232129927860324
542 ms 49.212.125.38
1 2026-08-25 00:00 639232119551972438
273 ms 49.212.125.38