DNS response history for ns2.corpoweb.net

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

36

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 12:30

All timestamps shown in UTC

Latest Resolved IP on Selected Date

154.16.145.222

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.corpoweb.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:30 639232576780683689
36 ms 154.16.145.222
35 2026-08-25 12:13 639232566381512620
2028 ms 154.16.145.222
34 2026-08-25 11:56 639232556111768563
93 ms 154.16.145.222
33 2026-08-25 11:39 639232545839529039
39 ms 154.16.145.222
32 2026-08-25 11:21 639232535349285207
25 ms 154.16.145.222
31 2026-08-25 11:04 639232524938080723
26 ms 154.16.145.222
30 2026-08-25 10:10 639232492740373468
31 ms 154.16.145.222
29 2026-08-25 09:53 639232482235303141
2024 ms 154.16.145.222
28 2026-08-25 09:35 639232471861770303
78 ms 154.16.145.222
27 2026-08-25 09:18 639232461630217327
42 ms 154.16.145.222
26 2026-08-25 09:01 639232451282965990
183 ms 154.16.145.222
25 2026-08-25 08:44 639232440814614938
47 ms 154.16.145.222
24 2026-08-25 08:26 639232430410720425
35 ms 154.16.145.222
23 2026-08-25 08:09 639232420003096185
27 ms 154.16.145.222
22 2026-08-25 07:51 639232409467287444
20 ms 154.16.145.222
21 2026-08-25 07:34 639232399077195997
71 ms 154.16.145.222
20 2026-08-25 07:17 639232388731528337
52 ms 154.16.145.222
19 2026-08-25 07:00 639232378288598612
44 ms 154.16.145.222
18 2026-08-25 06:06 639232346196373643
15 ms 154.16.145.222
17 2026-08-25 05:49 639232336112370741
42 ms 154.16.145.222
16 2026-08-25 05:32 639232326146508970
56 ms 154.16.145.222
15 2026-08-25 05:16 639232316189381720
7 ms 154.16.145.222
14 2026-08-25 04:59 639232306217998913
45 ms 154.16.145.222
13 2026-08-25 04:43 639232296255744174
46 ms 154.16.145.222
12 2026-08-25 04:26 639232286095760789
44 ms 154.16.145.222
11 2026-08-25 04:09 639232276086186273
29 ms 154.16.145.222
10 2026-08-25 03:52 639232265900986425
38 ms 154.16.145.222
9 2026-08-25 03:35 639232255723518075
2013 ms 154.16.145.222
8 2026-08-25 03:18 639232245484452890
2033 ms 154.16.145.222
7 2026-08-25 03:01 639232235157175331
2045 ms 154.16.145.222
6 2026-08-25 02:08 639232203197189095
12 ms 154.16.145.222
5 2026-08-25 01:50 639232192844564298
36 ms 154.16.145.222
4 2026-08-25 01:33 639232182496008942
68 ms 154.16.145.222
3 2026-08-25 01:16 639232172197053132
48 ms 154.16.145.222
2 2026-08-25 00:23 639232140250307418
55 ms 154.16.145.222
1 2026-08-25 00:05 639232129927860324
21 ms 154.16.145.222