DNS response history for ns1.agilliz.com

ns1.agilliz.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 29 DNS check records, 29 successful responses, 0 failed responses, and 483 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.agilliz.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

483 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

108.167.132.109

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.agilliz.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
29 2026-08-26 09:32 639233329214918079
146 ms 108.167.132.109
28 2026-08-26 09:15 639233318749762337
283 ms 108.167.132.109
27 2026-08-26 08:58 639233308387917838
291 ms 108.167.132.109
26 2026-08-26 08:40 639233297961740122
2008 ms 108.167.132.109
25 2026-08-26 08:23 639233287487159094
143 ms 108.167.132.109
24 2026-08-26 08:05 639233276995531707
144 ms 108.167.132.109
23 2026-08-26 07:48 639233266521568229
2203 ms 108.167.132.109
22 2026-08-26 07:30 639233256081047431
282 ms 108.167.132.109
21 2026-08-26 06:37 639233223620132921
284 ms 108.167.132.109
20 2026-08-26 06:19 639233213287814244
151 ms 108.167.132.109
19 2026-08-26 06:02 639233202925983161
169 ms 108.167.132.109
18 2026-08-26 05:45 639233192644780696
149 ms 108.167.132.109
17 2026-08-26 05:27 639233182401183833
282 ms 108.167.132.109
16 2026-08-26 05:11 639233172074181051
148 ms 108.167.132.109
15 2026-08-26 04:53 639233161808421455
142 ms 108.167.132.109
14 2026-08-26 04:36 639233151357344052
141 ms 108.167.132.109
13 2026-08-26 04:19 639233141034116946
299 ms 108.167.132.109
12 2026-08-26 04:02 639233130828334142
33 ms 108.167.132.109
11 2026-08-26 03:44 639233120373450007
137 ms 108.167.132.109
10 2026-08-26 03:27 639233110066216193
2222 ms 108.167.132.109
9 2026-08-26 02:34 639233078065410564
291 ms 108.167.132.109
8 2026-08-26 02:17 639233067787457832
281 ms 108.167.132.109
7 2026-08-26 01:59 639233057501801162
9 ms 108.167.132.109
6 2026-08-26 01:42 639233047089431703
209 ms 108.167.132.109
5 2026-08-26 01:25 639233036754790688
293 ms 108.167.132.109
4 2026-08-26 01:08 639233026412602472
2312 ms 108.167.132.109
3 2026-08-26 00:50 639233016064066127
381 ms 108.167.132.109
2 2026-08-26 00:33 639233005922655772
283 ms 108.167.132.109
1 2026-08-26 00:16 639232995672256907
287 ms 108.167.132.109