DNS response history for ns2.boulderindoorsoccer.com

ns2.boulderindoorsoccer.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 23 DNS check records, 23 successful responses, 0 failed responses, and 493 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.boulderindoorsoccer.com.
Records on Selected Date

23

Historical checks stored for this nameserver on selected date

Average Latency

493 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 07:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

172.96.180.158

Most recently resolved hosting IP on selected date

Successful Responses

23

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.boulderindoorsoccer.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
23 2026-08-26 07:33 639233256081047431
2293 ms 172.96.180.158
22 2026-08-26 06:39 639233223620132921
331 ms 172.96.180.158
21 2026-08-26 06:21 639233213287814244
327 ms 172.96.180.158
20 2026-08-26 06:04 639233202925983161
322 ms 172.96.180.158
19 2026-08-26 05:47 639233192644780696
331 ms 172.96.180.158
18 2026-08-26 05:30 639233182401183833
329 ms 172.96.180.158
17 2026-08-26 05:13 639233172074181051
332 ms 172.96.180.158
16 2026-08-26 04:55 639233161808421455
317 ms 172.96.180.158
15 2026-08-26 04:38 639233151357344052
327 ms 172.96.180.158
14 2026-08-26 04:21 639233141034116946
2165 ms 172.96.180.158
13 2026-08-26 04:04 639233130828334142
333 ms 172.96.180.158
12 2026-08-26 03:47 639233120373450007
335 ms 172.96.180.158
11 2026-08-26 03:29 639233110066216193
323 ms 172.96.180.158
10 2026-08-26 02:36 639233078065410564
318 ms 172.96.180.158
9 2026-08-26 02:19 639233067787457832
327 ms 172.96.180.158
8 2026-08-26 02:02 639233057501801162
323 ms 172.96.180.158
7 2026-08-26 01:44 639233047089431703
339 ms 172.96.180.158
6 2026-08-26 01:27 639233036754790688
329 ms 172.96.180.158
5 2026-08-26 01:10 639233026412602472
325 ms 172.96.180.158
4 2026-08-26 00:53 639233016064066127
327 ms 172.96.180.158
3 2026-08-26 00:35 639233005922655772
328 ms 172.96.180.158
2 2026-08-26 00:18 639232995672256907
326 ms 172.96.180.158
1 2026-08-26 00:01 639232985300872416
325 ms 172.96.180.158