A custom status domain passes through certificate and DNS stages before it becomes Active. Use the state shown in the status-page editor; do not guess a DNS target or treat a pending hostname as production-ready.
Confirm the requirements first
Before troubleshooting DNS, confirm:
- The public status page is enabled.
- Ownership of the monitored domain is Verified.
- The custom-domain request is enabled and saved.
- The hostname is the monitored domain or one of its subdomains.
- The value contains only a hostname, with no protocol, path, port, or query string.
A dedicated subdomain such as status.example.com is the simplest and most portable choice.
Match the state to the next action
| State | Meaning | Next action |
|---|---|---|
| Not configured | No usable custom hostname is saved. | Enter a valid hostname and save the request. |
| Pending certificate | The managed HTTPS certificate is not issued. | Publish and verify the Step 1 validation CNAME. |
| Deploying | The certificate is ready, but the dedicated distribution is still being prepared. | Wait, then select Check / activate domain again. |
| Pending DNS | The distribution is ready, but the visitor hostname does not resolve to its generated target. | Publish or correct the Step 2 routing CNAME. |
| Active | Certificate and public CNAME checks passed. | Test HTTPS and the exact configured hostname. |
| Error | Activation encountered a configuration or service error. | Correct the displayed issue, then run the check again. |
| Disabled | The custom domain is turned off and managed resources can be retiring. | Re-enable and repeat activation if the hostname should return. |
Activation checks run when you select Check / activate domain. Saving a DNS record does not continuously advance the state in the background.
Fix Pending certificate
Step 1 proves control of the hostname for certificate issuance.
- Copy the validation CNAME name and value exactly.
- Confirm the DNS provider did not append the domain a second time.
- Remove a conflicting record at the validation name.
- Make the record publicly resolvable and disable DNS proxying for it.
- Review restrictive CAA records if the certificate remains pending.
- Keep the validation record after activation so the certificate can renew.
After public DNS resolves correctly, select Check / activate domain again.
Fix Deploying
Deploying normally requires time rather than another DNS change. The managed distribution must finish deployment before the visitor hostname can be validated.
Wait, then run Check / activate domain again. Do not point the hostname to a target copied from another page or account.
Fix Pending DNS
Step 2 routes visitors to the completed status-page distribution.
- The record name must be the exact custom hostname.
- The record value must be the exact generated routing target.
- Remove conflicting A, AAAA, or CNAME records at that hostname.
- Disable proxying or flattening during activation.
- Check authoritative public DNS, not only the provider's saved-record screen.
- Allow the previous record's TTL to expire after a change.
The domain becomes Active only when its public CNAME matches the assigned target.
If the state is Active but the page does not work
- Test the exact HTTPS hostname saved in the editor.
- Test from a private window and another network.
- Confirm no old redirect, forwarding rule, DNS proxy, or web-host record intercepts the request.
- Test the shared
status.uptimebasics.compage. - Do not bypass a browser certificate warning.
If the shared page works, its snapshot is healthy and the remaining problem is specific to the custom hostname. If both pages fail, use Status page is unavailable.
When to contact Support
Contact Support if publicly resolvable DNS matches the records displayed in the editor but the state does not advance after another activation check.
Include the custom hostname, current state, last checked time, shared status-page URL, and public CNAME results. Do not send DNS-provider passwords, ownership tokens, private keys, or account recovery codes.