How to Create a Public Status Page in 60 Seconds

When your SaaS goes down, your users have two options: file a support ticket or assume you've gone under. A public status page gives them a third option — check it, see that you're aware of the issue, and wait.

That third option is worth a lot. It reduces support volume. It builds trust. It signals professionalism to enterprise prospects who always ask "do you have a status page?" before signing a contract.

Here's how to set one up in under a minute.

---

Step 1 — Create a PingBase account (30 seconds)

Go to app.pingba.se/register. Enter your email and a password. No credit card required — the free plan includes everything you need to get started.

---

Step 2 — Add your first monitor (20 seconds)

Once you're in the dashboard, click Add monitor. Enter:

• Name — something your users will recognize, like "API" or "App" or "Website"
• URL — the URL PingBase should check (e.g. https://yourapp.com or https://api.yourapp.com/health)
• Check interval — 5 minutes on free, 1 minute on Pro

Save it. PingBase will run the first check within seconds and show you the result.

Tip: Add multiple monitors if you have multiple components — your website, your API, your database endpoint. Each one gets its own status indicator on your status page. Users can see at a glance which component is affected during an incident.

---

Step 3 — Your status page is already live

This is the part most people don't expect. You don't need to "create" a status page — it's already there.

In the dashboard, click Status Page in the left sidebar. You'll see your status page URL — something like:

https://status.pingba.se/yourname

Open it. It shows:

• Current status for each monitor (green = up, red = down)
• Uptime percentage (24h, 7d, 30d)
• 90-day uptime history bars — one bar per day, color-coded
• Any active incidents

That's your public status page. Share the URL with your users, link it from your docs, put it in your support auto-reply. You're done.

---

Optional: use your own domain (5 minutes)

If you want your status page at status.yourcompany.com instead of the default URL, that's a PingBase Pro feature ($9/month).

Here's how:

1. 1
   In Settings → Status Page, enter status.yourcompany.com as your custom domain.
2. 2
   PingBase shows you a CNAME record to add. Go to your DNS provider and add: status → status.pingba.se
3. 3
   DNS propagates within a few minutes. SSL is handled automatically — no certificate setup required.

Once it's live, status.yourcompany.com shows your PingBase status page. Your users never see any PingBase branding if you don't want them to.

---

What to do during an incident

The status page updates automatically based on your monitors. If a monitor goes down, the component on your status page turns red immediately — no manual action needed.

But automatic status updates aren't the whole picture. During a real incident, your users want a human explanation of what's happening. PingBase has incident management built in:

1. Go to your status page settings in the dashboard
2. Click Post incident update
3. Write a brief plain-language explanation: "We're investigating elevated error rates on the API. Our team is looking into it."
4. The update appears on your status page immediately, timestamped
5. Post follow-up updates as you learn more: "Root cause identified, fix deploying now."
6. When resolved, mark the incident as resolved: "All systems operational. Postmortem to follow."

That pattern — acknowledge fast, update regularly, resolve clearly — is what separates companies that build user trust from companies that erode it.

---

Where to share your status page URL

Once it's live, put the URL everywhere:

• Your documentation site (usually in the footer or "Support" section)
• Your support email auto-reply: "For live status updates, visit status.yourapp.com"
• Your app's error pages — if users see a 500 error, a link to the status page tells them whether it's widespread or just them
• Your onboarding emails — one mention that it exists builds trust before they ever need it
• Your website footer

The goal is that when something goes wrong, your users' first instinct is to check the status page rather than email support.