Amplitude incident
Event properties showing as over quota for orgs using Guides and Surveys
Update timeline
- resolved Apr 13, 2026, 09:00 PM UTC
Apr 13, 14:00 PDT Resolved - This incident has been resolved. Apr 13, 13:53 PDT Monitoring - Erroneous events have been deleted. Event property limits should be accurate again and new event properties should be usable again. Any event properties that came in only during the overage window (and haven't been sent again since) will not be usable until post-processing occurs at end of day. Apr 13, 08:45 PDT Identified - At 8:45 am PDT, Guides and Surveys added a large number of event properties. Which projects are impacted? Any project that previously had less than 2000 event properties and that now has 2000 or more event properties. What's the impact? All such projects are unable to (a) add new event properties and (b) use those new event properties for filtering, creating cohorts. The issue has been identified, and the team is working on a fix that will remove all of these event properties. You may see some irregularities during this time. Once the mistakenly-added event properties are deleted, some post-processing will occur at the end of the day to restore any new event properties which could not be added to event property overages (new ones, added after 8:45 am PDT, assuming the project was put over the 2000 event property limit due to this change).
Looking to track Amplitude downtime and outages?
Pingoru polls Amplitude's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Amplitude reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Amplitude alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required