Now in beta · looking for early users

Know an API is down before your customers do.

StatusPane follows the official status pages of 90+ services your SaaS relies on, from GitHub and Cloudflare to OpenAI and Supabase, and puts them on a single page. You see what's broken, which of your apps it affects and where each incident stands. It's early, and what beta users tell us shapes what we build next.

Launch the beta or see what's down right now, no sign-up
Checkout
1 of 9 components affected
Down
RA
New builds are temporarily paused Railway · updated 16 minutes ago
  1. Investigating
  2. Identified
  3. Monitoring
  4. Resolved
  • Railway Down Builds · Deployments
  • Cloudflare Operational CDN/Cache · DNS
  • Supabase Operational Database · Auth · Storage
  • GitHub Operational Actions · Git Operations
Checked less than a minute ago Webhook delivered

Why StatusPane

Your SaaS runs on a dozen vendors. Their outages shouldn't take a dozen tabs to find.

Every service you depend on posts incidents on its own status page, in its own format, on its own schedule. Checking them all is nobody's job, so outages get noticed late.

The problem

Scattered status pages, and you hear about it last

When something breaks, you're refreshing bookmarks, searching social media and asking in chat whether it's you or them. By the time you know an upstream API is down, your customers already do.

  • githubstatus.com
  • cloudflarestatus.com
  • status.openai.com
  • status.supabase.com
  • status.railway.com
  • + 7 more
  1. Railway posts an incident on its status page
  2. Your deploys start failing. Nobody knows why
  3. An engineer starts debugging your own code
  4. A customer emails support asking what's wrong
Example timeline
The solution

One page that tells you if your vendors are healthy

StatusPane is the single place to check the health of every external service your SaaS relies on. Open it, and you know in seconds whether the problem is upstream and which of your apps it hits.

  • Checked for you. StatusPane follows the official status pages of 95 providers, from GitHub and Cloudflare to OpenAI and Supabase.
  • Only what you use. Watch the specific components you depend on, like GitHub Actions or Supabase Auth, not a provider's whole list.
  • Grouped by app. See at a glance which product an incident affects and what stage it's in, from Investigating to Resolved.
  • Pushed to your tools. Signed webhooks fire when a component's status changes, so your own alerting hears about it right away.
Solo engineers

You're the whole on-call rotation

Add the handful of services your project runs on and check one page instead of six bookmarks. Rule out an upstream outage before you spend an hour debugging your own code.

Team leads

Everyone sees the same status

Group components under each app your team owns. During an incident, nobody asks "is it just me?" in chat, because the answer is on one page everyone can open.

SaaS administrators

Every vendor, one source of truth

Keep track of every external service your organization depends on in one place, and connect it to the rest of your stack with signed webhooks.

Features

Know your vendors are up, wherever you look. Nothing to maintain.

90+ services, live in minutes

Pick from more than 90 providers, like GitHub, Cloudflare, OpenAI and Supabase, and see their real-time status within minutes. There's no code to write, nothing to install and no infrastructure to run.

One page for every service

Every external service your SaaS depends on shows up on a single web page, grouped by the apps you run. A terminal view (TUI) for the command line is on the roadmap.

Every status through one API

Read the status of all your watched services from a single REST API, authenticated with your organization's API keys. Feed it into your own dashboards, scripts and internal tools instead of scraping a dozen status pages.

Coming soon

Native desktop app

A native app for macOS, Windows and Linux will keep your services' status one click away. It's in the works now.

How it works

Up and running in two steps

  1. Create your app and pick its services

    Give your app a name, then choose the services it depends on from a list of 90+ providers. Select only the parts you actually use.

  2. Voilà: one page, one traffic light per service

    Every service you picked shows up on a single page as a traffic light. Green is operational, amber is degraded and red is down, with the status written beside each light so you can read it at a glance.

    • GitHub Actions Operational
    • Cloudflare CDN/Cache · DNS Degraded
    • Supabase Database · Auth Down

The beta

Early, focused, and built with the people using it

StatusPane is in beta. The core works today, a few things are still on the way, and the roadmap is shaped by the teams who try it now.

Works today

The core of StatusPane

  • Status from 90+ providers' official status pages
  • Pick only the components you use
  • Group services under the apps you run
  • Incident stages, from Investigating to Resolved
  • Signed webhooks when a status changes
  • A REST API with organization API keys
On the roadmap

What we're working toward

  • A terminal view (TUI)
  • A native app for macOS, Windows and Linux
  • Slack and PagerDuty alerts
  • Single sign-on (SSO)
What we ask of you

Use it, and tell us what's missing

Expect rough edges and frequent changes. Tell us which providers to add, what slows you down and what you'd need before relying on StatusPane every day. Beta feedback decides what we build next.

Stop hearing about outages from your customers.

Join the beta to put every service your SaaS depends on in one page, and help shape what StatusPane becomes.

Launch the beta

StatusPane is currently in beta