History for ns1.jamlinked.com.directideleteddomain.info.directideleteddomain.info
Domain: directideleteddomain.info • Tracking since 2026-08-04 23:25 UTC
DNS response history for ns1.jamlinked.com.directideleteddomain.info.directideleteddomain.info
ns1.jamlinked.com.directideleteddomain.info.directideleteddomain.info 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 17 DNS check records, 16 successful responses, 1 failed responses, and 1295 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.jamlinked.com.directideleteddomain.info.directideleteddomain.info.
Records on Selected Date
17
Historical checks stored for this nameserver on selected date
Average Latency
1295 ms
Calculated from available response records
Latest Check on Selected Date
2026-08-25 05:46
All timestamps shown in UTC
Latest Resolved IP on Selected Date
208.91.197.66
Most recently resolved hosting IP on selected date
Successful Responses
16
Checks that returned a measurable response
Failed Responses
1
Checks with no response or no returned latency
Failure Rate
6%
Based on the selected date history
Selected Date Status
Responsive
At least one successful response exists on selected date
History for ns1.jamlinked.com.directideleteddomain.info.directideleteddomain.info
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 |
|---|---|---|---|---|---|
| 17 | 2026-08-25 05:46 | 639232326146508970 |
|
721 ms | 208.91.197.66 |
| 16 | 2026-08-25 05:30 | 639232316189381720 |
|
1237 ms | 208.91.197.66 |
| 15 | 2026-08-25 05:13 | 639232306217998913 |
|
1216 ms | 208.91.197.66 |
| 14 | 2026-08-25 04:56 | 639232296255744174 |
|
1392 ms | 208.91.197.66 |
| 13 | 2026-08-25 04:40 | 639232286095760789 |
|
716 ms | 208.91.197.66 |
| 12 | 2026-08-25 04:23 | 639232276086186273 |
|
4143 ms | 208.91.197.66 |
| 11 | 2026-08-25 04:06 | 639232265900986425 |
|
717 ms | 208.91.197.66 |
| 10 | 2026-08-25 03:49 | 639232255723518075 |
|
145 ms | 208.91.197.66 |
| 9 | 2026-08-25 03:32 | 639232245484452890 |
|
1214 ms | 208.91.197.66 |
| 8 | 2026-08-25 03:15 | 639232235157175331 |
|
4642 ms | 208.91.197.66 |
| 7 | 2026-08-25 02:22 | 639232203197189095 |
|
1230 ms | 208.91.197.66 |
| 6 | 2026-08-25 02:05 | 639232192844564298 |
|
711 ms | 208.91.197.66 |
| 5 | 2026-08-25 01:47 | 639232182496008942 |
|
- | |
| 4 | 2026-08-25 01:30 | 639232172197053132 |
|
1051 ms | 208.91.197.66 |
| 3 | 2026-08-25 00:36 | 639232140250307418 |
|
136 ms | 208.91.197.66 |
| 2 | 2026-08-25 00:20 | 639232129927860324 |
|
718 ms | 208.91.197.66 |
| 1 | 2026-08-25 00:02 | 639232119551972438 |
|
728 ms | 208.91.197.66 |