Prisma: Increased 500s For Accelerate
Timeline of updates
- resolved
Description: We identified an increase in 500s at 12:30 UTC due a change deployed at the same time. Our monitoring and alerting picked up the issue shortly after this and we immediately rolled back the change. We are assessing the change and what caused the 500s and will implement the necessary improvements to prevent changes like this from causing any issues in the future. Affected users: All customers. Root cause: Deployment Workarounds: Rollback
From Prisma’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on www.prisma-status.com (opens in new tab).