DNS response history for ns2.corpdns.net

ns2.corpdns.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 274 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.corpdns.net.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

274 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:25

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.91.197.108

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.corpdns.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:25 639232566381512620
163 ms 208.91.197.108
35 2026-08-25 12:08 639232556111768563
320 ms 208.91.197.108
34 2026-08-25 11:51 639232545839529039
135 ms 208.91.197.108
33 2026-08-25 11:34 639232535349285207
301 ms 208.91.197.108
32 2026-08-25 11:16 639232524938080723
371 ms 208.91.197.108
31 2026-08-25 10:22 639232492740373468
347 ms 208.91.197.108
30 2026-08-25 10:05 639232482235303141
138 ms 208.91.197.108
29 2026-08-25 09:48 639232471861770303
293 ms 208.91.197.108
28 2026-08-25 09:30 639232461630217327
295 ms 208.91.197.108
27 2026-08-25 09:13 639232451282965990
282 ms 208.91.197.108
26 2026-08-25 08:56 639232440814614938
134 ms 208.91.197.108
25 2026-08-25 08:39 639232430410720425
287 ms 208.91.197.108
24 2026-08-25 08:21 639232420003096185
268 ms 208.91.197.108
23 2026-08-25 08:04 639232409467287444
290 ms 208.91.197.108
22 2026-08-25 07:46 639232399077195997
280 ms 208.91.197.108
21 2026-08-25 07:29 639232388731528337
271 ms 208.91.197.108
20 2026-08-25 07:12 639232378288598612
293 ms 208.91.197.108
19 2026-08-25 06:18 639232346196373643
133 ms 208.91.197.108
18 2026-08-25 06:01 639232336112370741
133 ms 208.91.197.108
17 2026-08-25 05:44 639232326146508970
176 ms 208.91.197.108
16 2026-08-25 05:28 639232316189381720
192 ms 208.91.197.108
15 2026-08-25 05:11 639232306217998913
285 ms 208.91.197.108
14 2026-08-25 04:54 639232296255744174
293 ms 208.91.197.108
13 2026-08-25 04:38 639232286095760789
292 ms 208.91.197.108
12 2026-08-25 04:21 639232276086186273
144 ms 208.91.197.108
11 2026-08-25 04:04 639232265900986425
133 ms 208.91.197.108
10 2026-08-25 03:47 639232255723518075
277 ms 208.91.197.108
9 2026-08-25 03:30 639232245484452890
280 ms 208.91.197.108
8 2026-08-25 03:13 639232235157175331
283 ms 208.91.197.108
7 2026-08-25 02:20 639232203197189095
339 ms 208.91.197.108
6 2026-08-25 02:03 639232192844564298
139 ms 208.91.197.108
5 2026-08-25 01:45 639232182496008942
134 ms 208.91.197.108
4 2026-08-25 01:28 639232172197053132
132 ms 208.91.197.108
3 2026-08-25 00:35 639232140250307418
1254 ms 208.91.197.108
2 2026-08-25 00:18 639232129927860324
334 ms 208.91.197.108
1 2026-08-25 00:00 639232119551972438
430 ms 208.91.197.108