Very Good Security experienced a major incident on August 24, 2026 affecting 3DS and Echo Server (Echo Server — Live US), lasting 1h 26m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Aug 24, 2026, 03:34 PM UTC
We are currently experiencing an incident involving our production 3DS services caused by a recent change to response formats. Our team is actively working with our 3DS provider on a fix to address this issue. We will provide an update within the next 30 minutes. Back to current status Status History Powered by Status.io Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription
- identified Aug 24, 2026, 03:34 PM UTC
We are currently experiencing an incident involving our production 3DS services caused by a recent change to response formats. Our team is actively working with our 3DS provider on a fix to address this issue. We will provide an update within the next 30 minutes.
- identified Aug 24, 2026, 04:05 PM UTC
We have identified the cause of the 3DS service disruption and a fix is being deployed to production now. We will confirm once recovery is complete and will provide another update within the next 30 minutes.
- identified Aug 24, 2026, 04:05 PM UTC
We have identified the cause of the 3DS service disruption and a fix is being deployed to production now. We will confirm once recovery is complete and will provide another update within the next 30 minutes.
- monitoring Aug 24, 2026, 04:15 PM UTC
The fix has been deployed to production and 3DS services have recovered. We are actively monitoring to confirm stability and will provide a final update once the incident is resolved.
- monitoring Aug 24, 2026, 04:15 PM UTC
The fix has been deployed to production and 3DS services have recovered. We are actively monitoring to confirm stability and will provide a final update once the incident is resolved.
- monitoring Aug 24, 2026, 04:16 PM UTC
The fix has been deployed to production and 3DS services have recovered. We are actively monitoring to confirm stability and will provide a final update once the incident is resolved.
- monitoring Aug 24, 2026, 04:16 PM UTC
The fix has been deployed to production and 3DS services have recovered. We are actively monitoring to confirm stability and will provide a final update once the incident is resolved.
- resolved Aug 24, 2026, 05:01 PM UTC
This incident has been resolved. The fix has been deployed and our production 3DS services have been operating normally throughout our monitoring period. We apologize for the disruption and thank you for your patience.