NIU website status
Is it down?
Hourly availability checks for cirrus, arcus, triton, and chubasco.
Last checked: no checks recorded
Loading status…
Current cards compare both sources when configured. Graphs use the selected source.
Availability over time
Outage history
Each block represents one UTC hour. Hover or focus a block for its check result.
Response time
Total HTTPS request time in milliseconds. Gaps indicate failed or missing checks.
Detected outages
Consecutive failed hourly checks, bounded by successful checks or gaps in monitoring. Times are detection times; outages may start or end between checks.
| Website | First failed check (UTC) | Next observation (UTC) | Failed checks |
|---|
How this works
Each configured monitor checks each website’s HTTPS home page once per hour, retrying failures up to three times. Successful responses and redirects count as responding. HTTP 401/403 responses count as responding with restricted access; other HTTP errors, DNS failures, connection errors, and invalid TLS certificates count as failed checks.
A failed check means the website could not be reached successfully from the monitoring location shown above. It does not establish that the entire machine is offline. Checks older than 90 minutes are marked stale. Gray hours mean no data, and are excluded from the successful-check percentage. History begins when the checker is installed; this page displays up to 30 days, and the downloadable data contains up to 90 days.
Outage timing is approximate at an hourly sampling interval. If Nimbus itself is unavailable, this status page will also be unavailable.
Download check history (JSON) →