A fix has been implemented and we are monitoring the results.
Posted Apr 19, 2024 - 19:26 UTC
Identified
We have identified the issue to be isolated to the iad1 (Washington DC, USA) region and have temporarily redirected Edge Function and Middleware traffic to other regions. Serverless Functions are not affected and will continue to run as normal.
Posted Apr 19, 2024 - 18:09 UTC
Update
We’re currently investigating an elevated rate of 500 errors originating from our iad (Washington DC, USA) edge node. Customers may see INTERNAL_EDGE_FUNCTION_INVOCATION_FAILED as a result. The issue happened intermittently beginning on April 18, 2024: April 18, 2024 21:27-21:28 UTC April 19, 2024 00:36-00:37 UTC April 19, 2024 06:54-06:55 UTC April 19, 2024 10:12-10:13 UTC April 19, 2024 13:45-13:46 UTC April 19, 2024 16:58-16:59 UTC
Posted Apr 19, 2024 - 17:52 UTC
Investigating
We’re currently investigating an elevated rate of 500 errors originating from our iad (Washington DC, USA) edge node. Customers may see INTERNAL_EDGE_FUNCTION_INVOCATION_FAILED as a result. The issue happened intermittently beginning on April 18, 2024: April 18, 2024 21:27-21:28 UTC April 19, 2024 00:36-00:37 UTC April 19, 2024 06:54-06:55 UTC April 19, 2024 10:12-10:13 UTC April 19, 2024 13:45-13:46 UTC April 19, 2024 16:58-16:59 UTC
Posted Apr 19, 2024 - 17:47 UTC
This incident affected: Edge Functions, Edge Middleware and Edge Network (IAD1 - Washington DC, USA).