outages.live
Live

OpenStatus

OpenStatus is operational

Checked 27 s ago Operational

History

90 days agoToday

Incidents in 90 days

0

Days with an incident

0

Median duration

No data

Longest incident

No data

Components

34
Marketing Operational
90 days agoNo incidentsToday
Status page Operational
90 days agoNo incidentsToday
API Server Operational
90 days agoNo incidentsToday
Dashboard Operational
90 days agoNo incidentsToday
Cron Scheduler Operational
90 days agoNo incidentsToday
Alerting Engine Operational
90 days agoNo incidentsToday
🇳🇱 Amsterdam, Netherlands (Fly) Operational
90 days agoNo incidentsToday
🇸🇪 Stockholm, Sweden (Fly) Operational
90 days agoNo incidentsToday
🇮🇳 Mumbai, India (Fly) Operational
90 days agoNo incidentsToday
🇫🇷 Paris, France (Fly) Operational
90 days agoNo incidentsToday
🇺🇸 Dallas, Texas, USA (Fly) Operational
90 days agoNo incidentsToday
🇺🇸 Secaucus, New Jersey, USA (Fly) Operational
90 days agoNo incidentsToday
🇩🇪 Frankfurt, Germany (Fly) Operational
90 days agoNo incidentsToday
🇧🇷 Sao Paulo, Brazil (Fly) Operational
90 days agoNo incidentsToday
🇺🇸 Ashburn, Virginia, USA (Fly) Operational
90 days agoNo incidentsToday
🇿🇦 Johannesburg, South Africa (Fly) Operational
90 days agoNo incidentsToday
🇺🇸 Los Angeles, California, USA (Fly) Operational
90 days agoNo incidentsToday
🇬🇧 London, United Kingdom (Fly) Operational
90 days agoNo incidentsToday
🇯🇵 Tokyo, Japan (Fly) Operational
90 days agoNo incidentsToday
🇺🇸 Chicago, Illinois, USA (Fly) Operational
90 days agoNo incidentsToday
🇸🇬 Singapore, Singapore (Fly) Operational
90 days agoNo incidentsToday
🇺🇸 San Jose, California, USA (Fly) Operational
90 days agoNo incidentsToday
🇦🇺 Sydney, Australia (Fly) Operational
90 days agoNo incidentsToday
🇨🇦 Toronto, Canada (Fly) Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

No incident in the last 90 days.

Follow OpenStatus

Your coding agent knows when OpenStatus is down, and tells you when a failure is theirs, not yours. You can also get OpenStatus incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "openstatus" and tell me if OpenStatus has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=openstatus
Slack
/feed subscribe https://outages.live/feed.xml?providers=openstatus

Go from tracking outages to fixing production issues with Polylane.

Try Polylane