DNS response history for ns2.avitalweb.com

ns2.avitalweb.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 36 DNS check records, 36 successful responses, 0 failed responses, and 383 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.avitalweb.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

383 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.28.17.147

Most recently resolved hosting IP on selected date

Successful Responses

36

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.avitalweb.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
36 2026-08-25 12:38 639232576780683689
131 ms 50.28.17.147
35 2026-08-25 12:20 639232566381512620
125 ms 50.28.17.147
34 2026-08-25 12:03 639232556111768563
115 ms 50.28.17.147
33 2026-08-25 11:46 639232545839529039
2128 ms 50.28.17.147
32 2026-08-25 11:28 639232535349285207
125 ms 50.28.17.147
31 2026-08-25 11:11 639232524938080723
124 ms 50.28.17.147
30 2026-08-25 10:17 639232492740373468
2122 ms 50.28.17.147
29 2026-08-25 10:00 639232482235303141
118 ms 50.28.17.147
28 2026-08-25 09:43 639232471861770303
164 ms 50.28.17.147
27 2026-08-25 09:25 639232461630217327
238 ms 50.28.17.147
26 2026-08-25 09:08 639232451282965990
250 ms 50.28.17.147
25 2026-08-25 08:51 639232440814614938
229 ms 50.28.17.147
24 2026-08-25 08:33 639232430410720425
241 ms 50.28.17.147
23 2026-08-25 08:16 639232420003096185
231 ms 50.28.17.147
22 2026-08-25 07:59 639232409467287444
149 ms 50.28.17.147
21 2026-08-25 07:41 639232399077195997
236 ms 50.28.17.147
20 2026-08-25 07:24 639232388731528337
247 ms 50.28.17.147
19 2026-08-25 07:07 639232378288598612
236 ms 50.28.17.147
18 2026-08-25 06:13 639232346196373643
118 ms 50.28.17.147
17 2026-08-25 05:56 639232336112370741
121 ms 50.28.17.147
16 2026-08-25 05:40 639232326146508970
172 ms 50.28.17.147
15 2026-08-25 05:23 639232316189381720
249 ms 50.28.17.147
14 2026-08-25 05:06 639232306217998913
116 ms 50.28.17.147
13 2026-08-25 04:50 639232296255744174
109 ms 50.28.17.147
12 2026-08-25 04:33 639232286095760789
116 ms 50.28.17.147
11 2026-08-25 04:16 639232276086186273
2155 ms 50.28.17.147
10 2026-08-25 03:59 639232265900986425
122 ms 50.28.17.147
9 2026-08-25 03:42 639232255723518075
116 ms 50.28.17.147
8 2026-08-25 03:25 639232245484452890
117 ms 50.28.17.147
7 2026-08-25 03:08 639232235157175331
2150 ms 50.28.17.147
6 2026-08-25 02:15 639232203197189095
115 ms 50.28.17.147
5 2026-08-25 01:58 639232192844564298
120 ms 50.28.17.147
4 2026-08-25 01:40 639232182496008942
239 ms 50.28.17.147
3 2026-08-25 01:23 639232172197053132
110 ms 50.28.17.147
2 2026-08-25 00:30 639232140250307418
112 ms 50.28.17.147
1 2026-08-25 00:13 639232129927860324
228 ms 50.28.17.147