Slowdowns on primary backend
Timeline · 1 update
- resolved Sep 29, 2026, 06:36 PM UTC
A longrunning database migration caused slower performance on a key database, but performance has now been restored
Transcend had 12 outages in the last 2 years totaling 43h 32m of downtime — averaging 0.5 incidents per month.
There were 12 Transcend outages since October 20, 2025 totaling 43h 32m of downtime. Each is summarised below — incident details, duration, and resolution information.
A longrunning database migration caused slower performance on a key database, but performance has now been restored
The GET and POST /sync routes in the Consent Backend experienced a temporary performance degradation beginning at approximately 16:30 EST, resulting in elevated response times and increased 5xx error responses. A fix was implemented in the caching layer, which resolved the issue at approximately 17:00 EST.
There was a brief delay in processing DSRs triggered by consent preference changes. Normal service has been restored.
Telemetry for airgap.js is down for all US based organizations. We're investigating the root cause and will provide an update soon
This incident has been resolved.
We are currently investigating an issue causing increased latency and intermittent timeouts across our backend API services. Users may experience slower response times or occasional request failures when interacting with the platform.
We are continuing to investigate this issue.
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 experiencing a partial disruption impacting the Preference Management Service. Calls to update user preferences are intermittently failing with 5xx errors. Our team is actively working to resolve the issue. We will share further updates as progress is made.
This incident has been resolved.
We are investigating an issue where preference updates submitted via the Privacy Center, Admin Dashboard, or API are not triggering configured consent workflows. Preference data is being stored correctly — no records have been lost. Downstream workflow actions (e.g., third-party integrations, automated notifications) triggered on preference change events have not fired since March 25 at 19:33 UTC. We have identified the root cause and a fix is in progress. We will provide an update once resolved and will communicate a backfill plan for affected workflows.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
The incident has been resolved.
Our Consent backend API "/sync" (GET and POST routes) experienced a brief service disruption between 17:20 UTC and 17:34 UTC on March 17 2026. During this time, calls to update or retrieve user preferences from the client-side arigap.js script may have failed with a 500 error status code. The issue has since been resolved and the service is operating normally.
Our Consent backend sync API experienced a major outage for approximately 1 hour between 8:23PM EST TO 9:24PM EST. During this time, calls to update the user's preferences from client side airgap.js script would have failed with a 500 error status code. At this time the issue has resolved.
In the EU region, our Consent Backend API experienced a major outage for approximately 19 minutes. During this time, calls to update the user's preferences would have failed with a 500 error status code. We are still investigating the scope of impact, but at this time we expect this issue to self-heal, as the Consent clients have built-in retries.
Our EU based privacy centers, like privacy.transcend.io for our own, were rejecting many requests to submit data subject requests during this time period. The privacy centers themselves would still load fine to display the privacy practices and options that a user could submit. This incident is now fully resolved.
We are seeing some 500 errors on our backend API service. Currently, our service appears to be alive in both the Europe and US-based backend regions, though more errors are happening on the US-backend.
Our error rates for our core backend services have remained very low and within normal bounds for the past hour. We do still have some downstream dependencies that are unavailable, resulting on some of our offline processes queuing up information to send to these third parties once they are available. As a result, a few specific areas of our application may take time to recover to normal operations.
We are seeing degraded performance on the EU backend, with requests timing out. We are still investigating the scope of impact.
Requests to EU backend are no longer timing out after a restart of the multi-tenant Sombra clusters. Our core backend error rates for both EU & US regions continue to remain low and within normal bounds for the past hour.
We've implemented recommended mitigations from our upstream vendors, which has allowed our systems to fully recover. Some Airgap.js telemetry information may encounter processing delays, as our systems catch up.