Alloy incident

[Retroactive] Elevated JQ Evaluation Memory Errors

Notice Resolved View vendor source →
Started
Mar 09, 2026, 03:24 PM UTC
Resolved
Mar 05, 2026, 04:00 AM UTC
Duration
Detected by Pingoru
Mar 09, 2026, 03:24 PM UTC

Update timeline

  1. resolved Mar 09, 2026, 03:24 PM UTC

    Between March 4 at 11:00 PM ET and March 5 at 10:07 AM ET, we experienced an elevated rate of memory-related errors impacting evaluations running through JQ input attributes. As a result, some evaluations returned a null value for the input attribute instead of the correct value, potentially interrupting decisioning in the Workflow. Impacted applications would need to be re-run. Only workflows using input attributes with JQ were impacted; other Workflow logic was not impacted. The issue has been identified and resolved, and all systems are now operating normally.

Looking to track Alloy downtime and outages?

Pingoru polls Alloy's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Alloy reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Alloy alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Alloy for free

5 free monitors · No credit card required