Fasterize incident

Errors 502 from the platform

Minor Resolved View vendor source →

Fasterize experienced a minor incident on September 29, 2022 affecting Acceleration, lasting 24d 23h. The incident has been resolved; the full update timeline is below.

Started
Sep 29, 2022, 08:44 AM UTC
Resolved
Oct 24, 2022, 08:39 AM UTC
Duration
24d 23h
Detected by Pingoru
Sep 29, 2022, 08:44 AM UTC

Affected components

Acceleration

Update timeline

  1. identified Sep 29, 2022, 08:44 AM UTC

    We are currently experiencing a platform issue. We noticed an increase in the number of TCP Resets since ~10 days on our load balancer. This issue has generated an increase of the level of 502 errors. Within the last hours, it represents 0.03% of the total number of requests. Our technical team is massively working to resolve this critical issue and will update the status of the debugging steps until full resolution.

  2. identified Sep 29, 2022, 08:53 AM UTC

    We are continuing to work on a fix for this issue.

  3. identified Sep 29, 2022, 02:18 PM UTC

    A workaround is being deployed. However, while we have identified the cause of the 502 increase, we have yet to determine the root cause. We're actively investigating this topic.

  4. monitoring Sep 30, 2022, 02:49 PM UTC

    The fix has been deployed. We have identified the source of the problem, which is an external integration provided by a partner. We will work with our partner to update/fix the offending module.

  5. resolved Oct 24, 2022, 08:39 AM UTC

    This incident has been now resolved by progressively deploying the updated module and monitoring the results in the last few days. Reminder: before that, a workaround was deployed to mitigate errors.