DNS response history for ns1.horiba.co.jp

ns1.horiba.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 29 DNS check records, 29 successful responses, 0 failed responses, and 582 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.horiba.co.jp.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

582 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.250.32.2

Most recently resolved hosting IP on selected date

Successful Responses

29

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.horiba.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
29 2026-08-27 09:34 639234191649612722
600 ms 202.250.32.2
28 2026-08-27 09:16 639234181105879568
552 ms 202.250.32.2
27 2026-08-27 08:59 639234170713214496
590 ms 202.250.32.2
26 2026-08-27 08:41 639234160341037652
645 ms 202.250.32.2
25 2026-08-27 08:24 639234149799404224
614 ms 202.250.32.2
24 2026-08-27 08:06 639234139553286469
604 ms 202.250.32.2
23 2026-08-27 07:13 639234107183588293
577 ms 202.250.32.2
22 2026-08-27 06:56 639234096905435724
545 ms 202.250.32.2
21 2026-08-27 06:38 639234086579410775
576 ms 202.250.32.2
20 2026-08-27 06:21 639234076291157956
566 ms 202.250.32.2
19 2026-08-27 06:04 639234065981939454
593 ms 202.250.32.2
18 2026-08-27 05:47 639234055548642997
551 ms 202.250.32.2
17 2026-08-27 05:29 639234045267979603
606 ms 202.250.32.2
16 2026-08-27 05:12 639234034999717463
605 ms 202.250.32.2
15 2026-08-27 04:55 639234024739225358
610 ms 202.250.32.2
14 2026-08-27 04:38 639234014311170162
621 ms 202.250.32.2
13 2026-08-27 04:21 639234003806017640
602 ms 202.250.32.2
12 2026-08-27 04:03 639233993356203030
571 ms 202.250.32.2
11 2026-08-27 03:10 639233961301716608
11 ms 202.250.32.2
10 2026-08-27 02:52 639233950834200647
591 ms 202.250.32.2
9 2026-08-27 02:35 639233940431849026
837 ms 202.250.32.2
8 2026-08-27 02:18 639233930110596398
563 ms 202.250.32.2
7 2026-08-27 02:00 639233919705434540
579 ms 202.250.32.2
6 2026-08-27 01:43 639233909452807845
834 ms 202.250.32.2
5 2026-08-27 01:26 639233899096420820
551 ms 202.250.32.2
4 2026-08-27 01:09 639233888707824939
562 ms 202.250.32.2
3 2026-08-27 00:51 639233878461203802
563 ms 202.250.32.2
2 2026-08-27 00:34 639233868060868209
588 ms 202.250.32.2
1 2026-08-27 00:17 639233857450922991
568 ms 202.250.32.2