Intercom Outage History

Intercom is up right now

Pingoru has recorded 116 incidents for Intercom: 116 in the last 12 months and 18 in the last 90 days.

Source: intercomstatus.com

116incidents recorded
116last 12 months
18last 90 days
56 minutestypical duration
Incidents per month
01020AprMayJunJulAugSepOct3
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Intercom in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20262020 of 720 (3%)
May 202640 of 744 (0%)
June 2026120 of 720 (0%)
July 202610 of 744 (0%)
August 202657 of 744 (1%)
September 2026107 of 720 (1%)
October 202630 of 584 (0%)

Incidents, newest first

Minor January 29, 2026 [AU Hosting] Fin for Salesforce Errors – Fin AI Agent

Started Jan 29, 2026, 09:32 PM UTC· resolved Jan 29, 2026, 09:32 PM UTC

  1. identified Jan 29, 2026, 08:34 PM UTC

    Fin for Salesforce is experiencing errors. Customers using Fin for Salesforce can resolve this issue by going into Fin Settings, then Salesforce Integration, and then clicking reconnect. This will allow for full service recovery.

  2. monitoring Jan 29, 2026, 09:13 PM UTC

    To recover service, log into Fin for Salesforce, go to Fin Settings, then Salesforce Integration, and then click reconnect. If you are still having issues, go to https://login.salesforce.com/ and log out of all sessions. Then try reconnecting again.

  3. resolved Jan 29, 2026, 09:32 PM UTC

    Customers using Fin for Salesforce can resolve this issue by going into Fin Settings, then Salesforce Integration, and then clicking reconnect. This operation must be performed by the cluster. We have confirmed that all customers following this process have seen recovery.

Read the full incident report →

Minor January 29, 2026 [EU Hosting] Fin for Salesforce Errors – Fin AI Agent

Started Jan 29, 2026, 09:32 PM UTC· resolved Jan 29, 2026, 09:32 PM UTC

  1. identified Jan 29, 2026, 08:34 PM UTC

    Fin for Salesforce is experiencing errors. Customers using Fin for Salesforce can resolve this issue by going into Fin Settings, then Salesforce Integration, and then clicking reconnect. This will allow for full service recovery.

  2. monitoring Jan 29, 2026, 09:13 PM UTC

    To recover service, log into Fin for Salesforce, go to Fin Settings, then Salesforce Integration, and then click reconnect. If you are still having issues, go to https://login.salesforce.com/ and log out of all sessions. Then try reconnecting again.

  3. resolved Jan 29, 2026, 09:32 PM UTC

    Customers using Fin for Salesforce can resolve this issue by going into Fin Settings, then Salesforce Integration, and then clicking reconnect. This operation must be performed by the cluster. We have confirmed that all customers following this process have seen recovery.

Read the full incident report →

Minor January 29, 2026 [US Hosting] Fin for Salesforce Errors – Fin AI Agent

Started Jan 29, 2026, 09:32 PM UTC· resolved Jan 29, 2026, 09:32 PM UTC

  1. identified Jan 29, 2026, 08:34 PM UTC

    Fin for Salesforce is experiencing errors. Customers using Fin for Salesforce can resolve this issue by going into Fin Settings, then Salesforce Integration, and then clicking reconnect. This will allow for full service recovery.

  2. monitoring Jan 29, 2026, 09:13 PM UTC

    To recover service, log into Fin for Salesforce, go to Fin Settings, then Salesforce Integration, and then click reconnect. If you are still having issues, go to https://login.salesforce.com/ and log out of all sessions. Then try reconnecting again.

  3. resolved Jan 29, 2026, 09:32 PM UTC

    Customers using Fin for Salesforce can resolve this issue by going into Fin Settings, then Salesforce Integration, and then clicking reconnect. This operation must be performed by the cluster. We have confirmed that all customers following this process have seen recovery.

Read the full incident report →

Minor January 29, 2026 [AU Hosting] Customers and teammates are currently unable to make or receive phone calls. – Phone

Started Jan 29, 2026, 05:31 PM UTC· resolved Jan 29, 2026, 05:31 PM UTC

  1. investigating Jan 29, 2026, 05:20 PM UTC

    We're seeing issues with Phone, specifically where customers and teammates are currently unable to make or receive phone calls..Our team is aware and investigating the issue. We’ll update you here as soon as we have more specific information.

  2. resolved Jan 29, 2026, 05:31 PM UTC

    Between 16:20 - 17:16 UTC, most phone features were in a degraded state, including outbound and inbound phone calls. We apologise for the disruption.

Read the full incident report →

Minor January 29, 2026 [EU Hosting] Customers and teammates are currently unable to make or receive phone calls. – Phone

Started Jan 29, 2026, 05:31 PM UTC· resolved Jan 29, 2026, 05:31 PM UTC

  1. investigating Jan 29, 2026, 05:20 PM UTC

    We're seeing issues with Phone, specifically where customers and teammates are currently unable to make or receive phone calls..Our team is aware and investigating the issue. We’ll update you here as soon as we have more specific information.

  2. resolved Jan 29, 2026, 05:31 PM UTC

    Between 16:20 - 17:16 UTC, most phone features were in a degraded state, including outbound and inbound phone calls. We apologise for the disruption.

Read the full incident report →

Minor January 29, 2026 [US Hosting] Customers and teammates are currently unable to make or receive phone calls. – Phone

Started Jan 29, 2026, 05:31 PM UTC· resolved Jan 29, 2026, 05:31 PM UTC

  1. investigating Jan 29, 2026, 05:20 PM UTC

    We're seeing issues with Phone, specifically where customers and teammates are currently unable to make or receive phone calls..Our team is aware and investigating the issue. We’ll update you here as soon as we have more specific information.

  2. resolved Jan 29, 2026, 05:31 PM UTC

    Between 16:20 - 17:16 UTC, most phone features were in a degraded state, including outbound and inbound phone calls. We apologise for the disruption.

Read the full incident report →

Notice January 27, 2026 Latency in the inbox for a subset of customers –

Started Jan 27, 2026, 05:03 PM UTC· resolved Jan 27, 2026, 05:03 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor January 27, 2026 [US Hosting] Latency in the inbox for a subset of customers – Fin AI Agent, Inbox, Web Messenger, Mobile Messenger and 12 more

Started Jan 27, 2026, 05:03 PM UTC· resolved Jan 27, 2026, 05:03 PM UTC

  1. resolved Jan 27, 2026, 05:03 PM UTC

    A small subset of Intercom customers experienced degraded service including inconsistent latency and stale data when reading from the platform.

Read the full incident report →