About and methodology

StatusPages shows live status for the services you rely on, read from each provider's own status page and presented in one place, so you do not have to hop between dozens of separate pages to find out what is up, what is degraded and what is down.

What the site does

We track 146 services across 9 categories, from CPaaS and cloud platforms to AI APIs, payments and gaming networks. Every service has its own page answering "is it down?", with the components it reports as affected, its current incident updates and a 90-day history. Each one links straight to the provider's own status page, which stays the source of truth.

• My stack builds one board for just the providers you depend on. Your choice lives in the page address, so you can bookmark or share it. No account needed.
• The status API serves everything on the site as free JSON and RSS, and alerts can go to Slack or your own webhook.
• The reliability dashboard shows industry-wide incident trends. It never scores or ranks individual providers.
• The reachability board is our own live up/down check of every service we track.

How often we check

Every provider is checked every five minutes. A page shows when it was last checked, and the boards refresh themselves while they are open. If a provider's feed cannot be read on a check, we keep showing the last status we did read and say so, rather than guessing.

Where the data comes from

Wherever a provider publishes a machine-readable status page (for example an Atlassian Statuspage summary, an Instatus or StatusPal page, or an incident RSS or Atom feed), we read that and report what the provider itself says. We do not change a provider's own rating, with one exception: when everything a messaging provider reports is delivery toward specific mobile networks or countries, we show it as degraded and say it is operator-level, because their platform itself is up.

Some services publish no feed we can read. They show as "status unavailable" with a link to their own page, an honest gap rather than a claim that all is well.

The reachability check is separate and coarser: we request each service's own endpoint and record whether it responds. A response shows the front door is open, not that every part of the service works, and a service that blocks automated requests shows as "could not reach" rather than as an outage.

AI summaries

A category board can carry a one-sentence summary of its open incidents, written by an AI model from the providers' own incident titles and updates. It is always labelled "AI summary", it is withdrawn as soon as the set of incidents it describes changes, and it never replaces the providers' own words, which are shown alongside it.

Not affiliated with any provider

StatusPages is independent. We are not affiliated with, endorsed by or speaking for any provider listed. Names and logos belong to their owners and are used only to identify each service. If you represent a service and want its listing added, changed or removed, contact us; services removed at their owner's request are listed on removed listings.