WildFire Issue

Final update

This incident has been resolved.

1. Resolved · Jun 2, 22:55 UTC
   This incident has been resolved.
2. Monitoring · Jun 2, 22:14 UTC
   A fix has been implemented and we are monitoring the results.
3. Identified · Jun 2, 21:56 UTC
   The issue has been identified and a fix is being implemented.
4. Investigating · Jun 2, 21:13 UTC
   We are continuing to investigate this issue.
5. Investigating · Jun 2, 19:23 UTC
   We are continuing to investigate this issue.
6. Investigating · Jun 2, 15:35 UTC
   Wildfire is experiencing 8X more traffic than the normal traffic. The source of this traffic is not yet identified. We are actively working on the issue.
7. Investigating · Jun 2, 15:28 UTC
   We are currently investigating this issue.
8. Identified · Jun 2, 07:21 UTC
   Root cause identified. The fix to be ready in a couple of hours and deployment to happen later today.
9. Investigating · Jun 2, 06:29 UTC
   WF is getting unexpected traffic from yesterday for which Wildfire services are not ready to handle. Wildfire has autoscaling settings. However, traffic is more than 8X of normal traffic. The max resources allocated can not handle these traffic.
10. Investigating · Jun 1, 13:46 UTC
    WildFire is currently experiencing an issue in US Cloud. We are actively working on this issue and will provide another update by 14:00 with further details. Customer Impact: Error while getting verdict Workaround: N/A