HTTP Proxy Access Logs Unavailable in VGS Dashboard

Update timeline

1. investigating Sep 18, 2026, 04:15 PM UTC

   HTTP Proxy access logs are currently unavailable for viewing within the VGS dashboard. There is no impact on any traffic flow. Our team is working to restore log visibility as quickly as possible. 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

2. investigating Sep 18, 2026, 04:15 PM UTC

   HTTP Proxy access logs are currently unavailable for viewing within the VGS dashboard. There is no impact on any traffic flow. Our team is working to restore log visibility as quickly as possible.

3. identified Sep 18, 2026, 04:37 PM UTC

   We have identified the root cause of the audit log issue as a recent deployment change to one of our backend services. Our team has initiated a rollback to the previous stable version, which is expected to be completed within 40–45 minutes. This issue is primarily affecting audit logs of high-traffic customers across multiple regions. There is no impact on traffic processing; only audit log visibility is affected. We will continue monitoring the rollback and will provide another update once it is complete.

4. identified Sep 18, 2026, 04:37 PM UTC

   We have identified the root cause of the audit log issue as a recent deployment change to one of our backend services. Our team has initiated a rollback to the previous stable version, which is expected to be completed within 40–45 minutes. This issue is primarily affecting audit logs of high-traffic customers across multiple regions. There is no impact on traffic processing; only audit log visibility is affected. We will continue monitoring the rollback and will provide another update once it is complete.

5. identified Sep 18, 2026, 05:26 PM UTC

   The rollback to the previous stable version is currently in progress. We are actively monitoring the process and validating that audit log visibility returns to normal once complete. This issue continues to primarily affect audit log visibility for high-traffic customers across multiple regions. There is no impact on transaction or traffic processing. We will provide our next update within 45 minutes, or sooner once the rollback has completed.

6. identified Sep 18, 2026, 05:26 PM UTC

   The rollback to the previous stable version is currently in progress. We are actively monitoring the process and validating that audit log visibility returns to normal once complete. This issue continues to primarily affect audit log visibility for high-traffic customers across multiple regions. There is no impact on transaction or traffic processing. We will provide our next update within 45 minutes, or sooner once the rollback has completed.

7. identified Sep 18, 2026, 06:24 PM UTC

   The rollback remains in progress. Our team is continuing to work through the remaining steps and will confirm that audit log visibility is fully restored once complete. This issue primarily affects audit log visibility for high-traffic customers across multiple regions. There is no impact on transaction or traffic processing. We will provide our next update within 45 minutes, or sooner if the rollback completes ahead of schedule.

8. identified Sep 18, 2026, 06:24 PM UTC

   The rollback remains in progress. Our team is continuing to work through the remaining steps and will confirm that audit log visibility is fully restored once complete. This issue primarily affects audit log visibility for high-traffic customers across multiple regions. There is no impact on transaction or traffic processing. We will provide our next update within 45 minutes, or sooner if the rollback completes ahead of schedule.

9. resolved Sep 18, 2026, 09:46 PM UTC

   We have completed the rollback to the previous stable version and have monitored the system following the rollback. Based on current observations, we are seeing minimal recurrence of the reported issue. If you continue to experience an issue viewing HTTP Proxy access logs in the VGS Dashboard, please reach out to our support team at [email protected] and we will assist you directly. We are resolving this incident and will follow up with a longer-term fix that will allow us to complete the underlying upgrade without impacting access log visibility.