DNS response history for ns2.edreza.net

ns2.edreza.net 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 36 DNS check records, 36 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.edreza.net.
Records on Selected Date

36

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-25 12:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

198.20.95.106

Most recently resolved hosting IP on selected date

Successful Responses

36

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.edreza.net

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
36 2026-08-25 12:39 639232576780683689
318 ms 198.20.95.106
35 2026-08-25 12:22 639232566381512620
6 ms 198.20.95.106
34 2026-08-25 12:05 639232556111768563
302 ms 198.20.95.106
33 2026-08-25 11:48 639232545839529039
310 ms 198.20.95.106
32 2026-08-25 11:30 639232535349285207
152 ms 198.20.95.106
31 2026-08-25 11:13 639232524938080723
305 ms 198.20.95.106
30 2026-08-25 10:19 639232492740373468
302 ms 198.20.95.106
29 2026-08-25 10:02 639232482235303141
153 ms 198.20.95.106
28 2026-08-25 09:44 639232471861770303
149 ms 198.20.95.106
27 2026-08-25 09:27 639232461630217327
311 ms 198.20.95.106
26 2026-08-25 09:10 639232451282965990
161 ms 198.20.95.106
25 2026-08-25 08:53 639232440814614938
307 ms 198.20.95.106
24 2026-08-25 08:35 639232430410720425
304 ms 198.20.95.106
23 2026-08-25 08:18 639232420003096185
313 ms 198.20.95.106
22 2026-08-25 08:01 639232409467287444
301 ms 198.20.95.106
21 2026-08-25 07:43 639232399077195997
168 ms 198.20.95.106
20 2026-08-25 07:26 639232388731528337
303 ms 198.20.95.106
19 2026-08-25 07:08 639232378288598612
317 ms 198.20.95.106
18 2026-08-25 06:15 639232346196373643
300 ms 198.20.95.106
17 2026-08-25 05:58 639232336112370741
321 ms 198.20.95.106
16 2026-08-25 05:41 639232326146508970
59 ms 198.20.95.106
15 2026-08-25 05:25 639232316189381720
7 ms 198.20.95.106
14 2026-08-25 05:08 639232306217998913
301 ms 198.20.95.106
13 2026-08-25 04:51 639232296255744174
297 ms 198.20.95.106
12 2026-08-25 04:35 639232286095760789
312 ms 198.20.95.106
11 2026-08-25 04:18 639232276086186273
334 ms 198.20.95.106
10 2026-08-25 04:01 639232265900986425
325 ms 198.20.95.106
9 2026-08-25 03:44 639232255723518075
299 ms 198.20.95.106
8 2026-08-25 03:27 639232245484452890
303 ms 198.20.95.106
7 2026-08-25 03:10 639232235157175331
319 ms 198.20.95.106
6 2026-08-25 02:16 639232203197189095
298 ms 198.20.95.106
5 2026-08-25 01:59 639232192844564298
300 ms 198.20.95.106
4 2026-08-25 01:42 639232182496008942
299 ms 198.20.95.106
3 2026-08-25 01:25 639232172197053132
324 ms 198.20.95.106
2 2026-08-25 00:31 639232140250307418
311 ms 198.20.95.106
1 2026-08-25 00:15 639232129927860324
301 ms 198.20.95.106