DNS response history for ns03.nishikawasangyo.co.jp

ns03.nishikawasangyo.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-27. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 576 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 ns03.nishikawasangyo.co.jp.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

576 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:28

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.248.5.5

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 ns03.nishikawasangyo.co.jp

Showing DNS history for 2026-08-27 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-27 12:28 639234296664302575
605 ms 202.248.5.5
36 2026-08-27 12:11 639234286253196126
711 ms 202.248.5.5
35 2026-08-27 11:17 639234253963286387
557 ms 202.248.5.5
34 2026-08-27 11:00 639234243654907465
386 ms 202.248.5.5
33 2026-08-27 10:43 639234233269654413
603 ms 202.248.5.5
32 2026-08-27 10:25 639234222943951923
531 ms 202.248.5.5
31 2026-08-27 10:08 639234212558002823
1683 ms 202.248.5.5
30 2026-08-27 09:51 639234202117531850
673 ms 202.248.5.5
29 2026-08-27 09:33 639234191649612722
256 ms 202.248.5.5
28 2026-08-27 09:16 639234181105879568
802 ms 202.248.5.5
27 2026-08-27 08:58 639234170713214496
726 ms 202.248.5.5
26 2026-08-27 08:41 639234160341037652
511 ms 202.248.5.5
25 2026-08-27 08:24 639234149799404224
509 ms 202.248.5.5
24 2026-08-27 08:06 639234139553286469
727 ms 202.248.5.5
23 2026-08-27 07:13 639234107183588293
507 ms 202.248.5.5
22 2026-08-27 06:55 639234096905435724
856 ms 202.248.5.5
21 2026-08-27 06:38 639234086579410775
529 ms 202.248.5.5
20 2026-08-27 06:21 639234076291157956
502 ms 202.248.5.5
19 2026-08-27 06:04 639234065981939454
245 ms 202.248.5.5
18 2026-08-27 05:47 639234055548642997
2257 ms 202.248.5.5
17 2026-08-27 05:29 639234045267979603
252 ms 202.248.5.5
16 2026-08-27 05:12 639234034999717463
518 ms 202.248.5.5
15 2026-08-27 04:55 639234024739225358
527 ms 202.248.5.5
14 2026-08-27 04:38 639234014311170162
525 ms 202.248.5.5
13 2026-08-27 04:20 639234003806017640
255 ms 202.248.5.5
12 2026-08-27 04:03 639233993356203030
517 ms 202.248.5.5
11 2026-08-27 03:10 639233961301716608
695 ms 202.248.5.5
10 2026-08-27 02:52 639233950834200647
522 ms 202.248.5.5
9 2026-08-27 02:35 639233940431849026
530 ms 202.248.5.5
8 2026-08-27 02:17 639233930110596398
506 ms 202.248.5.5
7 2026-08-27 02:00 639233919705434540
259 ms 202.248.5.5
6 2026-08-27 01:43 639233909452807845
249 ms 202.248.5.5
5 2026-08-27 01:26 639233899096420820
245 ms 202.248.5.5
4 2026-08-27 01:09 639233888707824939
495 ms 202.248.5.5
3 2026-08-27 00:51 639233878461203802
259 ms 202.248.5.5
2 2026-08-27 00:34 639233868060868209
253 ms 202.248.5.5
1 2026-08-27 00:17 639233857450922991
525 ms 202.248.5.5