Live

Sentry

Sentry is operational

Checked 26 s ago Operational

History

90 days agoToday

Incidents in 90 days

23

Days with an incident

17

Median duration

2 h 12 min

Longest incident

6 h 18 min

Components

41
Dashboard Operational
90 days ago3 days with an incidentToday
API Operational
90 days ago3 days with an incidentToday
Integration Pipeline Operational
90 days ago3 days with an incidentToday
Seer Operational
90 days ago1 day with an incidentToday

Notification Delivery

Slack Operational
90 days ago1 day with an incidentToday
Email Operational
90 days agoNo incidentsToday
PagerDuty Operational
90 days agoNo incidentsToday
Microsoft Teams Operational
90 days agoNo incidentsToday

Authentication Services

Password-Based Operational
90 days agoNo incidentsToday
Google Operational
90 days agoNo incidentsToday
GitHub Operational
90 days agoNo incidentsToday
Azure DevOps Operational
90 days agoNo incidentsToday
SAML-Based Single Sign-On Operational
90 days agoNo incidentsToday

US Ingestion

US Error Ingestion Operational
90 days ago5 days with an incidentToday
US Transaction Ingestion Operational
90 days ago2 days with an incidentToday
US Attachment Ingestion Operational
90 days ago2 days with an incidentToday
US Profile Ingestion Operational
90 days ago3 days with an incidentToday
US Replay Ingestion Operational
90 days ago2 days with an incidentToday
US Span Ingestion Operational
90 days ago5 days with an incidentToday
US Cron Monitoring Operational
90 days ago2 days with an incidentToday
Custom Metrics (beta) Operational
90 days ago2 days with an incidentToday
US Size Analysis Ingestion Operational
90 days ago3 days with an incidentToday
US Snapshot Ingestion Operational
90 days ago3 days with an incidentToday

EU Ingestion

EU Error Ingestion Operational
90 days ago1 day with an incidentToday

Past incidents

Provider status pageTimes in UTC

Follow Sentry

Your coding agent knows when Sentry is down, and tells you when a failure is theirs, not yours. You can also get Sentry 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 "sentry" and tell me if Sentry 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=sentry
Slack
/feed subscribe https://outages.live/feed.xml?providers=sentry

Go from tracking outages to fixing production issues with Polylane.

Try Polylane