Intercom - USLatency in the inbox for a subset of customers
A small subset of Intercom customers experienced degraded service including inconsistent latency and stale data when reading from the platform.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
A small subset of Intercom customers experienced degraded service including inconsistent latency and stale data when reading from the platform.
Resolved
Earlier today, some users may have encountered errors when creating Linear issues from Slack using the Linear or Linear Asks integration. The issue has been fully resolved, and all Slack-based issue creation is now operating normally. We apologize for any disruption this caused, and thank you for your patience.
Resolved
We continue to receive sporadic reports of outages at Microsoft, as well as delayed mail sending to Microsoft and their related properties. But have seen recovery for most senders. If you are experiencing delays or IP blocks in sending to Microsoft related properties, please open a ticket with your Technical Account Manager or email support@bird.com (or your dedicated support channel if applicable).
Resolved
This issue has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue with AI flows has been successfully resolved. Please refresh your browser to access the platform. Thank you for your patience
Resolved
We have been able to identify and fix the problem that was causing issues with generating link previews and editing media within Buffer. Thank you so much for your patience with us during this incident today and we hope everything in your Buffer account is working smoothly for you again now. If you do notice any lingering wonkiness with link previews or editing media at all, please do let us know.
Resolved
All impacted services have now fully recovered.
Resolved
Our third-party provider has successfully implemented a fix. We have verified that all affected services are now fully operational. We will continue to monitor the situation closely to ensure continued stability. Thank you for your patience.
Resolved
We fixed the degraded performance and all our systems are back online and functional.
Resolved
This incident has been resolved.
Resolved
After monitoring we are seeing authentication flows working as normal again, closing this incident.
Resolved
We're working on a long-term solution in the background
Resolved
This incident has been resolved.
Resolved
Incident: On 2026-01-22 the Asana App and all associated services had a service disruption due to dependency on a shared database used for storing metadata. This was triggered by a code path which caused overload for that database, followed by request queuing, timeouts, and errors. Impact: From 17:33 - 17:57 UTC the Asana App and all associated services were unavailable. There was a further 14 minutes of partial downtime from 18:45 - 18:59 UTC affecting 10-20% of users, also triggered by dependency on this shared database. Moving forward: We immediately rolled back our application code and added resources for this database. Going forward we will continue to reduce dependency on this shared database for common paths to reduce risk, and monitor for unexpected resource usage. Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.
Resolved
The issue with RAG indexing has been resolved.
Resolved
Between Jan 26, 4:53pm PST and Jan 26, 9:57pm PST, some database views appeared empty after sub-items were enabled, but this is now resolved!
Resolved
This maintenance has been completed successfully.
Resolved
A configuration change in our function runner service caused error rates to increase across all Convex deployments between 8:20pm PT and 8:35pm PT. This change has been rolled back, and all deployments should be operating normally.
Resolved
A configuration change in our function runner service caused error rates to increase across all Convex deployments between 8:20pm PT and 8:35pm PT. This change has been rolled back, and all deployments should be operating normally.
Resolved
Between January 24, 2026,19:56 UTC and January 25, 2026, 2:50 UTC repository creation and clone were degraded. On average, the error rate was 25% and peaked at 55% of requests for repository creation. This was due to increased latency on the repositories database impacting a read-after-write problem during repo creation. We mitigated the incident by stopping an operation that was generating load on the database to increase throughput. <br /><br />We have identified the repository creation problem and are working to address the issue and improve our observability to reduce our time to detection and mitigation of issues like this one in the future.<br />
Resolved
This incident has been resolved. Thank you for your patience.
Resolved
This incident has been resolved.
Resolved
We identified an issue where some destinations, for a subset of customers, in ReverseETL were not accurately reporting their delivery counts. We're currently backfilling the observability data, and all new runs for the affected ReverseETL should now display the correct counts.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
All services are working normally again, thanks for your patience.
Resolved
The issue has been resolved and systems have returned to normal.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved. Please follow up with the Lever Support team if you encounter continued disruptions when attempting Adobe Sign supported sendings.
Resolved
We have fixed the issue in authentication.
Resolved
All impacted services have now fully recovered.
Resolved
We have fixed the cause of the problem and queueing should now work as usual!
Resolved
A indisponibilidade no envio SMS do RD Station Marketing foi resolvida com sucesso. Caso você note que sua conta ainda contém alguma inconsistência, por favor, entre em contato com nosso Time de Suporte através da nossa Central de Ajuda "através da nossa Central de Ajuda": http://ajuda.rdstation.com/..
Resolved
On Jan 21st, 2025, between 11:15 UTC and 13:00 UTC the Copilot service was degraded for Grok Code Fast 1 model. On average, more than 90% of the requests to this model failed due to an issue with an upstream provider. No other models were impacted.<br /><br />The issue was resolved after the upstream provider fixed the problem that caused the disruption. GitHub will continue to enhance our monitoring and alerting systems to reduce the time it takes to detect and mitigate similar issues in the future.
Resolved
The issue has been identified and fixed.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved