Live

Amplitude

Amplitude is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

21

Days with an incident

23

Median duration

1 h 15 min

Longest incident

6 h 5 min

Components

25

Analytics

Web Reporting Operational
90 days ago1 day with an incidentToday
Web Application Operational
90 days ago1 day with an incidentToday

Experiment

Evaluation API Operational
90 days agoNo incidentsToday
Management API Operational
90 days agoNo incidentsToday
Web Application Operational
90 days agoNo incidentsToday
Flag Configurations API Operational
90 days agoNo incidentsToday
Web Experiment Script Operational
90 days agoNo incidentsToday

Audiences

Profile API Operational
90 days agoNo incidentsToday
Web Application Operational
90 days agoNo incidentsToday

Data

Web Application Operational
90 days agoNo incidentsToday
CLI/Codegen Operational
90 days agoNo incidentsToday
Data Processing Operational
90 days ago9 days with an incidentToday
Data Reception Operational
90 days agoNo incidentsToday
Cohort Export Operational
90 days agoNo incidentsToday
Event Streaming Operational
90 days ago6 days with an incidentToday
Data Export Operational
90 days ago12 days with an incidentToday
Guides & Surveys Operational
90 days ago1 day with an incidentToday
Amazon Web Services Operational
90 days agoNo incidentsToday
Marketing Website Operational
90 days agoNo incidentsToday
Session Replay Operational
90 days agoNo incidentsToday
Heatmaps Operational
90 days agoNo incidentsToday
AI Feedback Operational
90 days agoNo incidentsToday
Resource Center Operational
90 days agoNo incidentsToday
Agents and Chat Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Follow Amplitude

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane