pingoru pingoru Osano had 17 outages in the last 2 years totaling 23h 51m of downtime, averaging 0.7 incidents per month.
There were 17 Osano outages since February 3, 2025 totaling 23h 51m of downtime. Each is summarised below. Incident details, duration, and resolution information.
We've identified degraded service across our web application. Currently working on a fix.
This incident has been resolved.
Some customers may see inconsistent or incomplete scan results during this period. We are actively investigating.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
The Consent Management Publishing service is currently experiencing degraded service. We are investigating, and will keep you updated.
We are currently investigating this issue.
We have identified the root cause. We are working on restoring the publishing service ASAP.
We've implemented a fix, and are monitoring the CMP publishing service.
This incident has been resolved.
We are currently experiencing degraded service in the my.osano.com webapp. We are investigating and will keep you updated.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We’re currently experiencing degraded performance with our reporting dashboard. Some users may notice slow load times or incomplete data. Our team is actively investigating and working to restore full service as quickly as possible. We’ll share updates here as we learn more. Thank you for your patience.
The issue affecting our reporting dashboard has been fully resolved. All systems are now operating normally, and data is loading as expected.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
We've identified the root cause and have implemented a fix. We will continue to monitor.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented. We're continuing to monitor.
This incident has been resolved.