Start with the custom-domain state in the status-page editor. Certificate validation, edge deployment, and traffic routing use different DNS records and require different fixes.
Confirm the basic requirements
- The public status page is enabled.
- Ownership is Verified.
- Request custom domain is on and the request is saved.
- The custom hostname is the monitored domain or one of its subdomains.
- The hostname contains no protocol, path, or query string.
Use a dedicated subdomain such as status.example.com unless you have a specific reason to use the domain apex.
Pending certificate
Check the Step 1 certificate-validation CNAME:
- Copy the displayed name and value exactly.
- Confirm your provider did not append the domain twice.
- Remove conflicting records at the same validation name.
- Make sure the record is in public authoritative DNS.
- Keep DNS proxying off for the validation record.
- Check whether restrictive CAA records prevent issuance by the managed certificate authority.
The validation record can take time to appear after the certificate request. Select Check / activate domain again after it is publicly resolvable.
Deploying
Deploying means the certificate is issued but the dedicated edge distribution is not ready yet. No extra application change is normally needed.
Wait and select Check / activate domain again. Do not point the visitor hostname at an incomplete or guessed target; use the Step 2 value shown in the editor.
Pending DNS
Check the Step 2 routing CNAME:
- Its name must be the custom hostname.
- Its value must be the exact generated traffic target.
- Remove an old A, AAAA, or CNAME record that conflicts at the same hostname.
- Use a directly resolvable CNAME rather than a proxied or flattened record during activation.
- Check public DNS, not only the DNS provider's control panel.
- Allow for the previous record's TTL when replacing a target.
Uptime Basics marks the domain Active only when public CNAME resolution matches the expected managed traffic hostname.
HTTPS or certificate warning
Do not treat the custom URL as ready until the editor shows Active. Before then, DNS can point to a distribution that is still deploying or the browser can reach another service previously configured at that hostname.
If the state is Active but a certificate warning remains, confirm the browser address exactly matches the configured hostname, clear local DNS caches, and test from another network. Do not bypass a certificate warning for visitors.
Status page unavailable
- Confirm the status page itself was not disabled.
- Confirm the custom-domain request still shows Active.
- Wait for a new public snapshot after enabling or changing the page.
- Test the shared
status.uptimebasics.comURL to separate page-data issues from custom DNS issues. - Check whether a DNS proxy, redirect rule, or old web-host record intercepts the request.
If the shared page works but the custom URL does not, include the custom-domain state, last checked time, and public DNS results when contacting support.