Very Good Security outage history

September 7, 2026 14:44 UTC Identified - We are currently experiencing delays in webhook notification delivery. We have identified the root cause and are currently working on a mitigation. We will continue to keep you updated as we make progress. September 7, 2026 15:49 UTC Identified - Our team is actively working on a fix for the delayed webhook notifications and expects to apply it within the next hour. We will continue to monitor the situation closely and will post another update as soon as the fix is applied. September 7, 2026 17:02 UTC Identified - Our team is still working on a fix for the delayed webhook notifications. We continue to monitor the situation closely and will keep you updated as we make progress. September 7, 2026 19:54 UTC Monitoring - We can see recovery of the issue with webhooks. Our engineering team will keep monitoring the situation until full resolution of the issue. September 7, 2026 21:09 UTC Resolved - The issue affecting webhook services has been resolved. All services are fully stable and operating normally.

September 3, 2026 14:19 UTC Investigating - We are currently experiencing an issue affecting Mastercard Network Token and Account Updater services. This is due to an ongoing issue on Mastercard's side. Our team is in contact with Mastercard and working urgently to restore full service as quickly as possible. We will provide an update within 30 minutes. September 3, 2026 14:56 UTC Investigating - We are continuing to work with the Mastercard team to resolve the ongoing issues impacting the Network Token, Cryptogram, and Account Updater services. We do not yet have additional details to share, but remain actively engaged with Mastercard on a resolution. We will provide an update within 30 minutes. September 3, 2026 15:31 UTC Investigating - We continue to coordinate with Mastercard on resolving the issue impacting Network Token, Cryptogram, and Account Updater services. There have been no changes to report since our last update, and we remain in active contact with Mastercard to determine next steps. We will provide an update within 30 minutes. September 3, 2026 16:19 UTC Investigating - We remain in close contact with Mastercard as they work to resolve the issue impacting Network Token, Cryptogram, and Account Updater services. Mastercard has confirmed their engineering teams are actively engaged and investigating, and will share further updates as they become available. Our team continues to monitor the situation closely and will provide an update within 60 minutes. September 3, 2026 17:24 UTC Investigating - We continue to work closely with Mastercard on the issue impacting Network Token, Cryptogram, and Account Updater services. Mastercard's engineering teams remain actively engaged in investigating and have not yet shared additional details regarding an estimated resolution timeline. Our team continues to monitor closely and will provide an update within 60 minutes or sooner if we receive new information. September 3, 2026 17:53 UTC Investigating - We're currently experiencing intermittent failures affecting Mastercard. To minimize impact, we've made a temporary adjustment to our processing system that allows the majority of traffic to continue flowing normally. These failed requests are being tracked and will be re-processed once service is fully restored. No action is needed on your end. We appreciate your patience and will provide an update once everything is back to normal. September 3, 2026 18:53 UTC Investigating - We continue to work with Mastercard on the ongoing issue impacting Network Token, Cryptogram, and Account Updater services. Mastercard has confirmed the incident originated from an event at a third-party provider, and their engineering teams remain fully engaged in working toward a resolution. A resolution timeline has not yet been confirmed. We will provide our next update within 60 minutes, or sooner if we receive new information from Mastercard. September 3, 2026 19:17 UTC Monitoring - We continue to work with Mastercard on the ongoing issue impacting Network Token, Cryptogram, and Account Updater services. Over the last 15 minutes we have observed early signs of recovery, and our engineering team is closely monitoring system health and coordinating with Mastercard to confirm full service restoration. We will share our next update within 60 minutes, or sooner if we receive new information or confirm full recovery. September 3, 2026 20:27 UTC Monitoring - Both our engineering team and Mastercard are observing continued signs of recovery for Network Token, Cryptogram, and Account Updater services; however, we have been advised that service is not yet fully restored. We are continuing to monitor closely and coordinate with Mastercard on confirming full resolution. We will share our next update within 60 minutes, or sooner if we receive confirmation of full recovery from Mastercard. September 3, 2026 21:54 UTC Monitoring - Our engineering team is observing traffic across Network Token, Cryptogram, and Account Updater services returning to normal levels. We have not yet received official confirmation of full resolution from Mastercard and are treating the incident as ongoing until they confirm. In parallel, we will begin reprocessing requests affected during the incident. We will share our next update within 60 minutes September 3, 2026 23:21 UTC Monitoring - Live traffic across Network Token, Cryptogram, and Account Updater services has returned to normal levels and remains stable. We are still awaiting official confirmation of full resolution from Mastercard. The reprocessing of requests affected during the incident is underway and progressing as expected. Given the shift to reprocessing, our next update will be within 90 minutes, or sooner if we receive confirmation from Mastercard or reprocessing completes. September 4, 2026 01:15 UTC Monitoring - VGS systems for Network Token, Cryptogram, and Account Updater are operating normally. Mastercard's formal confirmation is still pending, but metrics on our side show services functioning as expected. The reprocessing of impacted requests is underway and progressing without issue. The next update will follow within 90 minutes, or sooner if reprocessing finishes or Mastercard provides confirmation. September 4, 2026 02:42 UTC Resolved - Reprocessing of affected requests is complete, and all VGS systems are operating normally. Our telemetry shows services are fully restored and stable on the VGS side. Given the sustained stability, we will be closing this incident on our status page, while continuing to monitor until we receive official confirmation from Mastercard.

September 1, 2026 19:10 UTC Investigating - We are currently experiencing a service disruption affecting all services in our sandbox environment. This issue is limited to the sandbox only — production services remain unaffected. Our team is actively investigating and working to restore full functionality as quickly as possible. We will share our next update within 45 minutes. September 1, 2026 19:28 UTC Identified - The issue affecting the VGS sandbox environment services has been identified. Our engineering team is actively working to mitigate the impact and restore normal performance as quickly as possible. We will share our next update within 45 minutes. September 1, 2026 19:58 UTC Monitoring - The sandbox environment services have returned to normal performance. Our team will continue monitoring closely to confirm full stability before marking this incident as resolved. We'll share a final update once resolution is confirmed. September 1, 2026 20:17 UTC Resolved - The issue affecting sandbox environment services has been resolved. All services are fully stable and operating normally. Thank you for your patience while we worked through this.

August 28, 2026 14:55 UTC Investigating - CMP is experiencing intermittent failures on write operations. Some write requests are failing; the rest complete normally. Read operations are unaffected. Our engineering team is actively working on a resolution, and we'll share our next update within 30 minutes. August 28, 2026 15:32 UTC Monitoring - Write operations to CMP have resumed and are succeeding normally, and the issue has been mitigated. Read operations were unaffected. Our team continues to closely monitor system performance to ensure continued stability. We'll share our next update within 30 minutes. August 28, 2026 16:09 UTC Resolved - The issue affecting CMP has been resolved, and the service is operating normally. Thank you for your patience while we worked through this.

August 24, 2026 10:03 UTC Identified - We are currently experiencing issues with delayed webhooks. Our team is actively working on the fix. We will share new updates within the next hour. August 24, 2026 11:37 UTC Identified - Our engineers have released the fix that partially mitigates the issue. Now we are working on the final development to resolve the issue of delayed webhooks. We still observe the delay in webhook delivery. August 24, 2026 13:44 UTC Identified - Our engineers continue working on the additional development work to resolve this issue. We will provide the next update within the next 60 minutes. August 24, 2026 15:02 UTC Monitoring - Our engineering team has deployed an additional fix, and the system is now processing the delayed webhooks. The team is monitoring the system and its progress towards processing the queue. We will provide the next update within the next 60 minutes. August 24, 2026 16:27 UTC Monitoring - Our engineering team's monitoring shows that the underlying issue has been mitigated. We are working through processing the backlog of delayed webhooks and expect delivery to catch up later today. We will post another update once the backlog has fully cleared. August 24, 2026 18:58 UTC Monitoring - As we continue to recover from the earlier incident, some webhooks may be delivered out of order. Newly generated events can arrive before delayed webhooks that are still in our backlog. We estimate the remaining backlog will be fully cleared within approximately 5 hours. In the meantime, we recommend performing a GET request upon receiving any webhook, as our system will always reflect the most current data for the associated card. We will continue to share updates as we make progress, with our next update scheduled for 21:00 UTC. August 24, 2026 21:40 UTC Monitoring - The backlog of events continues to clear; however, current estimates are that the queue will take approximately 4 hours to clear. We will share our next progress update around 23:30 UTC August 24, 2026 23:33 UTC Monitoring - Our event backlog is continuing to clear, we estimate the remaining queue should be fully caught up in about 3 hours. Thanks for your patience, we'll share our next update around 2:30 UTC, or sooner if the backlog clears early. August 25, 2026 02:24 UTC Monitoring - Progress on clearing the event backlog is taking slightly longer than expected. We currently estimate another 3 hours to fully process the remaining queue. We will share our next progress update around 5:30 UTC, or as soon as the backlog clears. August 25, 2026 05:34 UTC Monitoring - The event backlog continues to clear. Based on current progress, we estimate the remaining queue should be fully processed in approximately 3 hours. We will share our next progress update around 7:30 UTC, or as soon as the backlog clears. August 25, 2026 07:53 UTC Resolved - After close monitoring, we have confirmed that the event backlog has been cleared and webhook delivery is operating as expected.

August 24, 2026 15:34 UTC Identified - 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. August 24, 2026 16:05 UTC Identified - 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. August 24, 2026 16:15 UTC Monitoring - 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. August 24, 2026 16:16 UTC Monitoring - 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. August 24, 2026 17:01 UTC Resolved - 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.

August 13, 2026 18:34 UTC Investigating - We are investigating elevated error rates affecting a subset of Mastercard Account Updater enrollment requests in our Live environment. We will provide the next update within 30 minutes. August 13, 2026 19:15 UTC Investigating - Our engineering team has identified a likely cause of the elevated errors affecting a subset of Mastercard Account Updater requests and is working to confirm it and apply a fix. We will provide the next update within 45 minutes. August 13, 2026 20:01 UTC Identified - Our engineering team has identified the issue and is working on a solution to resolve the subset of errors impacting Mastercard Account Updater enrollment requests. We will provide the next update within 1 hour. August 13, 2026 21:17 UTC Identified - Our engineering team has applied a fix to resolve this issue. We are now monitoring error rates to confirm recovery. We will provide the next update within 1 hour. August 13, 2026 22:26 UTC Resolved - Our engineering team applied an additional fix, and after monitoring, Mastercard Account Updater enrollment requests are processing successfully, and we are no longer seeing the subset of errors.

August 3, 2026 23:58 UTC Scheduled - VGS will be performing a scheduled upgrade on the CMP Live environment. During this maintenance window, no customer downtime is expected. August 10, 2026 16:00 UTC Active - Scheduled maintenance is starting. August 10, 2026 21:00 UTC Completed - Scheduled maintenance is complete.

July 27, 2026 22:47 UTC Scheduled - VGS will be performing a scheduled upgrade on the CMP Sandbox environment. During this maintenance window, no customer downtime is expected. July 31, 2026 16:00 UTC Active - Scheduled maintenance is starting. July 31, 2026 18:00 UTC Completed - Scheduled maintenance is complete.

July 23, 2026 23:03 UTC Investigating - We are currently experiencing a service disruption affecting the VGS EU environment. Our engineering team is actively investigating the root cause and working to restore normal operations as quickly as possible. We will provide another update as soon as more information becomes available. July 23, 2026 23:41 UTC Identified - The issue affecting VGS EU environment services has been identified. VGS engineering team is actively working on mitigating the impact and restoring normal performance as quickly as possible. We will share another update once mitigation is complete or new details are available. July 24, 2026 00:48 UTC Identified - The VGS engineering team is continuing to actively work on mitigating the impact and restoring normal performance as quickly as possible. We will share another update once mitigation is complete or as new details become available. July 24, 2026 02:19 UTC Identified - The Vault API for the EU environment has been successfully restored. The VGS engineering team is continuing with restoration for all remaining impacted services to bring the environment back to full performance. We will share another update within the next hour or as soon as new details become available. July 24, 2026 02:41 UTC Monitoring - All services for the EU environment have been successfully restored. We are currently monitoring system stability to ensure full recovery. Thank you for your continued patience. July 24, 2026 03:30 UTC Resolved - After close monitoring, we have confirmed that all services for the EU environment are stable and operating normally. No further issues have been observed.

July 16, 2026 00:51 UTC Investigating - We are currently investigating an issue affecting Mastercard Network Token Notifications. Notifications for token activation, updates, deletions, and suspensions may be delayed. All other card networks continue to operate normally. We will provide updates as more information becomes available. July 16, 2026 02:33 UTC Investigating - We are continuing our investigation into this issue and have confirmed with the network that it requires further review by their team. Mastercard Network Token Notifications for token activation, updates, deletions, and suspensions continue to be delayed. We are working closely with the network to resolve this and will provide another update as soon as we have more information. July 16, 2026 04:08 UTC Identified - Our teams have identified the root cause of this issue, and the network team is currently working on a fix. We are monitoring the situation closely and will provide another update as progress is made on deploying the fix. July 16, 2026 07:37 UTC Monitoring - The network team has successfully deployed the fix, and we are seeing Mastercard Network Token Notifications return to normal levels. Notifications for token activation, updates, deletions, and suspensions are processing as expected, and we have not observed any further delays since the deployment. Our team will continue to monitor the service closely to ensure continued stability. July 16, 2026 09:00 UTC Resolved - After an extended period of close monitoring, we have confirmed that the issue affecting Mastercard Network Token Notifications is fully resolved.

June 15, 2026 21:36 UTC Investigating - We are currently investigating a partial degradation of the SFTP Proxy and Managed File Tokenization services on the VGS Sandbox. Users may experience intermittent latency, timeouts, or failed connections when making SFTP proxy requests in the Sandbox environment. Our engineering team is actively diagnosing the root cause to restore full performance. We will provide updates as more information becomes available. June 15, 2026 22:52 UTC Investigating - Our engineering team is continuing to investigate the degraded performance of the SFTP Proxy and Managed File Tokenization services on the VGS Sandbox. We are actively working to identify the root cause and restore full functionality. We will provide further updates as more information becomes available. June 16, 2026 00:13 UTC Identified - Our engineering team has identified the root cause of the degraded performance of the SFTP Proxy and Managed File Tokenization services on the VGS Sandbox. Our team is actively working on deploying a solution. We will provide another update no later than 1:30 UTC. June 16, 2026 01:35 UTC Monitoring - Our engineering team has deployed a fix for the degraded performance of the SFTP Proxy and Managed File Tokenization services on the VGS Sandbox. We are currently monitoring the system to confirm the issue is fully resolved. Please expect the next update no later than 2:30 UTC. June 16, 2026 02:38 UTC Monitoring - We have confirmed that SFTP Proxy in Sandbox is operating as expected. Our team is continuing to test and monitor MFT performance in the sandbox to ensure full functionality. We will provide another update once full functionality is confirmed June 16, 2026 07:21 UTC Resolved - The MFT and SFTP Proxy in the Sandbox have been confirmed operational and are performing as expected.

June 15, 2026 05:06 UTC Investigating - We are currently investigating an issue where users are unable to create or update routes in the Sandbox environment. Our engineering team is actively working to resolve this. We will provide a further update soon. June 15, 2026 05:55 UTC Monitoring - The route creation and update functionality has been restored in the Sandbox environment. We are actively monitoring to ensure continued stability and will provide further updates as needed. June 15, 2026 06:01 UTC Resolved - The route creation and update functionality in the Sandbox environment has been fully restored. All operations are now functioning as expected.

May 15, 2026 11:37 UTC Scheduled - VGS will be performing a scheduled maintenance on the LIVE-US environment. During this maintenance window, customers may experience brief periods of elevated response latency for up to 1 minute, and possibly 5xx responses. May 21, 2026 10:00 UTC Active - Scheduled maintenance is starting. May 21, 2026 11:00 UTC Completed - Scheduled maintenance is complete.

May 14, 2026 00:29 UTC Scheduled - VGS will be performing scheduled maintenance on the LIVE environment. During this maintenance window, the creation of new organizations and vaults, new user registrations, new service account creation, and updates to SSO configurations will be temporarily unavailable. The VGS Dashboard will operate in read-only mode for the duration of this window. Customers may experience brief periods of elevated response latency for up to 1 minute, and possibly 5xx responses. May 18, 2026 06:00 UTC Active - Scheduled maintenance is starting. May 18, 2026 08:59 UTC Active - The scheduled maintenance on the LIVE environment has been extended to 12 PM UTC and is still ongoing. Customers may continue to experience brief periods of elevated response latency and possible 5xx responses. We are actively working to complete the maintenance as quickly as possible and will provide another update once it concludes. May 18, 2026 10:26 UTC Completed - Scheduled maintenance is complete.

May 17, 2026 09:32 UTC Investigating - We are currently experiencing partial performance degradation affecting the Forward HTTP Proxy service. Our engineering team is actively investigating the issue and working to restore full performance as quickly as possible. We appreciate your patience and will provide further updates as more information becomes available. May 17, 2026 10:19 UTC Investigating - We are continuing to investigate performance degradation affecting both Forward and Reverse Proxy services. Our Engineering team is actively working to identify the cause and restore full performance. We will provide further updates as soon as more information becomes available. May 17, 2026 11:08 UTC Monitoring - Our Engineering team has applied improvements, and we are now seeing service performance recover. The service has been operating normally for the last 30 minutes. We continue to closely monitor the situation to ensure stability and will share further updates as more information becomes available. May 17, 2026 12:03 UTC Resolved - After close monitoring, we have confirmed that the HTTP proxy service is stable and operating normally. No further issues have been observed.

May 4, 2026 19:49 UTC Scheduled - VGS will be performing scheduled maintenance on the LIVE-EU environment. During this maintenance window, the creation of new organizations and vaults, new user registrations, new service account creation, and updates to SSO configurations will be temporarily unavailable. The VGS Dashboard will operate in read-only mode for the duration of this window. Customers may experience brief periods of elevated response latency for up to 1 minute, and possibly 5xx responses. May 13, 2026 18:00 UTC Active - Scheduled maintenance is starting. May 13, 2026 22:00 UTC Completed - Scheduled maintenance is complete.

May 4, 2026 19:42 UTC Scheduled - VGS will be performing scheduled maintenance on the LIVE AP environment. During this maintenance window, the creation of new organizations and vaults, new user registrations, new service account creation, and updates to SSO configurations will be temporarily unavailable. The VGS Dashboard will operate in read-only mode for the duration of this window. Customers may experience brief periods of elevated response latency for up to 1 minute, and possibly 5xx responses. May 12, 2026 12:00 UTC Active - Scheduled maintenance is starting. May 12, 2026 16:00 UTC Completed - Scheduled maintenance is complete.

May 8, 2026 00:56 UTC Investigating - Our engineering team is monitoring an active incident reported by AWS in us-east-1, including elevated DynamoDB API errors and EC2 instance availability issues in one availability zone. VGS operates across multiple availability zones; however, the DynamoDB issue is region-wide. You may have observed brief intermittent errors from VGS services starting around 23:38 UTC. A total service interruption is not expected, but you may continue to experience intermittent errors or minor latency while this issue persists. We apologize for any inconvenience and will continue to provide updates as AWS works toward a resolution. For more details on the AWS incident, see: https://health.aws.amazon.com/health/status May 8, 2026 02:14 UTC Monitoring - Our team is continuing to monitor the incident with AWS in us-east-1. You may experience intermittent errors or latency from VGS services while this persists. For details: https://health.aws.amazon.com/health/status May 8, 2026 03:21 UTC Monitoring - Our team continues to monitor the AWS incident in us-east-1. AWS has indicated that progress toward resolution is slower than anticipated. You may continue to experience intermittent errors or latency from VGS services during this time. We expect to receive the next update from their team by 10:00 PM PDT. For details: https://health.aws.amazon.com/health/status May 8, 2026 05:27 UTC Monitoring - Our team continues to monitor the AWS incident in us-east-1. AWS is observing early signs of recovery. You may still see some intermittent errors or latency from VGS services until full recovery is achieved. We expect to receive the next update from their team by 11:30 PM PDT. For details: https://health.aws.amazon.com/health/status May 8, 2026 06:53 UTC Monitoring - Our team continues to monitor the AWS incident in us-east-1. The AWS team is working towards recovery for the impacted components. You may still see some intermittent errors or latency from VGS services until full recovery is achieved. We expect to receive the next update from their team by 01:30 AM PDT. For details: https://health.aws.amazon.com/health/status May 8, 2026 08:54 UTC Monitoring - Our team continues to monitor the AWS incident in us-east-1. The AWS team is still working toward full recovery for the impacted components, though it is taking longer than initially anticipated. You may still see some intermittent errors or latency from VGS services until full recovery is achieved. We expect to receive the next update from their team by 03:30 AM PDT. For details: https://health.aws.amazon.com/health/status May 8, 2026 11:10 UTC Monitoring - Our team continues to monitor the AWS incident in us-east-1. The AWS team is making progress on recovery, though full resolution is expected to take several more hours. You may still see some intermittent errors or latency from VGS services until full recovery is achieved. We expect to receive the next update from their team by 6:30 AM PDT. For details: https://health.aws.amazon.com/health/status May 8, 2026 14:06 UTC Monitoring - Our team continues to monitor the AWS incident in us-east-1. The AWS team is actively working towards full recovery, though it is still expected to take several more hours. You may still see some intermittent errors or latency from VGS services until full recovery is achieved. We expect to receive the next update from their team by 9:00 AM PDT. For details: https://health.aws.amazon.com/health/status May 8, 2026 20:14 UTC Monitoring - Our team continues to monitor the ongoing AWS incident in us-east-1. Recovery is progressing more slowly than previously anticipated, and some VGS services may continue to experience intermittent errors or degraded performance for the next several hours. We will provide another update by 4:00 PM PDT or sooner if the situation changes. For details: https://health.aws.amazon.com/health/status May 8, 2026 23:30 UTC Monitoring - We are seeing positive signs of progress on the AWS incident in us-east-1. The number of affected services is beginning to improve, though some intermittent errors or degraded performance may persist while recovery efforts continue. We will provide another update as soon as we have new information. For details: https://health.aws.amazon.com/health/status May 8, 2026 23:49 UTC Resolved - AWS continues to work toward full resolution of the underlying incident in us-east-1, and their traffic mitigation efforts appear to have addressed potential instability on our end. Our team's monitoring has seen no impact to VGS services today. We will continue to monitor internally until the AWS incident is resolved and will reopen this incident if any impairment to VGS services is detected.

May 7, 2026 02:43 UTC Scheduled - VGS will be performing scheduled maintenance on all Sandbox environments. During this maintenance window, CMP and Vault services will be impacted. Customers may experience brief periods of elevated response latency for around 1-2 minutes during this window. May 7, 2026 16:00 UTC Active - Scheduled maintenance is starting. May 7, 2026 17:00 UTC Completed - Scheduled maintenance is complete.