Is Acceldata Data Observability Cloud Down Right Now? Live Acceldata Data Observability Cloud Status & Outages | IsDown had 17 outages in the last 2 years totaling 63h 34m of downtime — averaging 0.7 incidents per month.
There were 17 Is Acceldata Data Observability Cloud Down Right Now? Live Acceldata Data Observability Cloud Status & Outages | IsDown outages since July 17, 2025 totaling 63h 34m of downtime. Each is summarised below — incident details, duration, and resolution information.
There will be a scheduled system maintenance for routine infrastructure activities. There might be a slight disruption in certain services during this period.
We identified an issue that caused delays in the processing of platform events. As a result, some customers may have experienced delayed updates or notifications within the platform. Our team investigated the issue and implemented corrective actions to restore normal processing. Services are operating normally, and we continue to monitor the environment to ensure stability.
We are currently observing a degraded performance in the pipeline services. The team is investigating the issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently observing increased traffic impacting pipeline services. Mitigation actions, including scaling measures, are being implemented to improve system stability and observability. Our team continues to monitor the situation closely.
This incident has been resolved.
On May 11, 2026, a particular Kafka consumer group in US Production experienced degraded processing performance caused by CPU saturation and worker thread exhaustion within the pipeline application. This resulted in increased Kafka consumer lag and delayed pipeline processing, but there was no outage, data loss, or user-facing errors. Mitigation actions included provisioning a dedicated node group with increased resources, scaling the application, and applying deployment optimisations. Service performance recovered fully following the changes and continued monitoring confirmed system stability.
Following a production release after scheduled maintenance on May 10, 2025, the Catalog Service experienced degraded performance and delayed startup due to a stalled PostgreSQL migration holding locks on a critical database table. This impacted catalog-related operations for approximately 15 minutes. The issue was mitigated by terminating the blocking queries and restoring normal service operation. Preventive measures are being implemented to improve migration controls and reduce the risk of similar issues during future deployments.
The admin-central service experienced temporary performance degradation due to increased load on a dependent authentication component. Mitigation steps have been applied, and the service performance has returned to normal.
We are currently experiencing performance degradation affecting parts of our system. Our team has identified the issue and is actively working on a fix. Estimated time to resolution is approximately 40 minutes. We will provide further updates soon. Thank you for your patience.
The database load unexpectedly spiked to 100%, causing noticeable application performance degradation. A rollout restart was performed, which successfully restored the database load to normal operating levels. We are currently investigating the underlying root cause and will continue to monitor the system closely. Operations have returned to normal, and the application is functioning as expected.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Authentication and authorization APIs were down due to an AdminCentral service outage. Fix has been applied.
We identified that the Pendo API was causing slowness in UI page loading. We are applying fix
This incident has been resolved.
The Snowflake service experienced downtime due to high storage load. The issue was mitigated through remediation steps, and the service is now stable.
We are currently investigating this issue.
This incident has been resolved.
The Catalog service experienced downtime due to high database load. We mitigated the issue by optimising the database performance and managing parallelism on long running queries Service is now stable.
The Pipeline Service is currently down. as the 4.6.0 Upgrade, including the migration, is took longer than expected.
Cadence/profile anomaly detection affected.