DNS response history for ns2.s1-cns-ose-usea1-auto.com

ns2.s1-cns-ose-usea1-auto.com 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 33 DNS check records, 33 successful responses, 0 failed responses, and 673 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.s1-cns-ose-usea1-auto.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

673 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

23.20.131.92

Most recently resolved hosting IP on selected date

Successful Responses

33

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.s1-cns-ose-usea1-auto.com

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
33 2026-08-26 10:27 639233360361507238
178 ms 23.20.131.92
32 2026-08-26 10:09 639233350067824371
180 ms 23.20.131.92
31 2026-08-26 09:52 639233339545274518
185 ms 23.20.131.92
30 2026-08-26 09:34 639233329214918079
3100 ms 23.20.131.92
29 2026-08-26 09:17 639233318749762337
179 ms 23.20.131.92
28 2026-08-26 09:00 639233308387917838
180 ms 23.20.131.92
27 2026-08-26 08:42 639233297961740122
93 ms 23.20.131.92
26 2026-08-26 08:25 639233287487159094
183 ms 23.20.131.92
25 2026-08-26 08:08 639233276995531707
182 ms 23.20.131.92
24 2026-08-26 07:50 639233266521568229
181 ms 23.20.131.92
23 2026-08-26 07:32 639233256081047431
183 ms 23.20.131.92
22 2026-08-26 06:39 639233223620132921
4 ms 23.20.131.92
21 2026-08-26 06:21 639233213287814244
3 ms 23.20.131.92
20 2026-08-26 06:04 639233202925983161
180 ms 23.20.131.92
19 2026-08-26 05:47 639233192644780696
179 ms 23.20.131.92
18 2026-08-26 05:30 639233182401183833
91 ms 23.20.131.92
17 2026-08-26 05:13 639233172074181051
184 ms 23.20.131.92
16 2026-08-26 04:55 639233161808421455
190 ms 23.20.131.92
15 2026-08-26 04:38 639233151357344052
181 ms 23.20.131.92
14 2026-08-26 04:21 639233141034116946
183 ms 23.20.131.92
13 2026-08-26 04:04 639233130828334142
2969 ms 23.20.131.92
12 2026-08-26 03:46 639233120373450007
181 ms 23.20.131.92
11 2026-08-26 03:29 639233110066216193
184 ms 23.20.131.92
10 2026-08-26 02:36 639233078065410564
179 ms 23.20.131.92
9 2026-08-26 02:19 639233067787457832
2108 ms 23.20.131.92
8 2026-08-26 02:02 639233057501801162
3108 ms 23.20.131.92
7 2026-08-26 01:44 639233047089431703
2136 ms 23.20.131.92
6 2026-08-26 01:27 639233036754790688
2 ms 23.20.131.92
5 2026-08-26 01:10 639233026412602472
180 ms 23.20.131.92
4 2026-08-26 00:53 639233016064066127
182 ms 23.20.131.92
3 2026-08-26 00:35 639233005922655772
316 ms 23.20.131.92
2 2026-08-26 00:18 639232995672256907
197 ms 23.20.131.92
1 2026-08-26 00:01 639232985300872416
4463 ms 23.20.131.92