Previous incidents

We have applied manual patches to resolve the current issue and are implementing additional patches to ensure system stability. We will continue investigating a long-term solution under the updated configuration to ensure auto-scaling operates as expected. All services are now fully functional.

We have updated the service configuration, and the impact appears to be positive. Error rates have returned to normal levels, and services are now fully available with normal response times. We will continue to monitor the system and investigate the root cause.

The team has applied a fix, the service is recovering. We'll keep monitoring.

We have confirmed the issue is now resolved with multiple customers. If anyone is still facing issues we'd recommend to create a new user session. We will share a full incident report once our internal investigation will complete.

The issues causing runtime failure for both sites and function has been resolved.

Realtime appears to be running normally, but we'll continue to monitor.

All services are now available. Our team will continue investigating the root cause of the issue.

We have migrated to a fallback provider, and service is now fully restored. We will continue to monitor the situation closely and work with our vendors to help prevent similar incidents in the future.

Services have restored. Thanks for your patience

Services are available again.

Realtime should be functioning again. Thank you for your patience.

We expect API error rates to return to normal. The system is being actively monitored, and any new issues will be investigated immediately.

Our engineering team has identified the root cause of the incident and is implementing a series of remediation measures to prevent recurrence. All services are fully operational and performing within normal parameters.

Emails to Microsoft email domains appear to be functioning again.

The issue has been identified and resolved.

We will be publishing a detailed incident report outlining our findings and the corrective actions we are implementing to help ensure this does not happen again.

Functions should be restored. Thank you for your patience.

Execution logs have been re-enabled for all projects.

We've fixed the issue with function and site deployments in the Console.

Issues with NYC have been resolved. Function execution logs have been disabled to mitigate further issues. We're working on restoring functionality and will be tracking in a separate incident.

Our team have applied a patch, the issue seems to be resolved. We will continue to monitor and look for the root cause.

We have resolved the root cause of the issue and service has returned to normal.