DNS response history for ns1.digital.tel

ns1.digital.tel 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 33 DNS check records, 33 successful responses, 0 failed responses, and 336 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.digital.tel.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

336 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

170.64.160.33

Most recently resolved hosting IP on selected date

Successful Responses

33

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.digital.tel

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
33 2026-08-26 10:27 639233360361507238
567 ms 170.64.160.33
32 2026-08-26 10:10 639233350067824371
564 ms 170.64.160.33
31 2026-08-26 09:52 639233339545274518
560 ms 170.64.160.33
30 2026-08-26 09:35 639233329214918079
568 ms 170.64.160.33
29 2026-08-26 09:18 639233318749762337
275 ms 170.64.160.33
28 2026-08-26 09:00 639233308387917838
278 ms 170.64.160.33
27 2026-08-26 08:43 639233297961740122
3 ms 170.64.160.33
26 2026-08-26 08:25 639233287487159094
3 ms 170.64.160.33
25 2026-08-26 08:08 639233276995531707
6 ms 170.64.160.33
24 2026-08-26 07:50 639233266521568229
554 ms 170.64.160.33
23 2026-08-26 07:33 639233256081047431
304 ms 170.64.160.33
22 2026-08-26 06:39 639233223620132921
567 ms 170.64.160.33
21 2026-08-26 06:22 639233213287814244
273 ms 170.64.160.33
20 2026-08-26 06:04 639233202925983161
557 ms 170.64.160.33
19 2026-08-26 05:47 639233192644780696
3 ms 170.64.160.33
18 2026-08-26 05:30 639233182401183833
2 ms 170.64.160.33
17 2026-08-26 05:13 639233172074181051
568 ms 170.64.160.33
16 2026-08-26 04:56 639233161808421455
4 ms 170.64.160.33
15 2026-08-26 04:39 639233151357344052
2 ms 170.64.160.33
14 2026-08-26 04:21 639233141034116946
558 ms 170.64.160.33
13 2026-08-26 04:04 639233130828334142
562 ms 170.64.160.33
12 2026-08-26 03:47 639233120373450007
564 ms 170.64.160.33
11 2026-08-26 03:30 639233110066216193
563 ms 170.64.160.33
10 2026-08-26 02:36 639233078065410564
277 ms 170.64.160.33
9 2026-08-26 02:19 639233067787457832
381 ms 170.64.160.33
8 2026-08-26 02:02 639233057501801162
7 ms 170.64.160.33
7 2026-08-26 01:45 639233047089431703
558 ms 170.64.160.33
6 2026-08-26 01:28 639233036754790688
269 ms 170.64.160.33
5 2026-08-26 01:10 639233026412602472
564 ms 170.64.160.33
4 2026-08-26 00:53 639233016064066127
561 ms 170.64.160.33
3 2026-08-26 00:36 639233005922655772
561 ms 170.64.160.33
2 2026-08-26 00:19 639232995672256907
2 ms 170.64.160.33
1 2026-08-26 00:02 639232985300872416
3 ms 170.64.160.33