All Systems Operational

Uptime over the past 90 days. View historical uptime.
Kayzen UI Operational
90 days ago
100.0 % uptime
Today
Bidding Operational
90 days ago
98.92 % uptime
Today
Reporting and Data Operational
90 days ago
99.39 % uptime
Today
Audiences Operational
90 days ago
96.33 % uptime
Today
Kayzen APIs Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Feb 19, 2026

No incidents reported today.

Feb 18, 2026

No incidents reported.

Feb 17, 2026

No incidents reported.

Feb 16, 2026
Ad serving impacted for Frequency Cap Enabled Campaigns
Resolved - On Feb 17th, 2026 our backend pipeline for Frequency cap underwent scheduled maintenance, affecting ad serving from 04:15 AM to 04:44 AM UTC on orders/campaigns with Frequency cap enabled.

No impact occurred on orders/campaigns without Frequency cap.

Ad serving has returned to normal. We apologise for any inconvenience caused.
Feb 16, 22:30 UTC
Bidding Impacted
Resolved - We would like to inform you about a technical issue that occurred on 16 February 2026 between 22:24 UTC and 23:06 UTC, during which ad serving was impacted globally.
The issue has been fully resolved, and bidding is now operating normally.
Feb 16, 17:00 UTC
Feb 15, 2026

No incidents reported.

Feb 14, 2026
Audience Processing Impacted
Resolved - This incident has been resolved.
Feb 14, 08:56 UTC
Update - We are continuing to work on a fix for this issue.
Feb 13, 13:41 UTC
Identified - We are currently experiencing a technical issue with the Audience pipeline, which means that new audiences and updates to existing audiences will not be processed until the issue is resolved.

- In the UI, the status for any new audience will appear as “Processing,” and campaigns attached to a new audience (file- or URL-based) will not serve.
- Existing audiences may temporarily show a status of “Processing” or “Failed”; however, campaigns linked to these audiences will continue to serve using previously processed data.

We do not yet have an estimated time of resolution, but we will keep you informed as we make progress.
If you have any questions, please reach out via the chat widget.
Feb 12, 13:26 UTC
Feb 13, 2026
Feb 12, 2026
Feb 11, 2026

No incidents reported.

Feb 10, 2026

No incidents reported.

Feb 9, 2026
Ad serving impacted for Applist targeted Campaigns
Resolved - We experienced a technical issue between 06:45 UTC and 07:05 UTC, 9th Feb 2026 that have affected campaigns where:

1. A new Applist was created and attached to the campaign, or an existing Applist already attached was modified.
2. A Placement ID is manually blacklisted via the campaign detail page.

These campaigns stopped bidding and ad serving was disrupted. Campaigns without Applists, or those where no changes were made to Applists, were unaffected.
We apologise for the inconvenience. Please reach out if you have any questions.
Feb 9, 01:00 UTC
Feb 8, 2026

No incidents reported.

Feb 7, 2026
Reporting Delay
Resolved - On 7 February 2026, we experienced a temporary reporting delay between 17:30 UTC and 19:00 UTC due to a technical issue.
During this window, reporting for the following metrics may have been delayed:

Installs
Events
Conversions

The issue was fully resolved at 19:00 UTC, and reporting has since been fully restored.
This incident was limited to reporting only — bidding and ad serving were not impacted.
We apologize for any inconvenience this may have caused. If you continue to notice any discrepancies, please reach out via the support chat in the platform.
Feb 7, 12:00 UTC
Feb 6, 2026

No incidents reported.

Feb 5, 2026
Bidding Impacted - Singapore DC
Resolved - This incident has been resolved as of 06:08 UTC.
Feb 5, 07:07 UTC
Identified - We wanted to inform you about a technical issue that we are experiencing from 04:45 UTC, 5th Feb 2026 with our Singapore Datacenter. Due to which ad serving primarily across APAC region is impacted. We will keep you posted on further updates.
Feb 5, 05:21 UTC
← Incident History Powered by Atlassian Statuspage