CData Cloud Outage History

16 incidents recorded over the last 365 days, 8 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded CData Cloud Incident

CData Cloud incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 1, 2026Service Interruption: Arc Cloud/Sync Cloud - Azure Database MaintenanceSummary: Between 02:24 - 03:36 UTC on November 1, 2026, several customers experienced intermittent connectivity issues or total unavailability of their Arc Cloud and Sync Cloud instances. Our platform engineering team…0 minResolved
Sep 27, 2026Scheduled Maintenance of Arc/Sync - Upstream ProviderThe scheduled maintenance has been completed.1h 0mScheduled
Aug 28, 2026Scheduled Maintenance for Connect AIThe scheduled maintenance has been completed.3h 0mScheduled
Aug 27, 2026Scheduled Maintenance For Arc and SyncThis maintenance is complete3h 0mScheduled
Aug 16, 2026Scheduled Maintenance for Arc and Sync (Upstream Provider)The scheduled maintenance has been completed.1h 0mScheduled
Aug 13, 2026Connect AI - DownThe DNS record conflict affecting cloud.cdata.com has been completely resolved. All systems are operational, and routing through Cloudflare is fully restored. We apologize for any inconvenience caused.36 minResolved
Aug 9, 2026Scheduled Maintenance For Arc and Sync (Upstream Provider)The scheduled maintenance has been completed.1h 0mScheduled
Jun 24, 2026Connect AIThis incident has been resolved.6 minResolved
Mar 25, 2026Degraded Performance due to Metadatacache — Connect AI (Resolved)[RESOLVED] We have resolved the issue affecting Connect AI performance. All systems are operating normally. Impact: Users may have experienced slow connection response times, delayed query execution, or timeouts during…-1692 minResolved
Mar 22, 2026Scheduled Maintenance For Arc and SyncThe scheduled maintenance has been completed.1h 0mScheduled
Mar 15, 2026Service Interruption: Arc Cloud/Sync Cloud - Azure Database MaintenanceStatus: Resolved Summary: Between 02:05 - 03:17 UTC, several customers experienced intermittent connectivity issues or total unavailability of their instances. Our platform engineering team identified the cause as a…0 minResolved
Jan 16, 2026Scheduled Maintenance For Arc and SyncThe scheduled maintenance has been completed.3h 0mScheduled
Jan 14, 2026Issue with reauthenticating Oauth connectionsThis incident has been resolved.2h 8mResolved
Jan 12, 2026Scheduled Maintenance for Connect CloudThe scheduled maintenance has been completed.3h 0mScheduled
Jan 5, 2026Connect AI Dashboard UI outageThis incident has been resolved.5h 45mResolved
Nov 10, 2025Sync and Arc cloud outage affecting European instances.This incident has been resolved.1h 6mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next CData Cloud incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This CData Cloud Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before CData Cloud acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single CData Cloud outage in this window ran 5h 45m, against a mean recovery of 1h 43m. If you depend on CData Cloud in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.