DNS response history for ns4.ableteam.com

ns4.ableteam.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 298 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 ns4.ableteam.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

298 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.81.180.115

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 ns4.ableteam.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:36 639232576780683689
87 ms 208.81.180.115
35 2026-08-25 12:18 639232566381512620
103 ms 208.81.180.115
34 2026-08-25 12:01 639232556111768563
123 ms 208.81.180.115
33 2026-08-25 11:44 639232545839529039
613 ms 208.81.180.115
32 2026-08-25 11:27 639232535349285207
171 ms 208.81.180.115
31 2026-08-25 11:09 639232524938080723
280 ms 208.81.180.115
30 2026-08-25 10:15 639232492740373468
28 ms 208.81.180.115
29 2026-08-25 09:58 639232482235303141
42 ms 208.81.180.115
28 2026-08-25 09:41 639232471861770303
561 ms 208.81.180.115
27 2026-08-25 09:24 639232461630217327
513 ms 208.81.180.115
26 2026-08-25 09:06 639232451282965990
19 ms 208.81.180.115
25 2026-08-25 08:49 639232440814614938
31 ms 208.81.180.115
24 2026-08-25 08:32 639232430410720425
586 ms 208.81.180.115
23 2026-08-25 08:14 639232420003096185
42 ms 208.81.180.115
22 2026-08-25 07:57 639232409467287444
137 ms 208.81.180.115
21 2026-08-25 07:39 639232399077195997
37 ms 208.81.180.115
20 2026-08-25 07:22 639232388731528337
272 ms 208.81.180.115
19 2026-08-25 07:05 639232378288598612
2159 ms 208.81.180.115
18 2026-08-25 06:11 639232346196373643
101 ms 208.81.180.115
17 2026-08-25 05:54 639232336112370741
3 ms 208.81.180.115
16 2026-08-25 05:38 639232326146508970
17 ms 208.81.180.115
15 2026-08-25 05:21 639232316189381720
242 ms 208.81.180.115
14 2026-08-25 05:05 639232306217998913
506 ms 208.81.180.115
13 2026-08-25 04:48 639232296255744174
2 ms 208.81.180.115
12 2026-08-25 04:31 639232286095760789
32 ms 208.81.180.115
11 2026-08-25 04:14 639232276086186273
166 ms 208.81.180.115
10 2026-08-25 03:57 639232265900986425
506 ms 208.81.180.115
9 2026-08-25 03:40 639232255723518075
186 ms 208.81.180.115
8 2026-08-25 03:23 639232245484452890
2079 ms 208.81.180.115
7 2026-08-25 03:06 639232235157175331
95 ms 208.81.180.115
6 2026-08-25 02:13 639232203197189095
604 ms 208.81.180.115
5 2026-08-25 01:56 639232192844564298
3 ms 208.81.180.115
4 2026-08-25 01:38 639232182496008942
97 ms 208.81.180.115
3 2026-08-25 01:21 639232172197053132
173 ms 208.81.180.115
2 2026-08-25 00:28 639232140250307418
100 ms 208.81.180.115
1 2026-08-25 00:11 639232129927860324
20 ms 208.81.180.115