DNS response history for ns2.corpbsi.tech

ns2.corpbsi.tech 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 146 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.corpbsi.tech.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

146 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

129.121.99.22

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.corpbsi.tech

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:17 639232492740373468
201 ms 129.121.99.22
29 2026-08-25 10:00 639232482235303141
102 ms 129.121.99.22
28 2026-08-25 09:42 639232471861770303
111 ms 129.121.99.22
27 2026-08-25 09:25 639232461630217327
203 ms 129.121.99.22
26 2026-08-25 09:08 639232451282965990
210 ms 129.121.99.22
25 2026-08-25 08:51 639232440814614938
7 ms 129.121.99.22
24 2026-08-25 08:33 639232430410720425
5 ms 129.121.99.22
23 2026-08-25 08:16 639232420003096185
108 ms 129.121.99.22
22 2026-08-25 07:59 639232409467287444
203 ms 129.121.99.22
21 2026-08-25 07:41 639232399077195997
203 ms 129.121.99.22
20 2026-08-25 07:24 639232388731528337
204 ms 129.121.99.22
19 2026-08-25 07:07 639232378288598612
164 ms 129.121.99.22
18 2026-08-25 06:13 639232346196373643
208 ms 129.121.99.22
17 2026-08-25 05:56 639232336112370741
209 ms 129.121.99.22
16 2026-08-25 05:40 639232326146508970
4 ms 129.121.99.22
15 2026-08-25 05:23 639232316189381720
202 ms 129.121.99.22
14 2026-08-25 05:06 639232306217998913
3 ms 129.121.99.22
13 2026-08-25 04:50 639232296255744174
213 ms 129.121.99.22
12 2026-08-25 04:33 639232286095760789
200 ms 129.121.99.22
11 2026-08-25 04:16 639232276086186273
200 ms 129.121.99.22
10 2026-08-25 03:59 639232265900986425
211 ms 129.121.99.22
9 2026-08-25 03:42 639232255723518075
7 ms 129.121.99.22
8 2026-08-25 03:25 639232245484452890
201 ms 129.121.99.22
7 2026-08-25 03:08 639232235157175331
2 ms 129.121.99.22
6 2026-08-25 02:15 639232203197189095
100 ms 129.121.99.22
5 2026-08-25 01:58 639232192844564298
199 ms 129.121.99.22
4 2026-08-25 01:40 639232182496008942
99 ms 129.121.99.22
3 2026-08-25 01:23 639232172197053132
207 ms 129.121.99.22
2 2026-08-25 00:30 639232140250307418
202 ms 129.121.99.22
1 2026-08-25 00:13 639232129927860324
201 ms 129.121.99.22