DNS response history for ns3.hasweb.com

ns3.hasweb.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-27. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 101 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 ns3.hasweb.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

101 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

72.29.75.16

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 ns3.hasweb.com

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:23 639234296664302575
93 ms 72.29.75.16
36 2026-08-27 12:06 639234286253196126
10 ms 72.29.75.16
35 2026-08-27 11:12 639234253963286387
4 ms 72.29.75.16
34 2026-08-27 10:55 639234243654907465
91 ms 72.29.75.16
33 2026-08-27 10:38 639234233269654413
102 ms 72.29.75.16
32 2026-08-27 10:21 639234222943951923
196 ms 72.29.75.16
31 2026-08-27 10:03 639234212558002823
97 ms 72.29.75.16
30 2026-08-27 09:46 639234202117531850
152 ms 72.29.75.16
29 2026-08-27 09:29 639234191649612722
91 ms 72.29.75.16
28 2026-08-27 09:11 639234181105879568
93 ms 72.29.75.16
27 2026-08-27 08:54 639234170713214496
95 ms 72.29.75.16
26 2026-08-27 08:36 639234160341037652
102 ms 72.29.75.16
25 2026-08-27 08:19 639234149799404224
89 ms 72.29.75.16
24 2026-08-27 08:02 639234139553286469
93 ms 72.29.75.16
23 2026-08-27 07:08 639234107183588293
193 ms 72.29.75.16
22 2026-08-27 06:51 639234096905435724
98 ms 72.29.75.16
21 2026-08-27 06:33 639234086579410775
63 ms 72.29.75.16
20 2026-08-27 06:16 639234076291157956
8 ms 72.29.75.16
19 2026-08-27 05:59 639234065981939454
127 ms 72.29.75.16
18 2026-08-27 05:42 639234055548642997
95 ms 72.29.75.16
17 2026-08-27 05:25 639234045267979603
91 ms 72.29.75.16
16 2026-08-27 05:08 639234034999717463
6 ms 72.29.75.16
15 2026-08-27 04:50 639234024739225358
89 ms 72.29.75.16
14 2026-08-27 04:33 639234014311170162
103 ms 72.29.75.16
13 2026-08-27 04:16 639234003806017640
184 ms 72.29.75.16
12 2026-08-27 03:58 639233993356203030
224 ms 72.29.75.16
11 2026-08-27 03:05 639233961301716608
118 ms 72.29.75.16
10 2026-08-27 02:48 639233950834200647
222 ms 72.29.75.16
9 2026-08-27 02:30 639233940431849026
88 ms 72.29.75.16
8 2026-08-27 02:13 639233930110596398
104 ms 72.29.75.16
7 2026-08-27 01:56 639233919705434540
102 ms 72.29.75.16
6 2026-08-27 01:38 639233909452807845
90 ms 72.29.75.16
5 2026-08-27 01:21 639233899096420820
92 ms 72.29.75.16
4 2026-08-27 01:04 639233888707824939
117 ms 72.29.75.16
3 2026-08-27 00:47 639233878461203802
5 ms 72.29.75.16
2 2026-08-27 00:29 639233868060868209
90 ms 72.29.75.16
1 2026-08-27 00:12 639233857450922991
121 ms 72.29.75.16