DNS response history for ns1.zapzonemedia.com.directideleteddomain.com

ns1.zapzonemedia.com.directideleteddomain.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-27. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 2397 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.zapzonemedia.com.directideleteddomain.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

2397 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.91.197.7

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.zapzonemedia.com.directideleteddomain.com

Showing DNS history for 2026-08-27 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-27 10:27 639234222943951923
1926 ms 208.91.197.7
32 2026-08-27 10:10 639234212558002823
2381 ms 208.91.197.7
31 2026-08-27 09:53 639234202117531850
1211 ms 208.91.197.7
30 2026-08-27 09:35 639234191649612722
2259 ms 208.91.197.7
29 2026-08-27 09:18 639234181105879568
3665 ms 208.91.197.7
28 2026-08-27 09:00 639234170713214496
2257 ms 208.91.197.7
27 2026-08-27 08:43 639234160341037652
3771 ms 208.91.197.7
26 2026-08-27 08:26 639234149799404224
2376 ms 208.91.197.7
25 2026-08-27 08:08 639234139553286469
2254 ms 208.91.197.7
24 2026-08-27 07:14 639234107183588293
2359 ms 208.91.197.7
23 2026-08-27 06:57 639234096905435724
4131 ms 208.91.197.7
22 2026-08-27 06:40 639234086579410775
2352 ms 208.91.197.7
21 2026-08-27 06:23 639234076291157956
2362 ms 208.91.197.7
20 2026-08-27 06:06 639234065981939454
1207 ms 208.91.197.7
19 2026-08-27 05:48 639234055548642997
4133 ms 208.91.197.7
18 2026-08-27 05:31 639234045267979603
4134 ms 208.91.197.7
17 2026-08-27 05:14 639234034999717463
2296 ms 208.91.197.7
16 2026-08-27 04:57 639234024739225358
2248 ms 208.91.197.7
15 2026-08-27 04:40 639234014311170162
2258 ms 208.91.197.7
14 2026-08-27 04:22 639234003806017640
2139 ms 208.91.197.7
13 2026-08-27 04:05 639233993356203030
2380 ms 208.91.197.7
12 2026-08-27 03:11 639233961301716608
2137 ms 208.91.197.7
11 2026-08-27 02:54 639233950834200647
2255 ms 208.91.197.7
10 2026-08-27 02:36 639233940431849026
2252 ms 208.91.197.7
9 2026-08-27 02:19 639233930110596398
133 ms 208.91.197.7
8 2026-08-27 02:02 639233919705434540
1216 ms 208.91.197.7
7 2026-08-27 01:45 639233909452807845
2296 ms 208.91.197.7
6 2026-08-27 01:27 639233899096420820
1226 ms 208.91.197.7
5 2026-08-27 01:10 639233888707824939
2370 ms 208.91.197.7
4 2026-08-27 00:53 639233878461203802
3628 ms 208.91.197.7
3 2026-08-27 00:36 639233868060868209
1218 ms 208.91.197.7
2 2026-08-27 00:18 639233857450922991
4137 ms 208.91.197.7
1 2026-08-27 00:01 639233846871926285
2137 ms 208.91.197.7