Between 10:20 and 10:42 UTC we observed increased latency, overall slowness, and a degraded experience in the Inbox and Intercom REST API for users in the US region, caused by high internal database load.

All services have now been restored to normal functionality, and the team is implementing additional measures to prevent similar issues in the future.

Please don’t hesitate to reach out to team@intercom.io if you have any further questions or continue to experience unexpected behavior.

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 if you have any further questions or if you’re still seeing any unexpected behaviour

This incident fully resolved yesterday.

Slack recovered at 19:30 UTC and Phone recovered at 20:00 UTC.

Please don’t hesitate to reach out to team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour.

Today, Intercom services were impacted by a large event at our Cloud Provider. During the event, Intercom customers would have experienced varying types of degradation of services - increased error rates, high latency, and other third-party services, integrations and channels not working. During this event, our Engineering teams worked to rebalance our available compute capacity to keep core Intercom services online.

This incident is now resolved, and all services are now working as expected.

Fin over phone services have been fully restored and are operating normally.

Please don’t hesitate to reach out to team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour

Between 11:46 - 11:57 UTC the Inbox was down in the USA region. Fin and the Messenger were not affected.

The Inbox in the USA region is fully recovered. Apologies for the inconvenience.

Between 10:17 - 11:10 UTC today, quick replies in the Intercom messenger weren't working reliably. We rolled back a change that caused this issue. Apologies for the disruption.

Between approximately 13:49 and 16:16 UTC today, a small subset (< 1%) of customers experienced delays and inconsistent performance on Intercom due to a database shard issue. Our engineering team took action to reduce the load, and system performance has returned to normal - no further impact is expected.

As of approx 09:00 UTC today, restarting Safari 26 on MacOS / iOS fixes the issue of the messenger not working in incognito mode or when "Advanced Tracking and Fingerprinting Protection" is enabled. We are following-up with Apple.