Optro Outage History
6 incidents recorded over the last 365 days, 6 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 Optro Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 4, 2026 | SAML Callback Causing Login Failures | 4h 44m | Resolved |
| Oct 9, 2026 | Emergency Maintenance - EU customer database upgrade | 17h 47m | Resolved |
| Sep 3, 2026 | Workstream task failures | 2h 55m | Resolved |
| Jun 26, 2026 | Some users are unable to log in to Optro | 103h 50m | Resolved |
| May 6, 2026 | Lucidchart App Unavailable | 4h 44m | Resolved |
| Apr 27, 2026 | ABI Dashboards not loading | 14h 2m | 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 Optro 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 Optro 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 Optro 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 Optro outage in this window ran 4d 7h, against a mean recovery of 1d. If you depend on Optro 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.