History for ns.digiled.com
Domain: digiled.com • Tracking since 2026-08-04 23:25 UTC
DNS response history for ns.digiled.com
ns.digiled.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-24. For this date, NameServerHistory found 20 DNS check records, 20 successful responses, 0 failed responses, and 845 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 ns.digiled.com.
Records on Selected Date
20
Historical checks stored for this nameserver on selected date
Average Latency
845 ms
Calculated from available response records
Latest Check on Selected Date
2026-08-24 03:49
All timestamps shown in UTC
Latest Resolved IP on Selected Date
185.194.168.177
Most recently resolved hosting IP on selected date
Successful Responses
20
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 ns.digiled.com
Showing DNS history for 2026-08-24 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 |
|---|---|---|---|---|---|
| 20 | 2026-08-24 03:49 | 639231395791246644 |
|
637 ms | 185.194.168.177 |
| 19 | 2026-08-24 03:49 | 639231395791246644 |
|
637 ms | 192.168.68.20 |
| 18 | 2026-08-24 03:33 | 639231386075551458 |
|
50 ms | 185.194.168.177 |
| 17 | 2026-08-24 03:33 | 639231386075551458 |
|
50 ms | 192.168.68.20 |
| 16 | 2026-08-24 03:17 | 639231376208713791 |
|
50 ms | 185.194.168.177 |
| 15 | 2026-08-24 03:17 | 639231376208713791 |
|
50 ms | 192.168.68.20 |
| 14 | 2026-08-24 03:00 | 639231366170589276 |
|
10 ms | 192.168.68.20 |
| 13 | 2026-08-24 03:00 | 639231366170589276 |
|
10 ms | 185.194.168.177 |
| 12 | 2026-08-24 02:08 | 639231334732159368 |
|
11 ms | 185.194.168.177 |
| 11 | 2026-08-24 02:08 | 639231334732159368 |
|
11 ms | 192.168.68.20 |
| 10 | 2026-08-24 01:51 | 639231325035670078 |
|
50 ms | 192.168.68.20 |
| 9 | 2026-08-24 01:51 | 639231325035670078 |
|
50 ms | 185.194.168.177 |
| 8 | 2026-08-24 01:35 | 639231315132253837 |
|
2 ms | 185.194.168.177 |
| 7 | 2026-08-24 01:35 | 639231315132253837 |
|
2 ms | 192.168.68.20 |
| 6 | 2026-08-24 01:18 | 639231305014280808 |
|
34 ms | 192.168.68.20 |
| 5 | 2026-08-24 01:18 | 639231305014280808 |
|
34 ms | 185.194.168.177 |
| 4 | 2026-08-24 00:26 | 639231273779380675 |
|
3575 ms | 192.168.68.20 |
| 3 | 2026-08-24 00:26 | 639231273779380675 |
|
3575 ms | 185.194.168.177 |
| 2 | 2026-08-24 00:10 | 639231264180839154 |
|
4027 ms | 185.194.168.177 |
| 1 | 2026-08-24 00:10 | 639231264180839154 |
|
4027 ms | 192.168.68.20 |