Intermittent User Logouts
Timeline · 2 updates
- investigating Aug 27, 2026, 01:26 PM UTC
We are currently investigating this issue.
- resolved Aug 31, 2026, 04:55 PM UTC
This incident has been resolved.
Koddi had 10 outages in the last 2 years totaling 115h 52m of downtime — averaging 0.4 incidents per month.
There were 10 Koddi outages since March 25, 2025 totaling 115h 52m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating an intermittent service disruption.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
All customers in Azure east have been rerouted, and delivery is stable. Some users are experiencing intermittent UI issues, which we're working to mitigate now.
All affected services have been rerouted and are stable. We will continue to monitor.
This incident has been resolved.
Brief Ads Delivery latency degradation between 4:27 ET and 4:57 ET. Latency has stabilized, and the team is continuing to monitor.
We are aware of the ongoing Cloudflare service disruptions. While our systems remain operational, Koddi Ads UI users may see intermittent errors. As a precaution, we have moved our status to Yellow (Monitoring) until Cloudflare fully resolves the incident. We’ll continue to track progress and provide updates as needed.
Cloudflare has resolved the issue.
We are currently operating at a degraded level due to widespread issues affecting major cloud providers, including Azure and AWS. While our core systems remain functional, some services may experience slower performance or limited availability. We are closely monitoring the situation and will provide updates as cloud provider stability improves.
We are continuing to investigate this issue.
We are continuing to investigate the issue. We can confirm that there was no AWS impact, only Azure.
All systems are operational, we are continuing to monitor the stability of the underlying Azure resources.
This incident has been resolved.
We are aware of the ongoing AWS service disruptions impacting parts of the AWS infrastructure. While our systems remain operational, we are closely monitoring for any potential impact. As a precaution, we have moved our status to Yellow (Monitoring) until AWS fully resolves the incident. We’ll continue to track progress and provide updates as needed.
We are continuing our monitoring and of the AWS incident to ensure our service remains operational. AWS are reporting mitigations application that are showing early signs of success on their end. We’ll continue to track progress and provide updates as needed.
We have fully recovered Koddi Enterprise Reporting Services, and are not showing any additional degradations elsewhere. AWS is reporting progress in the recovery as well. We are continuing to monitor all systems out of an abundance of caution.
You may be experiencing higher-than-normal error rates in the Azure East region due to an ongoing cloud issue.
We have identified the cause for the degraded performance for Koddi UI, Delivery and Event collection in Azure EastUS is due to an upstream incident affecting Azure-managed disks. Our application services are healthy; impact is limited by infrastructure in the affected zone. We're working with Microsoft on remediation and have put mitigations in place to reduce risk.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
Various services are experiencing disruption in us-east-1. Fallback regions are all operational.
This incident has been resolved.
Between 6AM and 8AM CT some of our customers experienced a degradation in our Reporting performance. Core performance was not impacted, and this was limited to customers served from AWS (Azure not affected).
Between 1:57PM and 2:57PM EDT some of our Koddi Ads customers experienced an interruption in the ability to log in to the platform. This was caused by a significant outage in Auth0, our upstream authentication provider (https://status.auth0.com/incidents/6cv20z0sj11k). The impact was limited to the UI, and by 3:15PM EDT it was fully resolved. There was no impact to any Campaign Management APIs, Ad Delivery, Event Collection or Reporting Services.