DNS response history for zero2.w3space.net

zero2.w3space.net 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 27 DNS check records, 27 successful responses, 0 failed responses, and 313 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 zero2.w3space.net.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

313 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 08:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

194.163.176.190

Most recently resolved hosting IP on selected date

Successful Responses

27

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 zero2.w3space.net

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
27 2026-08-27 08:45 639234170713214496
9 ms 194.163.176.190
26 2026-08-27 08:28 639234160341037652
16 ms 194.163.176.190
25 2026-08-27 08:11 639234149799404224
7 ms 194.163.176.190
24 2026-08-27 07:53 639234139553286469
33 ms 194.163.176.190
23 2026-08-27 07:00 639234107183588293
15 ms 194.163.176.190
22 2026-08-27 06:42 639234096905435724
31 ms 194.163.176.190
21 2026-08-27 06:25 639234086579410775
8 ms 194.163.176.190
20 2026-08-27 06:08 639234076291157956
5 ms 194.163.176.190
19 2026-08-27 05:51 639234065981939454
27 ms 194.163.176.190
18 2026-08-27 05:34 639234055548642997
2028 ms 194.163.176.190
17 2026-08-27 05:16 639234045267979603
5 ms 194.163.176.190
16 2026-08-27 04:59 639234034999717463
5 ms 194.163.176.190
15 2026-08-27 04:42 639234024739225358
2021 ms 194.163.176.190
14 2026-08-27 04:25 639234014311170162
8 ms 194.163.176.190
13 2026-08-27 04:07 639234003806017640
15 ms 194.163.176.190
12 2026-08-27 03:50 639233993356203030
14 ms 194.163.176.190
11 2026-08-27 02:56 639233961301716608
7 ms 194.163.176.190
10 2026-08-27 02:39 639233950834200647
10 ms 194.163.176.190
9 2026-08-27 02:22 639233940431849026
48 ms 194.163.176.190
8 2026-08-27 02:04 639233930110596398
9 ms 194.163.176.190
7 2026-08-27 01:47 639233919705434540
10 ms 194.163.176.190
6 2026-08-27 01:30 639233909452807845
11 ms 194.163.176.190
5 2026-08-27 01:13 639233899096420820
7 ms 194.163.176.190
4 2026-08-27 00:55 639233888707824939
6 ms 194.163.176.190
3 2026-08-27 00:38 639233878461203802
39 ms 194.163.176.190
2 2026-08-27 00:21 639233868060868209
4044 ms 194.163.176.190
1 2026-08-27 00:03 639233857450922991
22 ms 194.163.176.190