Affected components
Update timeline
- investigating Mar 17, 2026, 04:15 PM UTC
Status: Investigating Beamery Engineering team has been alerted to an increase in CPU usage in our ElasticSearch cluster, the issue is being investigated. Search results may respond slower than normal. Affected components CRM (Degraded performance)
- identified Mar 17, 2026, 04:59 PM UTC
Status: Identified The team have identified a spike in Recipe usage as the root cause to the increased CPU. Additional resource is being deployed to support the increased load. Affected components CRM (Degraded performance)
- identified Mar 17, 2026, 07:26 PM UTC
Status: Identified CPU usage on the ElasticSearch cluster continues to be high despite remediations, the Beamery Engineering team have made further adjustments to bring this down. Recipe process time is expected to be reduced. Affected components CRM (Degraded performance)
- monitoring Mar 17, 2026, 11:17 PM UTC
Status: Monitoring Load is coming down following updates and normal service is expected to resume soon. The Beamery Engineering team are continuing to monitor the performance. Affected components CRM (Degraded performance)
- resolved Mar 18, 2026, 09:35 AM UTC
Status: Resolved Elastic CPU returned to normal following mitigations, normal service resumed. Affected components CRM (Operational)
Looking to track Beamery downtime and outages?
Pingoru polls Beamery's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Beamery reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Beamery alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required