Osano Outage History
8 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 Osano Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | Partial Outage - Degraded ServiceThis incident has been resolved. | 7 min | Resolved |
| Aug 6, 2026 | Degraded Service in Compliance Check ScannerThis incident has been resolved. | 16 min | Resolved |
| Jul 28, 2026 | Osano's Engineering team will be conducting routine infrastructure maintenance.The scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Apr 19, 2026 | Routine Infrastructure MaintenanceThe scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Apr 1, 2026 | Consent Management Publishing Experiencing Degraded ServiceThis incident has been resolved. | 1h 33m | Resolved |
| Mar 30, 2026 | Errors logging into my.osano.comThis incident has been resolved. | 38 min | Resolved |
| Mar 19, 2026 | Reporting Dashboard Performance DegradationThe issue affecting our reporting dashboard has been fully resolved. All systems are now operating normally, and data is loading as expected. | 5h 27m | Resolved |
| Mar 9, 2026 | Potential Degraded Service in Customer Reporting FeaturesThis incident has been resolved. | 1h 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 Osano 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 Osano 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 Osano 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 Osano outage in this window ran 5h 27m, against a mean recovery of 1h 45m. If you depend on Osano 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.