Intercom Outage History

Started Oct 30, 2026, 06:06 PM UTC· resolved Oct 30, 2026, 06:30 PM UTC

1. investigating Oct 30, 2026, 06:06 PM UTC

   We're investigating slowness with Fin Procedures.

2. monitoring Oct 30, 2026, 06:22 PM UTC

   Fin Procedures is now working as normal.

3. resolved Oct 30, 2026, 06:30 PM UTC

   Fin Procedures is back to normal.

Read the full incident report →

Started Oct 14, 2026, 05:43 PM UTC· resolved Oct 14, 2026, 05:55 PM UTC

1. investigating Oct 14, 2026, 05:43 PM UTC

   We're investigating reports of customer contact details showing up as "Redacted" in the Intercom helpdesk.

2. resolved Oct 14, 2026, 05:55 PM UTC

   Between 16:50 UTC and 17:39 UTC contact details were replaced with "Redacted" in the Intercom Helpdesk for teammates missing explicit permissions to view contact details. We're sorry for the disruption.

Read the full incident report →

Started Sep 16, 2026, 11:51 AM UTC· resolved Sep 16, 2026, 05:19 PM UTC

1. monitoring Sep 16, 2026, 11:51 AM UTC

   Fin for Salesforce customers may experience issues due to an upstream error. We have confirmation a fix is being worked on and will update here as soon as we know more.

2. resolved Sep 16, 2026, 05:19 PM UTC

   All services are presumed to be restored to normal operations. For more information please refer to this status page.: https://status.salesforce.com/incidents/20004433

Read the full incident report →

Started Sep 09, 2026, 03:55 PM UTC· resolved Sep 09, 2026, 04:04 PM UTC

1. investigating Sep 09, 2026, 03:55 PM UTC

   We're seeing issues with Intercom Messenger where Help Articles are not displaying. Our team is aware and investigating the issue. We’ll update you here as soon as we have more specific information.

2. resolved Sep 09, 2026, 04:05 PM UTC

   This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@fin.: mailto:[email protected] if you have any further questions or if you’re still seeing any unexpected behaviour

Read the full incident report →

Started Sep 04, 2026, 10:00 AM UTC· resolved Sep 04, 2026, 03:45 PM UTC

1. investigating Sep 04, 2026, 03:16 PM UTC

   We're seeing issues with Fin Agent responding to the first message of new inbound Conversations. Our team is aware and investigating the issue. We’ll update you here as soon as we have more specific information.

2. monitoring Sep 04, 2026, 03:47 PM UTC

   We have implemented a fix and are monitoring for recovery. We’ll let you know when we are confident in our recovery.

3. resolved Sep 04, 2026, 03:55 PM UTC

   This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@fin.: mailto:[email protected] if you have any further questions or if you’re still seeing any unexpected behaviour

Read the full incident report →

Started Sep 03, 2026, 02:13 PM UTC· resolved Sep 03, 2026, 02:36 PM UTC

1. investigating Sep 03, 2026, 02:29 PM UTC

   We're seeing issues with Fin in Australia. Our team is aware and investigating the issue. We’ll update you here as soon as we have more specific information.

2. monitoring Sep 03, 2026, 02:38 PM UTC

   We have implemented a fix and are monitoring for recovery. We’ll let you know when we are confident in our recovery.

3. resolved Sep 03, 2026, 02:41 PM UTC

   This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@fin.: mailto:[email protected] if you have any further questions or if you’re still seeing any unexpected behaviour

Read the full incident report →

Started Aug 26, 2026, 02:15 PM UTC· resolved Aug 26, 2026, 02:41 PM UTC

1. investigating Aug 26, 2026, 02:26 PM UTC

   We're investigating Fin not answering conversations in the USA hosting region.

2. identified Aug 26, 2026, 02:39 PM UTC

   We're seeing partial recovery for Fin answering questions.

3. resolved Aug 26, 2026, 02:49 PM UTC

   Between 14:15 - 14:41 UTC Fin was slow to respond to conversations. We have identified the cause and do not expect recurrence. Apologies for the disruption. There are more details available in the attached root cause analysis document.

Read the full incident report →

Started Aug 19, 2026, 10:30 AM UTC· resolved Aug 19, 2026, 11:35 PM UTC

1. investigating Aug 19, 2026, 11:12 PM UTC

   We're seeing issues with our Shopify integration. Our team is aware and investigating the issue. We’ll update you here as soon as we have more specific information.

2. monitoring Aug 19, 2026, 11:40 PM UTC

   We have implemented a fix and are monitoring. We’ll let you know when we are confident in our recovery.

3. resolved Aug 19, 2026, 11:45 PM UTC

   This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@fin.: mailto:[email protected] if you have any further questions or if you’re still seeing any unexpected behaviour.

Read the full incident report →

Started Aug 03, 2026, 02:22 PM UTC· resolved Aug 03, 2026, 08:03 PM UTC

1. investigating Aug 03, 2026, 02:22 PM UTC

   We're seeing issues with Intercom. Our team is aware and investigating the issue. We’ll update you here as soon as we have more specific information.

2. investigating Aug 03, 2026, 03:17 PM UTC

   We believe we have identified the root cause and are currently working through mitigation steps. Please be assured that we are still working to mitigate this issue and will update here as soon as we have more information.

3. monitoring Aug 03, 2026, 04:18 PM UTC

   We have implemented a fix and are monitoring for recovery. We’ll let you know when we are confident in our recovery.

4. resolved Aug 03, 2026, 08:03 PM UTC

   Between 13:35 UTC and 15:53 UTC customers experienced degraded search performance in the Inbox. Intermittently during the initial period of the investigation, some customers experienced conversations that failed to load in the Inbox. This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to [email protected] if you have any further questions or if you’re still seeing any unexpected behaviour

Read the full incident report →

Started Jul 15, 2026, 03:21 PM UTC· resolved Jul 15, 2026, 03:45 PM UTC

1. identified Jul 15, 2026, 03:21 PM UTC

   We're investigating Fin being slower than usual to answer questions, in the USA hosting region.

2. resolved Jul 15, 2026, 03:45 PM UTC

   Fin is back to normal. Between 14:45 - 15:30 UTC, Fin was slower than usual in the US hosting region.

Read the full incident report →

Started Jun 12, 2026, 07:13 PM UTC· resolved Jun 12, 2026, 07:13 PM UTC

1. identified Jun 12, 2026, 02:30 PM UTC

   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.

2. resolved Jun 12, 2026, 07:13 PM UTC

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

Read the full incident report →

Started Jun 11, 2026, 10:33 AM UTC· resolved Jun 11, 2026, 10:33 AM UTC

1. identified Jun 11, 2026, 09:54 AM UTC

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

2. resolved Jun 11, 2026, 10:33 AM UTC

   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

Read the full incident report →

Started Jun 10, 2026, 04:15 PM UTC· resolved Jun 10, 2026, 04:15 PM UTC

1. monitoring Jun 10, 2026, 01:19 PM UTC

   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.

2. resolved Jun 10, 2026, 04:15 PM UTC

   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.

Read the full incident report →

Started Jun 08, 2026, 11:53 AM UTC· resolved Jun 08, 2026, 11:53 AM UTC

1. investigating Apr 30, 2026, 04:58 PM UTC

   We are investigating reports that a malicious version (7.0.4) of the intercom-client npm package was briefly published earlier today. The latest legitimate version is 7.0.3. The impact is contained to the node SDK which is used to access Intercom APIs. If you installed [email protected], we recommend: • removing the package immediately • rotating any credentials (API keys, tokens, cloud credentials) that were accessible from that environment We are actively investigating and will share more information as it becomes available.

2. investigating Apr 30, 2026, 11:00 PM UTC

   We are continuing to investigate the malicious version of the intercom-client package. We have now confirmed that [email protected] was also compromised, between 20:53 UTC and 22:37 UTC on 2026-04-30. A safe version of v5.0.2 has since been restored. If you installed or updated intercom-php during this window, we recommend you: • Uninstall and reinstall the package from a clean source • Rotate any credentials (API keys, tokens, cloud credentials) that were accessible from the affected environment We will share further details as they become available.

3. monitoring May 01, 2026, 12:26 AM UTC

   We are continuing to investigate the malicious version of the intercom-client package. We have now confirmed that [email protected] was also compromised, between 20:53 UTC and 22:37 UTC on 2026-04-30. A safe version of v5.0.2 has since been restored. If you installed or updated intercom-php during this window, we recommend you: • Uninstall and reinstall the package from a clean source • Rotate any credentials (API keys, tokens, cloud credentials) that were accessible from the affected environment We will share further details as they become available.

4. monitoring May 01, 2026, 09:55 AM UTC

   Both malicious package versions ([email protected] and [email protected]) have been removed and are no longer available for download. Safe versions have been restored. GitHub Security Advisories have been published for both packages, enabling automated alerts via Dependabot and npm audit. • https://github.com/intercom/intercom-node/security/advisories/GHSA-54pg-9963-v8vg • https://github.com/intercom/intercom-php/security/advisories/GHSA-gr3r-crp5-qrrm We have been working with Wiz and Socket.dev directly to understand and mitigate impact from this event. As a precaution, we are rotating all credentials across all affected systems. We have found no evidence of unauthorized access to customer data or accounts. The impact has been limited to developer tooling. We will continue with remediation and share another update when we can.

5. monitoring May 01, 2026, 11:51 AM UTC

   As part of our investigation, we identified that the Apple Distribution Certificate used to sign our iOS SDK was potentially exposed. We have found no evidence that this certificate has been misused, but as a precaution we have revoked the certificate. This only affects developers who build apps that include the Intercom iOS SDK. It does not affect Intercom customers who use the Intercom product (Messenger, inbox, help center, etc.) or their end users. Apps already on the App Store are not affected. Specifically, this affects versions 19.5.6 and 19.5.7 of the following packages: - intercom-ios (https://github.com/intercom/intercom-ios) - intercom-ios-sp (https://github.com/intercom/intercom-ios-sp) If you are using either of these versions, your builds will fail until you update to a newly signed version. Instructions for resolving this will be available shortly. This change relates only to iOS integrations and do not affect the Intercom Android SDK, or the web Messenger.

6. monitoring May 01, 2026, 01:24 PM UTC

   The iOS Distribution Certificate has been revoked and all impacted releases have been re-signed with a new certificate. If your builds are failing, follow the instructions here: https://github.com/intercom/intercom-ios/wiki/Codesigning-Issue to update. This only affects developers who build apps that include the Intercom iOS SDK versions 19.5.6 and 19.5.7. It does not affect Intercom customers who use the Intercom product, their end users, or apps already on the App Store. These changes relate only to iOS integrations and do not affect the Android SDK or web Messenger.

7. monitoring May 04, 2026, 11:06 AM UTC

   Investigation and remediation continue Since our last update: • Credential rotation across affected systems is nearing completion • We have engaged independent external security partners to conduct a full assessment • Additional protections against malicious packages have been deployed alongside our existing security tooling • We continue to find no evidence of unauthorized access to customer data or Intercom accounts The compromised package versions ([email protected] and [email protected]) have been removed. Safe versions are available: [email protected] and [email protected]. GitHub Security Advisories with full technical details: - intercom-client: GHSA-54pg-9963-v8vg: https://github.com/intercom/intercom-node/security/advisories/GHSA-54pg-9963-v8vg - intercom-php: GHSA-gr3r-crp5-qrrm: https://github.com/intercom/intercom-php/security/advisories/GHSA-gr3r-crp5-qrrm We will continue to provide updates here as our investigation progresses.

8. monitoring May 06, 2026, 09:01 AM UTC

   Update: Continuing investigation Our investigation continues with support from independent external security partners. We continue to find no evidence of unauthorised access to customer data or Intercom accounts. All Intercom services remain fully operational. You are only potentially affected if your developers installed [email protected] (npm) or [email protected] during the affected window on April 30. The compromised package versions ([email protected] and [email protected]) remain removed. Safe versions: [email protected] and [email protected]. If you do not use these developer packages to interact with the Intercom REST API, you are not impacted. We are keeping this incident open while we complete our remediation and investigation. We will update this page when we are ready to close it out.

9. monitoring May 18, 2026, 12:39 PM UTC

   Update: Investigation continues - no change to impact Our investigation with independent external security partners continues. There is no evidence of unauthorized access to customer data or Intercom accounts. All Intercom services remain fully operational. The only impact has been to the compromised packages reported previously. The compromised versions ([email protected] and [email protected]) were removed and safe versions remain available. Since our last update, we have completed credential rotation and continued hardening our development environment with additional security controls. We will post a final update when we are ready to close this incident.

10. resolved Jun 08, 2026, 11:53 AM UTC

    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.

Read the full incident report →

Started Jun 01, 2026, 01:23 PM UTC· resolved Jun 01, 2026, 01:23 PM UTC

1. investigating Jun 01, 2026, 11:03 AM UTC

   We are currently investigating an issue affecting Fin replies for some customers. Our team is actively working to identify the root cause and mitigate the impact. We will provide updates here as soon as more information becomes available.

2. identified Jun 01, 2026, 11:31 AM UTC

   We have identified the root cause of the issue and are implementing a fix. We’ll update you here once we’ve confirmed our fix has been effective.

3. monitoring Jun 01, 2026, 11:58 AM UTC

   We have implemented a fix and are seeing signs of recovery for some affected customers. We are continuing to monitor the situation closely and will provide another update once we are confident that the full recovery is complete.

4. monitoring Jun 01, 2026, 12:43 PM UTC

   We are seeing signs of recovery for more affected customers and are continuing to monitor the situation closely. We will provide another update once we are confident that full recovery is complete.

5. resolved Jun 01, 2026, 01:23 PM UTC

   On June 1, 2026, between approximately 11:08 UTC and 13:24 UTC, a small subset of customers experienced degraded performance across Fin and Inbox. During this period, affected customers may have experienced inbox loading issues, delays in conversation updates, message delivery failures, conversation assignment issues, and disruptions to Fin replies. This issue is now 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

Read the full incident report →

Started May 21, 2026, 07:25 PM UTC· resolved May 21, 2026, 07:25 PM UTC

1. identified May 21, 2026, 11:09 AM UTC

   Workspaces in the USA hosting region may be experiencing incomplete historical data in reporting features since May 19th. We are backfilling data and should be up to date later today.

2. resolved May 21, 2026, 07:25 PM UTC

   The issue is resolved, reporting data is up to date.

Read the full incident report →

Started May 20, 2026, 10:17 AM UTC· resolved May 20, 2026, 10:17 AM UTC

1. monitoring May 20, 2026, 10:16 AM UTC

   Between 09:08 - 09:28 UTC, images were not loading in the Intercom inbox. Apologies for the disruption.

2. resolved May 20, 2026, 10:17 AM UTC

   The issue is resolved.

Read the full incident report →

Started Apr 27, 2026, 12:51 PM UTC· resolved Apr 27, 2026, 12:51 PM UTC

1. investigating Apr 27, 2026, 11:43 AM UTC

   We're seeing issues with the REST API in the Australia hosting region. Our team is aware and investigating the issue. We’ll update you here as soon as we have more specific information.

2. monitoring Apr 27, 2026, 12:08 PM UTC

   We have implemented a change and are monitoring for recovery. We’ll let you know when we are confident in our recovery is completed.

3. investigating Apr 27, 2026, 12:33 PM UTC

   The deployed fix did not resolve the issue. Team are continuing to investigate. We will update the status as soon as have identified the issue

4. monitoring Apr 27, 2026, 12:48 PM UTC

   We have implemented a change and are monitoring for recovery. We’ll let you know when we are confident in our recovery is completed.

5. resolved Apr 27, 2026, 12:51 PM UTC

   On April 27, 2026, between approximately 11:14 UTC and 12:52 UTC, customers hosted in our Australia region experienced errors and timeouts when using the Intercom REST API. Requests to the API would fail with timeout errors. Fin, the Intercom Inbox, and the Messenger were not affected during this window. Confirmed that the fix implemented resolved the issue, service is operating normally.

Read the full incident report →

Started Apr 22, 2026, 01:07 AM UTC· resolved Apr 22, 2026, 01:07 AM UTC

1. investigating Apr 21, 2026, 11:30 PM UTC

   Fin is currently experiencing difficulties affecting some customers. Our team is aware of the issue and are currently investigating. We will update you here when we have more information.

2. identified Apr 22, 2026, 12:03 AM UTC

   We have identified the root cause of the issue and are implementing a fix. We’ll update you here once we’ve confirmed our fix has been effective.

3. monitoring Apr 22, 2026, 12:55 AM UTC

   We have implemented a fix and are monitoring for recovery. We’ll let you know when we are confident in our recovery.

4. resolved Apr 22, 2026, 01:07 AM UTC

   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

Read the full incident report →

Started Apr 21, 2026, 10:24 AM UTC· resolved Apr 21, 2026, 10:24 AM UTC

1. investigating Apr 21, 2026, 09:57 AM UTC

   Fin's ability to deliver responses to customers is degraded. We are investigating the issue.

2. resolved Apr 21, 2026, 10:24 AM UTC

   On April 21, 2026, between 09:57 UTC and 10:24 UTC, Fin was unable to reliably respond to customer conversations in the EU region. The issue has now been resolved and Fin is operating as expected. We will follow up with a full Root Cause Analysis once we understand the technical details of the issue.

Read the full incident report →

Started Apr 15, 2026, 05:29 PM UTC· resolved Apr 15, 2026, 05:29 PM UTC

1. investigating Apr 15, 2026, 04:57 PM UTC

   Fin is currently experiencing delayed response times. Our team is aware of the issue and are currently investigating. We will update you here when we have more information.

2. identified Apr 15, 2026, 05:20 PM UTC

   We have identified the root cause of the issue and are implementing a fix. We’ll update you here once we’ve confirmed our fix has been effective.

3. resolved Apr 15, 2026, 05:29 PM UTC

   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

Read the full incident report →

Started Apr 14, 2026, 02:57 PM UTC· resolved Apr 14, 2026, 02:57 PM UTC

1. investigating Apr 14, 2026, 11:29 AM UTC

   Fin is currently experiencing difficulties. Our team is aware of the issue and are currently investigating. We will update you here when we have more information.

2. investigating Apr 14, 2026, 11:42 AM UTC

   Our team is continuing to investigate. We'll update you here as soon as we have more specific information.

3. investigating Apr 14, 2026, 11:53 AM UTC

   We have identified the root cause and are working on a mitigation. Customer Impact: Fin is not currently responding to conversations with those conversations being assigned to the default inbox. There is no data loss. Fin Voice is not successfully handing off conversations to teammates.

4. identified Apr 14, 2026, 12:15 PM UTC

   We have identified the root cause of the issue and are implementing a fix. We’ll update you here once we’ve confirmed our fix has been effective.

5. identified Apr 14, 2026, 12:40 PM UTC

   Fin is replying to conversations, but still cannot escalate to a human agent when necessary. Our team has identified a fix for this issue and is working on applying it.

6. monitoring Apr 14, 2026, 01:19 PM UTC

   As of 13:00 UTC, Fin and Fin Voice are operating normally for new conversations. For conversations during the incident that Fin did not respond and a teammate responded, Fin will not engage. For conversations where Fin or a teammate did not respond, Fin should re-engage with the conversation. We are continuing to re-drive conversations from the period.

7. monitoring Apr 14, 2026, 01:33 PM UTC

   The issue affecting Fin AI Agent and Fin Voice in the US region has been resolved. All services are operating normally. What happened: Between 11:18 and 12:20 UTC on April 14, 2026, a database issue prevented Fin from generating conversation parts in the US region. This affected Fin AI Agent across Messenger, Inbox, and Workflows. Fin Voice experienced an issue where it was unable to hand over conversations to teammates and would terminate calls with an error message at the escalation point. At 12:20 UTC we implemented a mitigation to enable Fin to start delivering answers to customers again. New conversations, or conversations where a customer messaged to Fin again would receive an answer but pre-existing conversations or conversations that had been actioned by a teammate would not receive a reply. At this point escalations from the Fin AI Agent and Fin Voice to customer support teams were not functioning as expected. At 13:00 UTC Fin AI Agent and Fin Voice were functioning as normal for new conversations. At approximately 13:05 UTC we retried any pending Fin conversations that had not yet been actioned by a teammate on workspaces. EU and AU regions were not impacted by this incident. What's next: Reporting data for affected customer workspaces may be incomplete for the duration of the incident window. We are investigating a method for backfilling this data and will provide a follow-up update once that is complete. A full root cause analysis will be forthcoming once all details of the incident have been established. We apologize for the disruption to your business.

8. resolved Apr 14, 2026, 02:57 PM UTC

   The issue affecting Fin AI Agent and Fin Voice in the US region has been resolved. All services are operating normally. What happened: Between 11:18 and 12:20 UTC on April 14, 2026, a database issue prevented Fin from generating conversation parts in the US region. This affected Fin AI Agent across Messenger, Inbox, and Workflows. Fin Voice experienced an issue where it was unable to hand over conversations to teammates and would terminate calls with an error message at the escalation point. At 12:20 UTC we implemented a mitigation to enable Fin to start delivering answers to customers again. New conversations, or conversations where a customer messaged to Fin again would receive an answer but pre-existing conversations or conversations that had been actioned by a teammate would not receive a reply. At this point escalations from the Fin AI Agent and Fin Voice to customer support teams were not functioning as expected. At 13:00 UTC Fin AI Agent and Fin Voice were functioning as normal for new conversations. At approximately 13:05 UTC we retried any pending Fin conversations that had not yet been actioned by a teammate on workspaces. EU and AU regions were not impacted by this incident. What's next: Reporting data for affected customer workspaces may be incomplete for the duration of the incident window. We are investigating a method for backfilling this data and will provide a follow-up update once that is complete. A full root cause analysis will be forthcoming once all details of the incident have been established. We apologize for the disruption to your business.

Read the full incident report →

Started Apr 11, 2026, 03:50 PM UTC· resolved Apr 11, 2026, 03:50 PM UTC

1. resolved Apr 11, 2026, 03:48 PM UTC

   We experienced elevated 5xx errors with our help center product between 16:00 UTC to 16:40 UTC. The issue has been resolved and all functionality should be back to normal. 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.

2. resolved Apr 11, 2026, 03:50 PM UTC

   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

Read the full incident report →

Started Apr 09, 2026, 07:35 AM UTC· resolved Apr 09, 2026, 07:35 AM UTC

1. investigating Apr 08, 2026, 06:22 PM UTC

   We're seeing issues with Intercom related to Inbox and email forwarding specifically across all regions. Our team is aware and investigating the issue. We’ll update you here as soon as we have more specific information.

2. investigating Apr 08, 2026, 07:17 PM UTC

   We are seeing a subset of customers intermittently affected by delays in email forwarding in the Intercom Inbox. Our team is actively investigating the issue. We’ll update you here as soon as we have more specific information.

3. resolved Apr 09, 2026, 07:35 AM UTC

   Between ~18.00 - ~23.00 UTC on the 8th April, a subset of customers experienced intermittent issues with email forwarding in the Intercom Inbox. During the incident Google has an incident open related to delivery issue that was impacting inbound support emails. The team continues to confirm root cause with an RCA to follow. This issue should now be resolved and all services are restored to normal functionality.

Read the full incident report →

Started Mar 30, 2026, 02:13 PM UTC· resolved Mar 30, 2026, 02:13 PM UTC

1. resolved Mar 30, 2026, 02:13 PM UTC

   We experienced elevated errors and latency on the Conversations API, specifically with the search method. The impact occurred between 11.47 UTC and 12.18 UTC. 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.

Read the full incident report →