DNS response history for dns2.digilab.co.jp

dns2.digilab.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 36 DNS check records, 36 successful responses, 0 failed responses, and 1657 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 dns2.digilab.co.jp.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

1657 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:18

All timestamps shown in UTC

Latest Resolved IP on Selected Date

211.15.55.77

Most recently resolved hosting IP on selected date

Successful Responses

36

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 dns2.digilab.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
36 2026-08-27 11:18 639234253963286387
1725 ms 211.15.55.77
35 2026-08-27 11:01 639234243654907465
1708 ms 211.15.55.77
34 2026-08-27 10:44 639234233269654413
1711 ms 211.15.55.77
33 2026-08-27 10:27 639234222943951923
1699 ms 211.15.55.77
32 2026-08-27 10:10 639234212558002823
1698 ms 211.15.55.77
31 2026-08-27 09:52 639234202117531850
1701 ms 211.15.55.77
30 2026-08-27 09:35 639234191649612722
1710 ms 211.15.55.77
29 2026-08-27 09:17 639234181105879568
1724 ms 211.15.55.77
28 2026-08-27 09:00 639234170713214496
1732 ms 211.15.55.77
27 2026-08-27 08:43 639234160341037652
1723 ms 211.15.55.77
26 2026-08-27 08:25 639234149799404224
1731 ms 211.15.55.77
25 2026-08-27 08:08 639234139553286469
1143 ms 211.15.55.77
24 2026-08-27 07:14 639234107183588293
1721 ms 211.15.55.77
23 2026-08-27 06:57 639234096905435724
1971 ms 211.15.55.77
22 2026-08-27 06:39 639234086579410775
1714 ms 211.15.55.77
21 2026-08-27 06:22 639234076291157956
1703 ms 211.15.55.77
20 2026-08-27 06:05 639234065981939454
4256 ms 211.15.55.77
19 2026-08-27 05:48 639234055548642997
1727 ms 211.15.55.77
18 2026-08-27 05:31 639234045267979603
1112 ms 211.15.55.77
17 2026-08-27 05:13 639234034999717463
1689 ms 211.15.55.77
16 2026-08-27 04:56 639234024739225358
3 ms 211.15.55.77
15 2026-08-27 04:39 639234014311170162
1722 ms 211.15.55.77
14 2026-08-27 04:22 639234003806017640
1718 ms 211.15.55.77
13 2026-08-27 04:04 639233993356203030
1729 ms 211.15.55.77
12 2026-08-27 03:11 639233961301716608
1805 ms 211.15.55.77
11 2026-08-27 02:54 639233950834200647
1963 ms 211.15.55.77
10 2026-08-27 02:36 639233940431849026
1725 ms 211.15.55.77
9 2026-08-27 02:19 639233930110596398
1706 ms 211.15.55.77
8 2026-08-27 02:01 639233919705434540
3 ms 211.15.55.77
7 2026-08-27 01:44 639233909452807845
1695 ms 211.15.55.77
6 2026-08-27 01:27 639233899096420820
1134 ms 211.15.55.77
5 2026-08-27 01:10 639233888707824939
1702 ms 211.15.55.77
4 2026-08-27 00:52 639233878461203802
1721 ms 211.15.55.77
3 2026-08-27 00:35 639233868060868209
1699 ms 211.15.55.77
2 2026-08-27 00:18 639233857450922991
1704 ms 211.15.55.77
1 2026-08-27 00:00 639233846871926285
1728 ms 211.15.55.77