DNS response history for ns2.edomz.com

ns2.edomz.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-25. For this date, NameServerHistory found 39 DNS check records, 39 successful responses, 0 failed responses, and 321 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.edomz.com.
Records on Selected Date

39

Historical checks stored for this nameserver on selected date

Average Latency

321 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:29

All timestamps shown in UTC

Latest Resolved IP on Selected Date

199.79.62.107

Most recently resolved hosting IP on selected date

Successful Responses

39

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.edomz.com

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
39 2026-08-25 13:29 639232608016476376
154 ms 199.79.62.107
38 2026-08-25 13:12 639232597643611557
2020 ms 199.79.62.107
37 2026-08-25 12:55 639232587225721862
155 ms 199.79.62.107
36 2026-08-25 12:37 639232576780683689
302 ms 199.79.62.107
35 2026-08-25 12:20 639232566381512620
2201 ms 199.79.62.107
34 2026-08-25 12:03 639232556111768563
154 ms 199.79.62.107
33 2026-08-25 11:46 639232545839529039
154 ms 199.79.62.107
32 2026-08-25 11:28 639232535349285207
162 ms 199.79.62.107
31 2026-08-25 11:11 639232524938080723
6 ms 199.79.62.107
30 2026-08-25 10:17 639232492740373468
5 ms 199.79.62.107
29 2026-08-25 10:00 639232482235303141
153 ms 199.79.62.107
28 2026-08-25 09:42 639232471861770303
153 ms 199.79.62.107
27 2026-08-25 09:25 639232461630217327
2156 ms 199.79.62.107
26 2026-08-25 09:08 639232451282965990
2198 ms 199.79.62.107
25 2026-08-25 08:51 639232440814614938
150 ms 199.79.62.107
24 2026-08-25 08:33 639232430410720425
151 ms 199.79.62.107
23 2026-08-25 08:16 639232420003096185
151 ms 199.79.62.107
22 2026-08-25 07:59 639232409467287444
6 ms 199.79.62.107
21 2026-08-25 07:41 639232399077195997
153 ms 199.79.62.107
20 2026-08-25 07:24 639232388731528337
153 ms 199.79.62.107
19 2026-08-25 07:06 639232378288598612
150 ms 199.79.62.107
18 2026-08-25 06:13 639232346196373643
151 ms 199.79.62.107
17 2026-08-25 05:56 639232336112370741
294 ms 199.79.62.107
16 2026-08-25 05:39 639232326146508970
208 ms 199.79.62.107
15 2026-08-25 05:23 639232316189381720
9 ms 199.79.62.107
14 2026-08-25 05:06 639232306217998913
3 ms 199.79.62.107
13 2026-08-25 04:50 639232296255744174
3 ms 199.79.62.107
12 2026-08-25 04:33 639232286095760789
4 ms 199.79.62.107
11 2026-08-25 04:16 639232276086186273
157 ms 199.79.62.107
10 2026-08-25 03:59 639232265900986425
4 ms 199.79.62.107
9 2026-08-25 03:42 639232255723518075
151 ms 199.79.62.107
8 2026-08-25 03:25 639232245484452890
5 ms 199.79.62.107
7 2026-08-25 03:08 639232235157175331
161 ms 199.79.62.107
6 2026-08-25 02:15 639232203197189095
11 ms 199.79.62.107
5 2026-08-25 01:58 639232192844564298
3 ms 199.79.62.107
4 2026-08-25 01:40 639232182496008942
160 ms 199.79.62.107
3 2026-08-25 01:23 639232172197053132
150 ms 199.79.62.107
2 2026-08-25 00:30 639232140250307418
149 ms 199.79.62.107
1 2026-08-25 00:13 639232129927860324
3 ms 199.79.62.107