Halaman status & sematan
Use your own domain for a status page
Serve your FastPing status page on a domain such as status.example.com: the CNAME record to create, automatic HTTPS, Cloudflare settings and troubleshooting.
Custom domains are part of the White-label status pages add-on ($15 a month), which also lets you hide the "Powered by FastPing" footer. Use a subdomain you control, such as status.example.com. Subdomains of fastping.app cannot be used, and each domain can belong to one status page only.
- At your DNS provider, create a CNAME record for the subdomain pointing to
direct.fastping.app:DNS recordsstatus.example.com. CNAME direct.fastping.app. - In FastPing, open the status page under Status pages, enter
status.example.comas the custom domain and save. - Once DNS has updated (usually minutes, sometimes longer depending on the record's previous TTL), open
https://status.example.com. The HTTPS certificate is requested automatically on the first visit, which can take a few seconds.
The custom domain serves the status page at its root, together with its own sub-pages; any other address on the domain redirects to the page.
Create the CNAME with the proxy status set to DNS only (grey cloud). Visitors must reach direct.fastping.app directly so that FastPing can obtain and serve the certificate for your domain. The same applies to other DNS providers that offer a proxy or CDN option for records.
DNS does not allow a CNAME record at the root of a domain (example.com itself), because the root also holds records such as MX and NS. A subdomain such as status. avoids the problem and keeps your status page independent of your main website.
| Message | What it means | What to do |
|---|---|---|
Unknown status page | The domain points to FastPing but is not saved on any status page (often a typo, or www. versus no www.). | Check the custom domain field of the status page. |
Certificate warning in the browser | The certificate could not be issued yet: the CNAME does not point to FastPing yet, or a proxy sits in front. | Check the record with the DNS lookup tool, set it to DNS only, wait for the old TTL to expire and reload. |
That domain is already used by another status page. | Each domain can serve one page. | Remove it from the other page first. |
The DNS lookup shows what the CNAME currently resolves to.
If the add-on is removed from your plan, the FastPing footer returns and the custom domain is no longer supported. The page remains available at its fastping.app address.