DNS response history for ns2.avbelize.com

ns2.avbelize.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-25. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 303 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.avbelize.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

303 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.240.205.231

Most recently resolved hosting IP on selected date

Successful Responses

35

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.avbelize.com

Showing DNS history for 2026-08-25 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
35 2026-08-25 12:23 639232566381512620
345 ms 66.240.205.231
34 2026-08-25 12:06 639232556111768563
11 ms 66.240.205.231
33 2026-08-25 11:49 639232545839529039
337 ms 66.240.205.231
32 2026-08-25 11:31 639232535349285207
344 ms 66.240.205.231
31 2026-08-25 11:14 639232524938080723
351 ms 66.240.205.231
30 2026-08-25 10:20 639232492740373468
16 ms 66.240.205.231
29 2026-08-25 10:03 639232482235303141
394 ms 66.240.205.231
28 2026-08-25 09:45 639232471861770303
338 ms 66.240.205.231
27 2026-08-25 09:28 639232461630217327
351 ms 66.240.205.231
26 2026-08-25 09:11 639232451282965990
361 ms 66.240.205.231
25 2026-08-25 08:54 639232440814614938
350 ms 66.240.205.231
24 2026-08-25 08:36 639232430410720425
362 ms 66.240.205.231
23 2026-08-25 08:19 639232420003096185
337 ms 66.240.205.231
22 2026-08-25 08:02 639232409467287444
339 ms 66.240.205.231
21 2026-08-25 07:44 639232399077195997
360 ms 66.240.205.231
20 2026-08-25 07:27 639232388731528337
17 ms 66.240.205.231
19 2026-08-25 07:09 639232378288598612
374 ms 66.240.205.231
18 2026-08-25 06:16 639232346196373643
355 ms 66.240.205.231
17 2026-08-25 05:59 639232336112370741
400 ms 66.240.205.231
16 2026-08-25 05:42 639232326146508970
361 ms 66.240.205.231
15 2026-08-25 05:26 639232316189381720
20 ms 66.240.205.231
14 2026-08-25 05:09 639232306217998913
332 ms 66.240.205.231
13 2026-08-25 04:52 639232296255744174
330 ms 66.240.205.231
12 2026-08-25 04:36 639232286095760789
367 ms 66.240.205.231
11 2026-08-25 04:19 639232276086186273
338 ms 66.240.205.231
10 2026-08-25 04:02 639232265900986425
350 ms 66.240.205.231
9 2026-08-25 03:45 639232255723518075
21 ms 66.240.205.231
8 2026-08-25 03:28 639232245484452890
349 ms 66.240.205.231
7 2026-08-25 03:11 639232235157175331
330 ms 66.240.205.231
6 2026-08-25 02:18 639232203197189095
369 ms 66.240.205.231
5 2026-08-25 02:00 639232192844564298
345 ms 66.240.205.231
4 2026-08-25 01:43 639232182496008942
331 ms 66.240.205.231
3 2026-08-25 01:26 639232172197053132
333 ms 66.240.205.231
2 2026-08-25 00:33 639232140250307418
340 ms 66.240.205.231
1 2026-08-25 00:16 639232129927860324
336 ms 66.240.205.231