DNS response history for ns2.edsum.com

ns2.edsum.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 36 DNS check records, 36 successful responses, 0 failed responses, and 235 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.edsum.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

235 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.126.100.172

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.edsum.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
36 2026-08-25 12:36 639232576780683689
243 ms 209.126.100.172
35 2026-08-25 12:19 639232566381512620
278 ms 209.126.100.172
34 2026-08-25 12:02 639232556111768563
257 ms 209.126.100.172
33 2026-08-25 11:45 639232545839529039
233 ms 209.126.100.172
32 2026-08-25 11:27 639232535349285207
255 ms 209.126.100.172
31 2026-08-25 11:10 639232524938080723
272 ms 209.126.100.172
30 2026-08-25 10:16 639232492740373468
231 ms 209.126.100.172
29 2026-08-25 09:59 639232482235303141
235 ms 209.126.100.172
28 2026-08-25 09:41 639232471861770303
254 ms 209.126.100.172
27 2026-08-25 09:24 639232461630217327
125 ms 209.126.100.172
26 2026-08-25 09:07 639232451282965990
233 ms 209.126.100.172
25 2026-08-25 08:50 639232440814614938
260 ms 209.126.100.172
24 2026-08-25 08:32 639232430410720425
242 ms 209.126.100.172
23 2026-08-25 08:15 639232420003096185
276 ms 209.126.100.172
22 2026-08-25 07:58 639232409467287444
283 ms 209.126.100.172
21 2026-08-25 07:40 639232399077195997
276 ms 209.126.100.172
20 2026-08-25 07:23 639232388731528337
248 ms 209.126.100.172
19 2026-08-25 07:05 639232378288598612
235 ms 209.126.100.172
18 2026-08-25 06:12 639232346196373643
268 ms 209.126.100.172
17 2026-08-25 05:55 639232336112370741
235 ms 209.126.100.172
16 2026-08-25 05:38 639232326146508970
232 ms 209.126.100.172
15 2026-08-25 05:22 639232316189381720
231 ms 209.126.100.172
14 2026-08-25 05:05 639232306217998913
241 ms 209.126.100.172
13 2026-08-25 04:49 639232296255744174
10 ms 209.126.100.172
12 2026-08-25 04:32 639232286095760789
282 ms 209.126.100.172
11 2026-08-25 04:15 639232276086186273
293 ms 209.126.100.172
10 2026-08-25 03:58 639232265900986425
239 ms 209.126.100.172
9 2026-08-25 03:41 639232255723518075
235 ms 209.126.100.172
8 2026-08-25 03:24 639232245484452890
231 ms 209.126.100.172
7 2026-08-25 03:07 639232235157175331
234 ms 209.126.100.172
6 2026-08-25 02:14 639232203197189095
267 ms 209.126.100.172
5 2026-08-25 01:56 639232192844564298
232 ms 209.126.100.172
4 2026-08-25 01:39 639232182496008942
248 ms 209.126.100.172
3 2026-08-25 01:22 639232172197053132
285 ms 209.126.100.172
2 2026-08-25 00:29 639232140250307418
20 ms 209.126.100.172
1 2026-08-25 00:12 639232129927860324
228 ms 209.126.100.172