Summary On April 22, 2026, we experienced a temporary service disruption affecting the PRISM API. The issue was caused by unintended configuration changes introduced during internal updates.
Timeline (UTC)
13:49 – Configuration changes deployed 13:49–14:12 – Service disruption impacting production 14:12 – Fix deployed 14:12–14:28 – Service recovery period 14:28 – Full service restored
Impact Users experienced intermittent service disruption for approximately 39 minutes.
Cause During internal updates, configuration changes intended for a non-production environment were inadvertently applied to production, resulting in the disruption.
Resolution The issue was identified and corrected, and the affected configuration changes were reverted. Service was fully restored by 14:28 UTC.
Next Steps We are reviewing our deployment processes to ensure stronger environment isolation and prevent similar issues in the future.