Beamery incident

Increased latency on Search

Resolved after 17 hours 19 minutes, affecting CRM, on March 17, 2026.

monitoring Mar 17, 2026, 11:17 PM UTC

Load is coming down following updates and normal service is expected to resume soon. The Beamery Engineering team are continuing to monitor the performance.

Started
Mar 17, 2026, 04:15 PM UTC
Resolved
Mar 18, 2026, 09:35 AM UTC
Duration
17h 19m
Detected by Pingoru
Mar 17, 2026, 04:15 PM UTC

Affected components

CRM

Update timeline

  1. investigating Mar 17, 2026, 04:15 PM UTC

    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.

  2. identified Mar 17, 2026, 04:59 PM UTC

    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.

  3. identified Mar 17, 2026, 07:26 PM UTC

    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.

  4. monitoring Mar 17, 2026, 11:17 PM UTC

    Load is coming down following updates and normal service is expected to resume soon. The Beamery Engineering team are continuing to monitor the performance.

  5. resolved Mar 18, 2026, 09:35 AM UTC

    Elastic CPU returned to normal following mitigations, normal service resumed.

Your product runs on more than Beamery

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →