Degraded Functions Service

Our Engineering team has confirmed that the issue impacting our Functions service has been fully resolved. If you continue to experience any issues in relation to this incident please open a ticket with our support team. Thank you for your patience.

Functions in BLR1 region are now restored to normal service. As of 17:00 UTC, all impact has been mitigated and users should no longer experience any issues with the Functions. We are monitoring the situation and will post an update once the incident is completely resolved.

Thank you for your patience and we apologize for the inconvenience.

Functions in FRA1 and LON1 are now restored to normal service. We continue work to remediate BLR1.

Our Engineering team has discovered that some Function invocations were duplicated, so a subset of users may have experienced that during the course of this incident.

We will post an update once the last region has returned to normal service.

Our Engineering team has been working in order to restore the Functions service. At this time, normal service has been restored in most of the regions including AMS3, SGP1, TOR1, and SYD1.

We’re now working to fully remediate the remaining regions: BLR1, FRA1, and LON1. We will post an update as soon as that has completed. Thank you for your patience!

Beginning 14:37 UTC, our Engineering team has identified an issue impacting Functions in AMS3, BLR1, FRA1, LON1, SGP1, SYD1, and TOR1. During this time, users with standalone Functions or Functions deployed through Apps may experience performance degradation, leading to delays in Functions invocations and/or Functions working more slowly than normal.

Our team is working to mitigate the issue and we will provide an update as soon as possible.