DNS response history for ns2.chasecorporate.online

ns2.chasecorporate.online 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-26. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 393 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.chasecorporate.online.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

393 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:53

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.214.49.212

Most recently resolved hosting IP on selected date

Successful Responses

31

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.chasecorporate.online

Showing DNS history for 2026-08-26 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
31 2026-08-26 09:53 639233339545274518
164 ms 162.214.49.212
30 2026-08-26 09:35 639233329214918079
170 ms 162.214.49.212
29 2026-08-26 09:18 639233318749762337
350 ms 162.214.49.212
28 2026-08-26 09:00 639233308387917838
1836 ms 162.214.49.212
27 2026-08-26 08:43 639233297961740122
167 ms 162.214.49.212
26 2026-08-26 08:26 639233287487159094
346 ms 162.214.49.212
25 2026-08-26 08:08 639233276995531707
177 ms 162.214.49.212
24 2026-08-26 07:51 639233266521568229
168 ms 162.214.49.212
23 2026-08-26 07:33 639233256081047431
340 ms 162.214.49.212
22 2026-08-26 06:39 639233223620132921
335 ms 162.214.49.212
21 2026-08-26 06:22 639233213287814244
350 ms 162.214.49.212
20 2026-08-26 06:05 639233202925983161
336 ms 162.214.49.212
19 2026-08-26 05:47 639233192644780696
340 ms 162.214.49.212
18 2026-08-26 05:30 639233182401183833
2166 ms 162.214.49.212
17 2026-08-26 05:13 639233172074181051
340 ms 162.214.49.212
16 2026-08-26 04:56 639233161808421455
344 ms 162.214.49.212
15 2026-08-26 04:39 639233151357344052
336 ms 162.214.49.212
14 2026-08-26 04:21 639233141034116946
171 ms 162.214.49.212
13 2026-08-26 04:04 639233130828334142
339 ms 162.214.49.212
12 2026-08-26 03:47 639233120373450007
172 ms 162.214.49.212
11 2026-08-26 03:30 639233110066216193
339 ms 162.214.49.212
10 2026-08-26 02:37 639233078065410564
349 ms 162.214.49.212
9 2026-08-26 02:19 639233067787457832
335 ms 162.214.49.212
8 2026-08-26 02:02 639233057501801162
171 ms 162.214.49.212
7 2026-08-26 01:45 639233047089431703
344 ms 162.214.49.212
6 2026-08-26 01:28 639233036754790688
337 ms 162.214.49.212
5 2026-08-26 01:11 639233026412602472
167 ms 162.214.49.212
4 2026-08-26 00:53 639233016064066127
336 ms 162.214.49.212
3 2026-08-26 00:36 639233005922655772
348 ms 162.214.49.212
2 2026-08-26 00:19 639232995672256907
171 ms 162.214.49.212
1 2026-08-26 00:02 639232985300872416
332 ms 162.214.49.212