Kevel had 20 outages in the last 2 years totaling 33h 37m of downtime — averaging 0.8 incidents per month.
There were 20 Kevel outages since November 25, 2024 totaling 33h 37m of downtime. Each is summarised below — incident details, duration, and resolution information.
Between approximately 06:30 and 06:42 UTC on October 15, 2026, ad serving in EU-Central-1 experienced elevated response times and intermittent errors on decision requests. Service has recovered, and no customer action is required.
We are currently investigating an issue impacting some users saving changes made to Ads through the Ad Server UI. Changes made through the Management API are not affected. We have identified a likely cause and are working to resolve it.
A fix has been deployed and saving changes in the Ad Server UI is working as expected. We are continuing to monitor.
Confirming this is now resolved. Please find a summary below. Between ~19:38 and ~22:35 UTC on September 17, 2026, saving an ad through the Ad Server UI may have returned an error even though the change was applied successfully. Users who retried after seeing the error may have created duplicate ads. We recommend reviewing any ads created or edited during this window and removing any duplicates.
Between 21:36 and 21:54 UTC on September 9, 2026, ad serving in US-East-1 experienced elevated response times and intermittent errors on decision requests. Service recovered on its own, and no customer action is required.
We are currently investigating an issue that is causing degraded Ad Serving for customers in the EU Central 1 region.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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 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.
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.
We are currently investigating an issue impacting Kevel Ad Serving. We will keep you updating along the way.
We have identified the issue and are working on a fix.
A fix has been implemented for most impacted customers. We are deploying the fix to the remaining impacted customers and monitoring.
This incident has been resolved.
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.
This incident has been resolved.
We identified an issue with our ad publication and balancing systems starting at 22:23 UTC on July 23, 2025. The issue was resolved at 17:12 UTC on July 24, 2025. Some customers may have experienced underdelivery on affected ads.
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.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
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.