ステータスページと埋め込み
Create a public status page
Publish a status page with the monitors you choose, 90 days of uptime bars and recent incidents, so customers and players can check before they contact you.
- In the dashboard, open Status pages.
- Enter a title (for example "Example Inc. status") and an address: 3 to 40 lowercase letters, numbers or dashes. The page is published at
https://fastping.app/s/<address>; the address must not already be taken. - Optionally add a description (up to 500 characters), such as which services the page covers or where to get support.
- Tick the monitors to show and save. You can change all of this later.
The free plan and the base paid plan include 1 status page; each additional page costs $2 a month.
- An overall banner, such as "All systems operational", with the time of the last update.
- Active incidents: the ones you post, with their latest update, and outages that monitoring detected by itself ("Detected automatically by monitoring").
- Maintenance in progress and scheduled maintenance.
- Each monitor's name and current status, with daily uptime bars over the last 90 days. Game servers also show the current player count.
- A form to get updates by email, plus Atom and RSS feeds and a JSON version of the page.
- The incident history of the last 90 days, day by day. Every incident and maintenance window has its own page with its full timeline.
Incidents, maintenance and subscribers are explained in Maintenance windows, incident updates and email subscribers.
With JavaScript on, the page reloads itself every 60 seconds, so it keeps showing the current state. It waits while a visitor is typing, moving through the page with the keyboard or has used it in the last 30 seconds, and the Pause updates button next to the last-updated time stops the reloads until the browser tab is closed. Without JavaScript the page shows the state at the moment it was loaded. A copy may be cached for up to 30 seconds.
The page is shown in the visitor's browser language when FastPing is available in it, and it sets no cookies. FastPing is available in English, Chinese (Simplified), Spanish, Arabic, Portuguese (Brazil), Indonesian, French, Japanese, Russian and German.
Visitors see monitor names, never the URLs, hosts or ports behind them. Still, choose names you are happy to publish: "Website" and "Login" rather than "db-primary-10.0.3.7".
Every status page also publishes its incidents and maintenance as feeds, and its current state as JSON:
https:/: Atom, for feed readers and chat tools that follow feeds;/ fastping.app/ s/ <address>/ feed.atom https:/: the same entries as RSS 2.0;/ fastping.app/ s/ <address>/ feed.rss https:/: the overall state, each monitor's state and 90-day uptime, open incidents and outages, and active or upcoming maintenance. Any website may fetch it (cross-origin requests are allowed)./ fastping.app/ s/ <address>/ status.json
On a custom domain the same files are at /feed.atom, /feed.rss and /status.json. What each one contains is described in Maintenance windows, incident updates and email subscribers.
- Show what your users experience, not every internal component: "Website", "API", "Login", "EU game server".
- Link to the page from your website footer, your app's error pages and your support auto-replies, so people find it when something is wrong.
- Host the page on a domain that does not depend on your own infrastructure. A status page on the same server as your website goes down with it; the FastPing address or a custom domain pointing to FastPing does not.
With the white-label add-on you can serve the page on your own domain, such as status.example.com, and remove the "Powered by FastPing" footer: see Use your own domain for a status page.