Intercom Outage History

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 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 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 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 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 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 27, 2026, 11:43 AM UTC· resolved Apr 27, 2026, 12:51 PM UTC

No vendor updates were posted for this incident.

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 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 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, 11:30 PM UTC· resolved Apr 22, 2026, 01:07 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

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

No vendor updates were posted for this incident.

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 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 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 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 11, 2026, 03:48 PM UTC· resolved Apr 11, 2026, 03:48 PM UTC

No vendor updates were posted for this incident.

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 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 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 →