Very Good Security experienced a minor incident on August 24, 2026 affecting Platform Insights and Echo Server (Echo Server — Live US) and 1 more component, lasting 21h 49m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Aug 24, 2026, 10:03 AM UTC
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. 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, 10:03 AM UTC
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.
- identified Aug 24, 2026, 11:37 AM UTC
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.
- identified Aug 24, 2026, 11:37 AM UTC
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.
- identified Aug 24, 2026, 01:44 PM UTC
Our engineers continue working on the additional development work to resolve this issue. We will provide the next update within the next 60 minutes.
- identified Aug 24, 2026, 01:44 PM UTC
Our engineers continue working on the additional development work to resolve this issue. We will provide the next update within the next 60 minutes.
- monitoring Aug 24, 2026, 03:02 PM UTC
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.
- monitoring Aug 24, 2026, 03:02 PM UTC
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.
- monitoring Aug 24, 2026, 04:27 PM UTC
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.
- monitoring Aug 24, 2026, 04:27 PM UTC
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.
- monitoring Aug 24, 2026, 06:58 PM UTC
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.
- monitoring Aug 24, 2026, 06:58 PM UTC
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.
- monitoring Aug 24, 2026, 09:40 PM UTC
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
- monitoring Aug 24, 2026, 09:40 PM UTC
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
- monitoring Aug 24, 2026, 11:33 PM UTC
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.
- monitoring Aug 24, 2026, 11:33 PM UTC
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.
- monitoring Aug 25, 2026, 02:24 AM UTC
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.
- monitoring Aug 25, 2026, 02:24 AM UTC
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.
- monitoring Aug 25, 2026, 05:34 AM UTC
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.
- monitoring Aug 25, 2026, 05:34 AM UTC
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.
- resolved Aug 25, 2026, 07:53 AM UTC
After close monitoring, we have confirmed that the event backlog has been cleared and webhook delivery is operating as expected.