Transcend had 17 outages in the last 2 years totaling 86h 35m of downtime — averaging 0.7 incidents per month.
There were 17 Transcend outages since February 21, 2025 totaling 86h 35m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
We are currently investigating this issue.
A fix has been implemented and we are seeing the application fully work again. We are continuing to monitor as traffic picks back up to ensure performance continues as expected.
We are seeing some tasks begin to fail again
We have identified the code change that is causing the issue, and are working to roll out a release. We expect a partial outage in the EU region of our backend while this fix is released
Our deploy has completed, and our metrics are looking good. We will continue to monitor the EU and the US backend, but both are resolving with normal responses and we have a good understanding of what caused this issue.
We are currently investigating performance issues with our Admin Dashboard
We are continuing to investigate this issue.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
The Admin Dashboard is operational. Some pages for some organizations remain in the loading state indefinitely. Interacting with the navigational sidebar can prompt pages to load. We are continuing to investigate this issue.
The Admin Dashboard is fully operational. Pages no longer hang in a loading state.
This incident has been resolved.
We are currently investigating performance issues with our backend API.
We have identified a fix and are scaling our infrastructure to accommodate extreme API demand. The first-order impact to load times in the Admin Dashboard were fixed overnight and we are monitoring results this morning (Pacific Time). The second-order impact on DSR processing times is our focus this morning, and infrastructure scaling is underway.
We have successfully scaled our infrastructure up to accommodate the increased API demand in the EU region. Backend performance is now healthy. However, the secondary effect of the recent backend performance degradation is that a backlog of DSRs have accrued. The backlog is actively being processed now. We will keep this incident open until that DSR processing pipeline returns to normal levels.
The DSR backlog is now down to normal levels. Incoming DSRs should process as per usual.
We are currently investigating an issue with our CDN cache invalidation, which impacts Consent deployments.
We've determined this is an issue with our CDN Provider, and are currently helping their escalation team investigate further.
We're continuing to investigate with our provider. Note that this issue only impacts publishing updates to airgap.js bundles - existing consent deployments continue to function as expected.
Our CDN provider has identified and fixed a cache purging issue. Updates to Consent bundles should now deploy as expected. For more information, see https://www.cloudflarestatus.com/incidents/vft3jf8tvnv2
We are currently investigating this issue.
Our systems in the EU are under increased load and we are scaling up to meet demand.
A fix has been implemented and we are monitoring the results.
This issue has been resolved, with latency returning to normal levels since 1:28 PM PDT.
Email sending is occasionally failing. We are investigating the issue.
We are continuing to investigate this issue.
Email sending has resumed.
This incident has been resolved.