DNS response history for ns2.all-in-1.com

ns2.all-in-1.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 27 DNS check records, 27 successful responses, 0 failed responses, and 264 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.all-in-1.com.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

264 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

68.177.108.20

Most recently resolved hosting IP on selected date

Successful Responses

27

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.all-in-1.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
27 2026-08-26 08:41 639233297961740122
319 ms 68.177.108.20
26 2026-08-26 08:23 639233287487159094
325 ms 68.177.108.20
25 2026-08-26 08:06 639233276995531707
159 ms 68.177.108.20
24 2026-08-26 07:49 639233266521568229
321 ms 68.177.108.20
23 2026-08-26 07:31 639233256081047431
327 ms 68.177.108.20
22 2026-08-26 06:37 639233223620132921
346 ms 68.177.108.20
21 2026-08-26 06:20 639233213287814244
212 ms 68.177.108.20
20 2026-08-26 06:02 639233202925983161
339 ms 68.177.108.20
19 2026-08-26 05:45 639233192644780696
328 ms 68.177.108.20
18 2026-08-26 05:28 639233182401183833
325 ms 68.177.108.20
17 2026-08-26 05:11 639233172074181051
316 ms 68.177.108.20
16 2026-08-26 04:54 639233161808421455
324 ms 68.177.108.20
15 2026-08-26 04:37 639233151357344052
162 ms 68.177.108.20
14 2026-08-26 04:19 639233141034116946
323 ms 68.177.108.20
13 2026-08-26 04:02 639233130828334142
174 ms 68.177.108.20
12 2026-08-26 03:45 639233120373450007
320 ms 68.177.108.20
11 2026-08-26 03:28 639233110066216193
323 ms 68.177.108.20
10 2026-08-26 02:34 639233078065410564
166 ms 68.177.108.20
9 2026-08-26 02:17 639233067787457832
209 ms 68.177.108.20
8 2026-08-26 02:00 639233057501801162
162 ms 68.177.108.20
7 2026-08-26 01:43 639233047089431703
335 ms 68.177.108.20
6 2026-08-26 01:26 639233036754790688
334 ms 68.177.108.20
5 2026-08-26 01:08 639233026412602472
173 ms 68.177.108.20
4 2026-08-26 00:51 639233016064066127
320 ms 68.177.108.20
3 2026-08-26 00:34 639233005922655772
172 ms 68.177.108.20
2 2026-08-26 00:17 639232995672256907
157 ms 68.177.108.20
1 2026-08-26 00:00 639232985300872416
160 ms 68.177.108.20