Status page unavailable means the public page could not load a valid, enabled status-page snapshot. It does not mean the monitored website is Down.
Confirm which URL is affected
Test the shared Uptime Basics URL first:
https://status.uptimebasics.com/your-slug
If you also use a custom domain, test it separately.
- If the shared URL works but the custom URL does not, the page data is available and the problem is normally custom-domain DNS, certificate deployment, or routing.
- If both URLs are unavailable, check the page's enabled state, slug, monitor, and latest public snapshot.
Use a private browser window or another network when local DNS or an old browser cache may be involved.
Check whether the page is enabled
- Open the monitor.
- Expand Public Status Page under Monitor Tools.
- Open the status-page settings.
- Confirm the page is enabled and the displayed shared URL uses the expected slug.
Disabling a status page intentionally removes its public snapshot while preserving its settings and reserved slug. Re-enable the page to restore public access.
Deleting the monitor disables its status page and reserves the slug during the 30-day monitor recovery period. Restoring the monitor restores its saved page configuration in a disabled state. Permanent monitor cleanup removes the page record and releases the slug.
Do not confuse Paused with Unavailable
Pausing a monitor does not disable an enabled status page. The public page remains available and shows Paused, while retaining historical results.
If an enabled page shows Unavailable rather than Paused, investigate page loading or configuration instead of the monitor's pause state.
Allow a short cache update
Enabling a page writes a public snapshot from the latest monitor data. New check results and saved display changes refresh that snapshot, but the public cache can take about one minute to update.
For a transient request failure, a browser that recently loaded the page can use a bounded cached snapshot and show a delayed-update notice. If no valid current or cached payload can be loaded, the page shows Unavailable instead of inventing status data.
Wait briefly, refresh once, and test a private window. Repeated rapid refreshes do not force monitoring checks or bypass the public cache.
Check the slug and link
- Copy the URL shown in the status-page editor rather than typing it from memory.
- Confirm the slug has not been changed.
- Remove an extra path, query string, or trailing punctuation copied from another message.
- Confirm the link points to
status.uptimebasics.com, not an old hosting or preview address.
A valid slug belongs to one monitor at a time. A URL for a disabled, deleted, or renamed page will not load the replacement automatically.
If only the custom domain fails
Open the custom-domain section and review its state. A custom hostname is not ready for visitors until it shows Active.
Continue with Custom status domain is pending or not working. Keep the shared URL available while DNS and certificate setup is being corrected.
When to contact Support
Contact Support if the page is enabled, the exact shared URL remains unavailable after the cache interval, and the monitor still exists.
Include the monitor name, shared URL, custom URL if used, approximate time, page enabled state, and custom-domain state. Do not include verification tokens, DNS-account credentials, private keys, or saved monitor authentication.