DNS response history for g4svr.ashizuri.com

g4svr.ashizuri.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-25. For this date, NameServerHistory found 22 DNS check records, 22 successful responses, 0 failed responses, and 678 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 g4svr.ashizuri.com.
Records on Selected Date

22

Historical checks stored for this nameserver on selected date

Average Latency

678 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 07:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.140.42.201

Most recently resolved hosting IP on selected date

Successful Responses

22

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 g4svr.ashizuri.com

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
22 2026-08-25 07:46 639232399077195997
2293 ms 210.140.42.201
21 2026-08-25 07:28 639232388731528337
510 ms 210.140.42.201
20 2026-08-25 07:11 639232378288598612
522 ms 210.140.42.201
19 2026-08-25 06:17 639232346196373643
519 ms 210.140.42.201
18 2026-08-25 06:00 639232336112370741
516 ms 210.140.42.201
17 2026-08-25 05:44 639232326146508970
507 ms 210.140.42.201
16 2026-08-25 05:27 639232316189381720
518 ms 210.140.42.201
15 2026-08-25 05:11 639232306217998913
566 ms 210.140.42.201
14 2026-08-25 04:54 639232296255744174
513 ms 210.140.42.201
13 2026-08-25 04:37 639232286095760789
510 ms 210.140.42.201
12 2026-08-25 04:20 639232276086186273
508 ms 210.140.42.201
11 2026-08-25 04:03 639232265900986425
510 ms 210.140.42.201
10 2026-08-25 03:47 639232255723518075
502 ms 210.140.42.201
9 2026-08-25 03:30 639232245484452890
2361 ms 210.140.42.201
8 2026-08-25 03:12 639232235157175331
509 ms 210.140.42.201
7 2026-08-25 02:19 639232203197189095
521 ms 210.140.42.201
6 2026-08-25 02:02 639232192844564298
498 ms 210.140.42.201
5 2026-08-25 01:45 639232182496008942
525 ms 210.140.42.201
4 2026-08-25 01:27 639232172197053132
502 ms 210.140.42.201
3 2026-08-25 00:34 639232140250307418
497 ms 210.140.42.201
2 2026-08-25 00:17 639232129927860324
494 ms 210.140.42.201
1 2026-08-25 00:00 639232119551972438
506 ms 210.140.42.201