Very Good Security incident

HTTP Proxy Performance Degradation

Minor Resolved View vendor source →

Very Good Security experienced a minor incident on May 17, 2026 affecting HTTP Proxy and Echo Server (Live US), lasting 2h 30m. The incident has been resolved; the full update timeline is below.

Started
May 17, 2026, 09:32 AM UTC
Resolved
May 17, 2026, 12:03 PM UTC
Duration
2h 30m
Detected by Pingoru
May 17, 2026, 09:32 AM UTC

Affected components

HTTP ProxyEcho Server (Live US)

Update timeline

  1. investigating May 17, 2026, 09:32 AM UTC

    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

  2. investigating May 17, 2026, 09:32 AM UTC

    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.

  3. investigating May 17, 2026, 10:19 AM UTC

    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.

  4. investigating May 17, 2026, 10:19 AM UTC

    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.

  5. monitoring May 17, 2026, 11:08 AM UTC

    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.

  6. monitoring May 17, 2026, 11:08 AM UTC

    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.

  7. resolved May 17, 2026, 12:03 PM UTC

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