Istoricul incidentelor Intercom

There are currently delays in sending and receiving messages to/from Meta properties (Facebook, Instagram, WhatsApp) due to issues on their side. We're monitoring the situation.

Meta services are back up and running, and we’ve caught up on queued messages.

We are investing a high rate of errors in the mobile SDK endpoints and mobile push functionality in the EU and Australian hosting regions.

For EU customers between 09:34 - 10:18UTC, and AU customers between 09:36 - 10:06UTC Mobile SDK endpoints and mobile push were impaired. This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to [[email protected]](mailto:[email protected]) if you have any further questions or if you’re still seeing any unexpected behaviour

Earlier today at 10:10 UTC many teammates were forced to logout and log back into Intercom. In a small number of cases, server side rate limiting impaired logging back in, causing login loops. We've resolved this issue as of 13:00 UTC. Apologies for any disruption.

Open browser tabs with old logins to the Intercom app may be causing ongoing login/logout churn - closing old tabs or restarting web browser will prevent this from happening.

**Resolved** We're closing this incident. On April 30, 2026 an attacker published malicious versions of intercom-client (v7.0.4) and intercom-php (v5.0.2). Both were removed from distribution within hours of discovery. No evidence of unauthorized access to customer data or Intercom accounts was found. If you installed [email protected] or [email protected] on April 30 and haven't already done so, we recommend rotating any credentials configured in that environment. All other versions of both packages are safe. We kept the incident open out of an abundance of caution while we completed credential rotation, hardened our infrastructure, and monitored closely for any follow-on activity. We're now satisfied it's fully remediated.