DNS response history for ns2.hazuz.com

ns2.hazuz.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-26. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 289 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 ns2.hazuz.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

289 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

142.4.222.107

Most recently resolved hosting IP on selected date

Successful Responses

33

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 ns2.hazuz.com

Showing DNS history for 2026-08-26 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
33 2026-08-26 10:40 639233370841350248
218 ms 142.4.222.107
32 2026-08-26 10:23 639233360361507238
110 ms 142.4.222.107
31 2026-08-26 10:06 639233350067824371
221 ms 142.4.222.107
30 2026-08-26 09:49 639233339545274518
138 ms 142.4.222.107
29 2026-08-26 09:31 639233329214918079
111 ms 142.4.222.107
28 2026-08-26 09:14 639233318749762337
120 ms 142.4.222.107
27 2026-08-26 08:56 639233308387917838
219 ms 142.4.222.107
26 2026-08-26 08:39 639233297961740122
221 ms 142.4.222.107
25 2026-08-26 08:22 639233287487159094
2107 ms 142.4.222.107
24 2026-08-26 08:04 639233276995531707
225 ms 142.4.222.107
23 2026-08-26 07:47 639233266521568229
224 ms 142.4.222.107
22 2026-08-26 07:29 639233256081047431
222 ms 142.4.222.107
21 2026-08-26 06:35 639233223620132921
215 ms 142.4.222.107
20 2026-08-26 06:18 639233213287814244
115 ms 142.4.222.107
19 2026-08-26 06:01 639233202925983161
220 ms 142.4.222.107
18 2026-08-26 05:43 639233192644780696
7 ms 142.4.222.107
17 2026-08-26 05:26 639233182401183833
219 ms 142.4.222.107
16 2026-08-26 05:09 639233172074181051
220 ms 142.4.222.107
15 2026-08-26 04:52 639233161808421455
109 ms 142.4.222.107
14 2026-08-26 04:35 639233151357344052
216 ms 142.4.222.107
13 2026-08-26 04:17 639233141034116946
128 ms 142.4.222.107
12 2026-08-26 04:00 639233130828334142
2117 ms 142.4.222.107
11 2026-08-26 03:43 639233120373450007
117 ms 142.4.222.107
10 2026-08-26 03:26 639233110066216193
152 ms 142.4.222.107
9 2026-08-26 02:33 639233078065410564
219 ms 142.4.222.107
8 2026-08-26 02:15 639233067787457832
116 ms 142.4.222.107
7 2026-08-26 01:58 639233057501801162
217 ms 142.4.222.107
6 2026-08-26 01:41 639233047089431703
219 ms 142.4.222.107
5 2026-08-26 01:24 639233036754790688
157 ms 142.4.222.107
4 2026-08-26 01:07 639233026412602472
108 ms 142.4.222.107
3 2026-08-26 00:49 639233016064066127
215 ms 142.4.222.107
2 2026-08-26 00:32 639233005922655772
103 ms 142.4.222.107
1 2026-08-26 00:15 639232995672256907
220 ms 142.4.222.107