Is Very Good Security down?

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. 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

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.

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.

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.

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.

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.

After close monitoring, we have confirmed that the HTTP proxy service is stable and operating normally. No further issues have been observed.

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

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

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

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

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

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

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

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

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

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

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.

We are investigating a delay in log delivery to the VGS Dashboard. Our engineering team has been notified and is actively looking into the issue. We appreciate your patience as we resolve this.

We are investigating a delay in log delivery to the VGS Dashboard. Our engineering team has been notified and is actively looking into the issue. We appreciate your patience as we resolve this.

Our engineering team is continuing to investigate the log delivery delay affecting the VGS Dashboard. We are actively working to restore delivery times to normal levels and will share another update shortly.

The log delivery delays on the VGS Dashboard have been mitigated. We are now seeing logs flowing to the dashboard, and we are monitoring the service as it continues to stabilize and catch up. Thank you for your patience.

We are currently experiencing a minor delay in delivering logs to the VGS Dashboard. Our engineering team is actively investigating the issue and working to reduce log latency back to normal levels. We appreciate your patience as we resolve this.

The VGS engineering team is continuing to investigate the log delivery delays on the VGS Dashboard. The team is actively troubleshooting the issue to resolve the latency and restore normal functionality as soon as possible. Thank you for your continued patience.

The VGS engineering team is continuing to investigate the log delivery delays on the VGS Dashboard. We appreciate your patience and will provide updates as our investigation progresses.

The log delivery delays on the VGS Dashboard have been mitigated. Logs are now flowing to the dashboard, and we are monitoring the service as it continues to stabilize. Thank you for your patience.