Kevel had 25 outages in the last 2 years totaling 44h 10m of downtime — averaging 1 incident per month.
There were 25 Kevel outages since July 4, 2024 totaling 44h 10m of downtime. Each is summarised below — incident details, duration, and resolution information.
We identified an issue that may have delayed delivery of beta log data via Data Shipping for some customers between June 9, 2026 at 21:16 UTC and June 11, 2026 at 14:18 UTC. This issue has been resolved. Beta logs are now being shipped as expected, and no log data was lost. We are actively working to deliver any delayed logs from the affected period.
Mar 31, 10:12 EDT Resolved - The issue has been resolved and system performance has remained stable. We will continue to monitor as a precaution. Mar 31, 06:09 EDT Update - System performance has remained stable following the applied mitigation. We are continuing to monitor to ensure ongoing reliability. Mar 31, 05:00 EDT Monitoring - A mitigation has been applied and we are currently monitoring the system to ensure continued stability. Mar 31, 02:25 EDT Update - We are continuing to investigate the root cause. In the meantime, we have scaled additional capacity in the affected region, which has restored stability to ad serving. We will provide further updates as we learn more. Mar 31, 01:05 EDT Investigating - We are currently investigating degraded ad serving performance in the us-east-1 region.
Mar 1, 14:30 EST Completed - The scheduled maintenance has been completed. Mar 1, 14:27 EST Update - Scheduled maintenance is still in progress. We will provide updates as necessary. Mar 1, 11:30 EST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb 26, 15:27 EST Scheduled - During the maintenance window, the creation and modification of login user accounts will be temporarily unavailable via both the Management UI and API. All other platform functionality will remain fully operational throughout this period. This maintenance is part of a series of improvements we are making to the user management experience on Kevel Ad Server. We appreciate your patience and understanding as we work to enhance the platform. For full details on what's changing, please visit our documentation: https://dev.kevel.com/docs/user-management-new If you have any questions or concerns, please don't hesitate to reach out to our support team.
Some reporting data did not process correctly between 2026-02-20 21:00:00 and 2026-02-20 22:00:00 UTC. We have since reprocessed the affected data. As a result, some reporting metrics for that time period may have increased. Additionally, in cases where clicks or conversions were fired late for ads delivered previously, the associated clicks and click-derived revenue were applied to the original delivery dates, resulting in updates to historical metrics.
Feb 3, 16:38 EST Resolved - This incident has been resolved. Issue began: 1:55 PM ET Issue resolved: 4:37 PM ET Feb 3, 16:25 EST Monitoring - A fix has been implemented and we are monitoring the results. Feb 3, 16:09 EST Investigating - We have identified an issue impacting ad serving. An investigation is underway with our team. We'll keep you updated along the way.
Customers in the eu-central-1 region may have experienced periods of high decision response times between 06:10 and 08:05 UTC on November 24, 2025. This was caused by anomalous behavior while the Kevel system scaled in response to irregular traffic patterns. Kevel's core ad serving systems are designed to mitigate these situations and we've adjusted our scaling algorithms following this investigation to reduce the likelihood of recurrence.
Oct 14, 16:12 EDT Resolved - This incident has been resolved. Oct 14, 15:42 EDT Update - We are continuing to monitor for any further issues. Oct 14, 14:49 EDT Monitoring - A fix has been implemented and we are monitoring the results. Oct 14, 14:37 EDT Investigating - We identified an issue impacting Reporting. Reports are processing through the system. We'll keep you updated along the way.
Aug 12, 16:37 EDT Resolved - This incident has been resolved. Aug 12, 15:48 EDT Update - A fix has been implemented for most impacted customers. We are deploying the fix to the remaining impacted customers and monitoring. Aug 12, 13:13 EDT Identified - We have identified the issue and are working on a fix. Aug 12, 12:39 EDT Investigating - We are currently investigating an issue impacting Kevel Ad Serving. We will keep you updating along the way.
Jul 31, 12:24 EDT Resolved - This incident has been resolved. Jul 31, 12:09 EDT Monitoring - We identified an issue impacting Forecast. Some instances were not responding to Forecast requests or Forecast API requests from ~15:15 UTC to ~15:55 UTC on July 31, 2025. A fix has already been deployed and we are monitoring.
We identified an issue with our ad publication and balancing systems that began on July 21, 2025, at 16:55 UTC. The issue was resolved on July 28, 2025, at 21:41 UTC. As a result, some customers may have experienced overdelivery of affected ads.
Jul 2, 17:13 EDT Resolved - This incident has been resolved. Jul 2, 17:03 EDT Identified - The issue has been identified and a fix is being implemented. Jul 2, 17:02 EDT Investigating - We identified an issue impacting ad publication starting 2025-07-02 20:10 UTC. Users might experience issues starting, stopping, and pausing ads; however, ad balancing is not impacted. An investigation is underway with our team. We'll keep you updated along the way.
We identified an issue impacting ad serving in us-east-1, beginning at 13:10 UTC. An investigation is underway with our team. We'll keep you updated along the way.
We have identified the issue and are working on a fix.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an increase in response times for Events (Impressions and Clicks) in EU Central 1 Region. An investigation is underway with our team. We'll keep you updated along the way.
This incident has been resolved.
We are currently investigating an issue that is causing degraded performance for UserDB endpoints in our US East Region. If a customer receives a 500 type error, it means that the attempted update to UserDB failed and will need to be retried.
We are continuing to investigate 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.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating an issue we have identified in our US East region which is causing high response times for UserDB endpoints.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Unauthenticated self-serve users may see incorrect branding on [yoursubdomain].campaign-dashboard.com. We are currently investigating this issue.
The issue has been identified and a fix is being tested.
We have implemented a fix and are monitoring the application
We are continuing to monitor for any further issues.
This incident has been resolved.
We have identified an issue with our Decision Request engine in the eu-west-1 region which started at 8:25 UTC. This issue will be impacting responses from the API in that region. We have resolved the issue and are actively monitoring the results.
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
This incident has been resolved.
Kevel Reporting system experienced a partial loss of functionality in reporting resulting in blank or stale campaign and flight auxiliary data. Performance metrics and entity ids were not impacted. Specifically, entity names, price, rate type and dates of campaigns and flights that were created or updated during the incident window would appear blank in reports generated during the same timeframe. This is now resolved. Newly created reports will contain correct and up to date campaign and flight auxiliary data. You may have to regenerate any reports that were created during the impacted timeframe. This issue started on 13 September 2024 10:00 AM UTC and was resolved 17 September 2024 11:00 AM UTC.
We're currently investigating a delay in reporting data ingestion that started at 8pm UTC, Saturday the 10th August.
We've identified what is causing the reporting data to not ingest correctly, and we're currently working on re-processing the historic data. No data loss has occurred.
Our team is continuing to work on reprocessing the historic data
Our team is continuing to work on reprocessing the historic data
Our systems are working on reprocessing the historic data
The ingest of the historic data is progressing, and a final update will be provided once we have confirmed that all historic data has been ingested correctly.
The ingest of historical data has now been complete, and we've been able to confirm data accuracy. This incident is now resolved.
Delay in all events ingestion from 3rd July 6pm UTC to 4th July 10AM UTC (16 hours). All of the data has now been backfilled and bucketed to the correct time.