Resolved -
The incident is resolved.
May 14, 17:50 UTC
Monitoring -
We have a solution for this issue and a new deploy is required to enable it. If you are seeing function errors, please make a new deployment of your site.
May 14, 17:41 UTC
Identified -
We're seeing increased function invocation errors beginning at ~13:45 UTC. We've identified the likely cause and are implementing a fix.
May 14, 17:30 UTC
Resolved -
The incident is resolved.
May 9, 21:45 UTC
Monitoring -
We have applied a solution for the function invocation issue in the southeast-2 region and we are monitoring to confirm the resolution.
May 9, 21:33 UTC
Identified -
We have identified an issue starting at 20:38 UTC which is preventing invocations for functions deployed to the ap-southeast-2 region for the High-Performance Edge Network only. We are working on a solution now.
May 9, 21:12 UTC
Resolved -
This has been resolved.
May 7, 13:01 UTC
Update -
We are continuing to monitor for any further issues.
May 7, 12:24 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
May 7, 11:55 UTC
Investigating -
Starting 11:27 UTC our API started to experience high latency and elevated error rates. We are investigating the issue.
May 7, 11:49 UTC
Resolved -
This incident has been resolved.
May 6, 10:39 UTC
Monitoring -
We have identified the cause and implemented a fix. We will continue to actively monitor the results.
May 6, 10:08 UTC
Update -
We are continuing to investigate these function errors on our Standard Edge and High-Performance Edge network.
May 6, 09:48 UTC
Investigating -
We see an increased number of errors when running Functions on the Standard Edge network. High-Performance Edge is not affected. Our team is investigating
May 6, 09:22 UTC