Cellebrite Outage History
8 incidents recorded over the last 365 days, 4 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Cellebrite Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 3, 2026 | Genesis – US Service UpdateWe are currently experiencing an issue affecting Genesis customers hosted in the US region, where queries result in a “Generate Response Failure” error. The issue is related to an external service provider, and our… | 2h 7m | Resolved |
| Oct 22, 2026 | Unable to view evidence in Guardian ProWe have identified the root cause of the issue affecting Guardian Pro and a fix has been developed, tested, and is currently being deployed to production. Our teams are closely monitoring the deployment process to… | 3h 11m | Resolved |
| Oct 21, 2026 | Guardian Pro Environment MaintenanceScheduled Maintenance | 14h 0m | Scheduled |
| Oct 7, 2026 | Guardian Collaborate / Guardian Pro (SPECIFY REGION) - <issue here>Cellebrite Guardian Pro is currently experiencing an issue with opening evidence. Non-admin users do not have the option to view evidence in the system. Admin users are not impacted. The Cellebrite team is working on… | 6h 3m | Resolved |
| Oct 6, 2026 | Guardian Upgrade MaintenanceScheduled Maintenance | 4h 0m | Scheduled |
| Oct 6, 2026 | Upgrade maintenance windowScheduled Maintenance | 2h 0m | Scheduled |
| Sep 4, 2026 | Maintenance WindowScheduled Maintenance | 7h 0m | Scheduled |
| Mar 30, 2026 | US Guardian OutageWe are actively troubleshooting a network issue resulting in customers unable to connect to their Guardian instances in the United States. We will continue to update the status page as we make progress toward resolution | 5269h 59m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Cellebrite incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Cellebrite Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Cellebrite acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Cellebrite outage in this window ran 219d 13h, against a mean recovery of 27d 15h. If you depend on Cellebrite in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.