LinearProblems with events and processors (US East)
The issue affecting events and processors in the US East region has been resolved. Some events may take a short time to fully catch up, and actions may remain briefly delayed.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
The issue affecting events and processors in the US East region has been resolved. Some events may take a short time to fully catch up, and actions may remain briefly delayed.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour
Resolved
This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour
Resolved
This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour
Resolved
🎉 The issue has been resolved and we are back to normal.
Resolved
This incident is now resolved. Thank you for your patience and understanding.
Resolved
All impacted services have now fully recovered.
Resolved
We are able to confirm that the issues with publishing content to Facebook Pages has been resolved. Thank you for your patience
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Between approximately 9:42 AM and 10:38 AM ET on April 10, we observed delivery failures for customers in the US1, AP1, and AP2 regions. During this window, notifications to the following integrations were delayed or temporarily undelivered: • PagerDuty • Slack • Microsoft Teams • Webhooks • Jira • ServiceNow • OpsGenie • VictorOps • BigPanda • Zendesk • Sumologic All delayed notifications have been replayed with the following exceptions: PagerDuty pages and Slack notifications queued during the outage window were not replayed, as they were no longer actionable at the time of recovery. Webhook notifications will be reprocessed and delivered at a later date. No monitoring data was lost during this incident. Monitor evaluations continued normally — only the delivery of triggered notifications was affected. Thank you for your patience.
Resolved
We have successfully deployed a fix for the PrivateLink hostname issue to the User Console. Customers who experienced incorrect PrivateLink URLs or connectivity issues with their deployments should now see correct hostnames. We apologize for the inconvenience.
Resolved
Between 08:00 UTC and 09:24 UTC April 10, 2026, customers may have experienced failures or delays in database connectivity. This incident is now resolved, and we apologize for any inconvenience. No further updates are planned.
Resolved
This issue is now resolved.
Resolved
All activity log data is now live and up to date.
Resolved
On April 1st, 2026 between 14:40 and 17:00 UTC the GitHub code search service had an outage which resulted in users being unable to perform searches.<br /><br />The issue was initially caused by an upgrade to the code search Kafka cluster ZooKeeper instances which caused a loss of quorum. This resulted in application-level data inconsistencies which required the index to be reset to a point in time before the loss of quorum occurred. Meanwhile, an accidental deploy resulted in query services losing their shard-to-host mappings, which are typically propagated by Kafka.<br /><br />We remediated the problem by performing rolling restarts in the Kafka cluster, allowing quorum to be reestablished. From there we were able to reset our index to a point in time before the inconsistencies occurred.<br /><br />The team is working on ways to improve our time to respond and mitigate issues relating to Kafka in the future.
Resolved
We have resolved the issue.
Resolved
We've fixed the issue and will be monitoring the situation.
Resolved
This issue has been fully resolved, and all services are operating normally. We have continued to monitor the environment and have not observed any further issues. Customer websites and services remain fully operational, and support response times have returned to normal. If you experience any issues or need assistance, please reach out via Live Chat or by submitting a support case. We appreciate your patience throughout this incident.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We can confirm that the fix was applied uniformly to all impacted and potentially impacted environments; no teams should see ingest errors related to this issue anymore.
Resolved
On April 2, 2026 between 8:19 PM PDT and 11:56 PM PDT, some users may have experienced difficulties while working in Box. During this time, Box Sign users might have experienced errors while creating new signature requests, accessing existing signature requests, or attempting ~~been unable~~ to access the service. The issue occurred as a result of an erroneous change made by a third-party infrastructure provider. We were able to resolve the issue by escalating it to the provider. In addition, we are working to improve the reliability of the Box Sign service by enhancing our disaster recovery processes to prevent similar issues from occurring in the future. We are conducting a full engineering postmortem and our overview is subject to change with further analysis and findings. In the event our continuing investigation yields further substantive findings, we may publish additional analysis after the conclusion of the full engineering postmortem. We are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter. Sincerely, The Box Team
Resolved
This incident is now resolved
Resolved
This incident has been resolved.
Resolved
The issue has been resolved Services have returned to normal. You can stay up to date on the status of our services anytime here on our status page: https://status.sumup.com.
Resolved
The maintenance has been completed successfully.
Resolved
We have concluded our monitoring period and observed no further issues. All systems are operating normally. Thank you for your continued patience.
Resolved
We have confirmed no further impact from this incident, and are now marking it as resolved.
Resolved
All impacted services have now fully recovered.
Resolved
All impacted services have now fully recovered.
Resolved
The issue with image cropping have been fully resolved, and it’s functioning as expected again. If you encounter any further problems, please don’t hesitate to reach out to our team.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue affecting async transcription processing has been fully resolved. All systems are operating normally. We apologize for the disruption to your workflows. If you have any questions, please reach out to support@assemblyai.com.
Resolved
This incident has been resolved.
Resolved
All connections to the Slack app have been restored. However, if you are still running into issues, we recommend reconnecting the app.
Resolved