← Back to the carnage
AMPLITUDE
🟠 Amplitude's external streaming destination feature decided to ghost all your data in transit. Engineering claims they found the problem but are apparently fluent in corporate time estimates. Your analytics pipeline is now a static display of wishful thinking. (Auto-resolved: no updates in 24h)
// The official story
Streaming to External Destinations Unavailable
// Status page says
Oct 22 , 15:08 PDT Identified - We are currently investigating an issue affecting streaming to external destinations. During this time, streaming deliveries are unavailable, and retrying data sends is also impacted. Our Engineering team has identified the affected infrastructure and is actively working to restore functionality. We apologize for the disruption and will provide further updates as our investigation
🔗 Official status page (for the PR-approved version)
https://status.amplitude.com/incidents/zsk5n9qys4ddAmplitude's Greatest Hits
🟢 AMPLITUDE
Oct 08, 2026
🟠 Amplitude discovered their US data pipeline is basically a procrastinator—BigQuery exports are lagging harder than your 3pm standup attendance. EU got the express lane while America got the scenic route. Downstream gremlin appears guilty. (Auto-resolved: no updates in 24h)
🟢 AMPLITUDE
Oct 05, 2026
⚪ Amplitude's Guides and Surveys service took an unexpected 8-minute nap between 11:40-11:48 AM PT, leaving users unable to create, edit, or publish anything. They've since woken up and claim everything's fine, though they're still checking if anyone left the stove on. (Auto-resolved: no updates in 24h)
🟢 AMPLITUDE
Sep 17, 2026
🟠 Amplitude's data pipeline decided to move at geological timescales since 11:30 AM PST. Your analytics are taking a scenic route to actually showing up. Engineers are investigating why 'realtime' apparently means 'whenever it feels like it.'. (Auto-resolved: no updates in 24h)
🟢 AMPLITUDE
Aug 25, 2026
⚪ Amplitude ghosted users for 15 minutes while its engineers played the classic 'turn it off and on again' game. The platform's now back and pretending nothing happened. Your data missed its flight but made the later connection. (Auto-resolved: no updates in 24h)