DiscordApplications experiencing 503 errors
We believe that the 503s have been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
We believe that the 503s have been resolved.
Resolved
Our team has been monitoring and job processing has returned to normal. This incident is now resolved. Further details available in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21532
Resolved
This issue is now resolved.
Resolved
Incident was resolved. Thank you for your patience. Board functionality is back to normal.
Resolved
Incident was resolved. Thank you for your patience. Board functionality is back to normal.
Resolved
From 12:04 to 12:09 PDT, most docs sites experienced either a partial or total outage when attempting to view pages. We caught the issue internally immediately, and were able to roll back code for all affected sites within minutes. This was caused by incorrect debug code pushed by one of our developers. No further action is required on our customers' part to resolve the issue.
Resolved
We had a backlog in our notifications queue that prevented timely delivery of alerts to channels such as Email, Slack, etc. The backlog has been processed as of 19:20 UTC. Our autoscaling rules for this service had a monitoring gap that prevented a scale-out to maintain a low latency on the queue. This monitoring gap has been resolved.
Resolved
The fix has been deployed and we have not seen any more errors. This incident is now resolved.
Resolved
All SSO login/sign-up issues and Udemy Business MCP authentication issues have been resolved. Both standard SSO access and MCP-based AI tool integrations are now working normally.
Resolved
This incident has been resolved.
Resolved
This issue is fully resolved.
Resolved
Our engineers have found the issue causing Closed Conversations not to display in the Closed Folder, and this has now been resolved, You should now find all of those Conversations in the Closed Folder as normal. Thanks for your patience while we worked on getting this one fixed up!
Resolved
This incident has been resolved.
Resolved
Users were unable to retrieve documents across multiple platforms. This included degraded performance or failures when attempting to access documents via the CLI as well as through other interfaces.
Resolved
On March 6, 2026, between 16:16 UTC and 23:28 UTC the Webhooks service was degraded and some users experienced intermittent errors when accessing webhook delivery histories, retrying webhook deliveries, and listing webhooks via the UI and API. On average, the error rate was 0.57% and peaked at approximately 2.73% of requests to the service. This was due to unhealthy infrastructure affecting a portion of webhook API traffic.<br /><br />We mitigated the incident by redeploying affected services, after which service health returned to normal.<br /><br />We are working to improve detection of unhealthy infrastructure and strengthen service safeguards to reduce time to detection and mitigation of issues like this one in the future.
Resolved
This issue is now resolved.
Resolved
The situation has now stabilized. We are closing this incident.
Resolved
This incident has been resolved
Resolved
This incident has been resolved.
Resolved
The issue affecting Supabase Log ingestion has been fully resolved. Log ingestion across all services has returned to normal operation.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The background refresh has now completed and pull request review statuses should be displaying correctly again. If you happen to see a PR with an outdated status, navigating to the individual PR in Linear should trigger an immediate refresh. Thanks for your patience while we worked through this.
Resolved
The system returned to a fully stable state.
Resolved
We are seeing significantly fewer reports related to domain mapping and expect the DNS propagation process to complete in the coming hours. We are marking this incident as resolved. If you have any questions or need assistance, our team is available to help.
Resolved
We have successfully mitigated the incident, and the affected service is now fully operational. Our teams have verified that normal functionality has been restored and the service is performing as expected.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The recent issue impacting MediaFlows, where some event-based triggers did not execute as expected, has been resolved. All services are now operating normally.
Resolved
The issue has been resolved.
Resolved
We've mitigated the impact and event processing delays are below 60 seconds and falling continuously.
Resolved
This incident is now mitigated. Thank you for your patience and understanding.
Resolved
We scaled our systems and resolved the issue.
Resolved
We have resolved the issue.
Resolved
We have resolved the issue with the Course completion feature on our site, but some users who watched the full course content during the incident may still see the lectures not being marked as completed. We appreciate your patience. [Action needed] Udemy is working to fix this issue automatically as part of the cleanup tasks from this incident, but it may take more time. If you urgently need this to be resolved, please contact support who can support you further.
Resolved
The issue resolved once the AWS issues resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
All impacted services have now fully recovered.
Resolved