DNS response history for galileo.tam.ne.jp

galileo.tam.ne.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 32 DNS check records, 32 successful responses, 0 failed responses, and 561 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 galileo.tam.ne.jp.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

561 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.133.160.2

Most recently resolved hosting IP on selected date

Successful Responses

32

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 galileo.tam.ne.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
32 2026-08-25 11:15 639232524938080723
493 ms 210.133.160.2
31 2026-08-25 10:22 639232492740373468
555 ms 210.133.160.2
30 2026-08-25 10:05 639232482235303141
576 ms 210.133.160.2
29 2026-08-25 09:47 639232471861770303
599 ms 210.133.160.2
28 2026-08-25 09:30 639232461630217327
548 ms 210.133.160.2
27 2026-08-25 09:13 639232451282965990
478 ms 210.133.160.2
26 2026-08-25 08:55 639232440814614938
495 ms 210.133.160.2
25 2026-08-25 08:38 639232430410720425
449 ms 210.133.160.2
24 2026-08-25 08:21 639232420003096185
733 ms 210.133.160.2
23 2026-08-25 08:03 639232409467287444
471 ms 210.133.160.2
22 2026-08-25 07:46 639232399077195997
549 ms 210.133.160.2
21 2026-08-25 07:28 639232388731528337
560 ms 210.133.160.2
20 2026-08-25 07:11 639232378288598612
480 ms 210.133.160.2
19 2026-08-25 06:17 639232346196373643
550 ms 210.133.160.2
18 2026-08-25 06:00 639232336112370741
852 ms 210.133.160.2
17 2026-08-25 05:44 639232326146508970
286 ms 210.133.160.2
16 2026-08-25 05:27 639232316189381720
530 ms 210.133.160.2
15 2026-08-25 05:11 639232306217998913
543 ms 210.133.160.2
14 2026-08-25 04:54 639232296255744174
555 ms 210.133.160.2
13 2026-08-25 04:37 639232286095760789
551 ms 210.133.160.2
12 2026-08-25 04:20 639232276086186273
624 ms 210.133.160.2
11 2026-08-25 04:04 639232265900986425
565 ms 210.133.160.2
10 2026-08-25 03:47 639232255723518075
576 ms 210.133.160.2
9 2026-08-25 03:30 639232245484452890
836 ms 210.133.160.2
8 2026-08-25 03:12 639232235157175331
554 ms 210.133.160.2
7 2026-08-25 02:19 639232203197189095
593 ms 210.133.160.2
6 2026-08-25 02:02 639232192844564298
571 ms 210.133.160.2
5 2026-08-25 01:45 639232182496008942
545 ms 210.133.160.2
4 2026-08-25 01:27 639232172197053132
560 ms 210.133.160.2
3 2026-08-25 00:34 639232140250307418
548 ms 210.133.160.2
2 2026-08-25 00:17 639232129927860324
554 ms 210.133.160.2
1 2026-08-25 00:00 639232119551972438
558 ms 210.133.160.2