DNS response history for ns2.corpbot.net

ns2.corpbot.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 30 DNS check records, 30 successful responses, 0 failed responses, and 232 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.corpbot.net.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

232 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

138.201.11.94

Most recently resolved hosting IP on selected date

Successful Responses

30

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.corpbot.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
30 2026-08-25 10:13 639232492740373468
64 ms 138.201.11.94
29 2026-08-25 09:56 639232482235303141
40 ms 138.201.11.94
28 2026-08-25 09:38 639232471861770303
20 ms 138.201.11.94
27 2026-08-25 09:21 639232461630217327
60 ms 138.201.11.94
26 2026-08-25 09:04 639232451282965990
43 ms 138.201.11.94
25 2026-08-25 08:47 639232440814614938
2 ms 138.201.11.94
24 2026-08-25 08:29 639232430410720425
2030 ms 138.201.11.94
23 2026-08-25 08:12 639232420003096185
38 ms 138.201.11.94
22 2026-08-25 07:55 639232409467287444
25 ms 138.201.11.94
21 2026-08-25 07:37 639232399077195997
4 ms 138.201.11.94
20 2026-08-25 07:20 639232388731528337
31 ms 138.201.11.94
19 2026-08-25 07:03 639232378288598612
23 ms 138.201.11.94
18 2026-08-25 06:09 639232346196373643
52 ms 138.201.11.94
17 2026-08-25 05:52 639232336112370741
2069 ms 138.201.11.94
16 2026-08-25 05:36 639232326146508970
77 ms 138.201.11.94
15 2026-08-25 05:19 639232316189381720
15 ms 138.201.11.94
14 2026-08-25 05:03 639232306217998913
41 ms 138.201.11.94
13 2026-08-25 04:46 639232296255744174
2008 ms 138.201.11.94
12 2026-08-25 04:29 639232286095760789
15 ms 138.201.11.94
11 2026-08-25 04:12 639232276086186273
40 ms 138.201.11.94
10 2026-08-25 03:55 639232265900986425
3 ms 138.201.11.94
9 2026-08-25 03:38 639232255723518075
19 ms 138.201.11.94
8 2026-08-25 03:21 639232245484452890
49 ms 138.201.11.94
7 2026-08-25 03:04 639232235157175331
18 ms 138.201.11.94
6 2026-08-25 02:11 639232203197189095
3 ms 138.201.11.94
5 2026-08-25 01:54 639232192844564298
46 ms 138.201.11.94
4 2026-08-25 01:36 639232182496008942
66 ms 138.201.11.94
3 2026-08-25 01:19 639232172197053132
47 ms 138.201.11.94
2 2026-08-25 00:26 639232140250307418
8 ms 138.201.11.94
1 2026-08-25 00:09 639232129927860324
7 ms 138.201.11.94