- Detected by Pingoru
- Apr 27, 2026, 12:51 PM UTC
- Resolved
- Apr 27, 2026, 12:51 PM UTC
- Duration
- —
Affected: REST API
Timeline · 5 updates
-
investigating Apr 27, 2026, 11:43 AM UTC
Status: Investigating 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. Affected components REST API (Partial outage)
-
monitoring Apr 27, 2026, 12:08 PM UTC
Status: Monitoring We have implemented a change and are monitoring for recovery. We’ll let you know when we are confident in our recovery is completed. Affected components REST API (Partial outage)
-
investigating Apr 27, 2026, 12:33 PM UTC
Status: Investigating 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 Affected components REST API (Partial outage)
-
monitoring Apr 27, 2026, 12:48 PM UTC
Status: Monitoring We have implemented a change and are monitoring for recovery. We’ll let you know when we are confident in our recovery is completed. Affected components REST API (Partial outage)
-
resolved Apr 27, 2026, 12:51 PM UTC
Status: Resolved 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. Affected components REST API (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 27, 2026, 11:43 AM UTC
- Resolved
- Apr 27, 2026, 12:51 PM UTC
- Duration
- 1h 8m
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 01:07 AM UTC
- Resolved
- Apr 22, 2026, 01:07 AM UTC
- Duration
- —
Affected: Fin AI Agent
Timeline · 4 updates
-
investigating Apr 21, 2026, 11:30 PM UTC
Status: Investigating 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. Affected components Fin AI Agent (Degraded performance)
-
identified Apr 22, 2026, 12:03 AM UTC
Status: Identified 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. Affected components Fin AI Agent (Degraded performance)
-
monitoring Apr 22, 2026, 12:55 AM UTC
Status: Monitoring We have implemented a fix and are monitoring for recovery. We’ll let you know when we are confident in our recovery. Affected components Fin AI Agent (Degraded performance)
-
resolved Apr 22, 2026, 01:07 AM UTC
Status: Resolved 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 Affected components Fin AI Agent (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 01:07 AM UTC
- Resolved
- Apr 22, 2026, 01:07 AM UTC
- Duration
- —
Affected: Fin AI Agent
Timeline · 4 updates
-
investigating Apr 21, 2026, 11:30 PM UTC
Status: Investigating 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. Affected components Fin AI Agent (Degraded performance)
-
identified Apr 22, 2026, 12:03 AM UTC
Status: Identified 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. Affected components Fin AI Agent (Degraded performance)
-
monitoring Apr 22, 2026, 12:55 AM UTC
Status: Monitoring We have implemented a fix and are monitoring for recovery. We’ll let you know when we are confident in our recovery. Affected components Fin AI Agent (Degraded performance)
-
resolved Apr 22, 2026, 01:07 AM UTC
Status: Resolved 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 Affected components Fin AI Agent (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 01:07 AM UTC
- Resolved
- Apr 22, 2026, 01:07 AM UTC
- Duration
- —
Affected: Fin AI Agent
Timeline · 4 updates
-
investigating Apr 21, 2026, 11:30 PM UTC
Status: Investigating 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. Affected components Fin AI Agent (Degraded performance)
-
identified Apr 22, 2026, 12:03 AM UTC
Status: Identified 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. Affected components Fin AI Agent (Degraded performance)
-
monitoring Apr 22, 2026, 12:55 AM UTC
Status: Monitoring We have implemented a fix and are monitoring for recovery. We’ll let you know when we are confident in our recovery. Affected components Fin AI Agent (Degraded performance)
-
resolved Apr 22, 2026, 01:07 AM UTC
Status: Resolved 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 Affected components Fin AI Agent (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 21, 2026, 11:30 PM UTC
- Resolved
- Apr 22, 2026, 01:07 AM UTC
- Duration
- 1h 36m
Read the full incident report →
- Detected by Pingoru
- Apr 21, 2026, 11:13 AM UTC
- Resolved
- Apr 21, 2026, 10:24 AM UTC
- Duration
- —
Read the full incident report →
- Detected by Pingoru
- Apr 21, 2026, 10:24 AM UTC
- Resolved
- Apr 21, 2026, 10:24 AM UTC
- Duration
- —
Affected: Fin AI AgentInboxWeb MessengerMobile MessengerWebhooksREST APIPhoneCopilotTicketsOmnichannelHelp CenterApps and IntegrationsReportingKnowledge HubOutboundOther
Timeline · 2 updates
-
investigating Apr 21, 2026, 09:57 AM UTC
Status: Investigating Fin's ability to deliver responses to customers is degraded. We are investigating the issue. Affected components Mobile Messenger (Operational) Web Messenger (Operational) Tickets (Operational) Help Center (Operational) Apps and Integrations (Operational) Knowledge Hub (Operational) Fin AI Agent (Full outage) Inbox (Operational) Webhooks (Operational) Omnichannel (Operational) Reporting (Operational) REST API (Operational) Copilot (Operational) Outbound (Operational) Other (Operational) Phone (Operational)
-
resolved Apr 21, 2026, 10:24 AM UTC
Status: Resolved 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. Affected components Fin AI Agent (Operational) Inbox (Operational) Webhooks (Operational) Help Center (Operational) Web Messenger (Operational) Outbound (Operational) REST API (Operational) Omnichannel (Operational) Apps and Integrations (Operational) Reporting (Operational) Other (Operational) Mobile Messenger (Operational) Phone (Operational) Copilot (Operational) Tickets (Operational) Knowledge Hub (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 11, 2026, 03:50 PM UTC
- Resolved
- Apr 11, 2026, 03:50 PM UTC
- Duration
- —
Affected: Fin AI AgentInboxWeb MessengerMobile MessengerWebhooksREST APIPhoneCopilotTicketsOmnichannelHelp CenterApps and IntegrationsReportingKnowledge HubOutboundOther
Timeline · 2 updates
-
resolved Apr 11, 2026, 03:48 PM UTC
Status: Resolved 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. Affected components Web Messenger (Operational) Copilot (Operational) Tickets (Operational) Reporting (Operational) Knowledge Hub (Operational) Other (Operational) Mobile Messenger (Operational) Phone (Operational) REST API (Operational) Omnichannel (Operational) Help Center (Operational) Apps and Integrations (Operational) Inbox (Operational) Fin AI Agent (Operational) Webhooks (Operational) Outbound (Operational)
-
resolved Apr 11, 2026, 03:50 PM UTC
Status: Resolved 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 Affected components Help Center (Operational) Fin AI Agent (Operational) Inbox (Operational) Phone (Operational) REST API (Operational) Webhooks (Operational) Outbound (Operational) Other (Operational) Reporting (Operational) Knowledge Hub (Operational) Web Messenger (Operational) Copilot (Operational) Tickets (Operational) Omnichannel (Operational) Mobile Messenger (Operational) Apps and Integrations (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 11, 2026, 03:50 PM UTC
- Resolved
- Apr 11, 2026, 03:50 PM UTC
- Duration
- —
Affected: Fin AI AgentInboxWeb MessengerMobile MessengerWebhooksREST APIPhoneCopilotTicketsOmnichannelHelp CenterApps and IntegrationsReportingKnowledge HubOutboundOther
Timeline · 2 updates
-
resolved Apr 11, 2026, 03:48 PM UTC
Status: Resolved 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. Affected components Fin AI Agent (Operational) Other (Operational) Inbox (Operational) Webhooks (Operational) Copilot (Operational) Tickets (Operational) Knowledge Hub (Operational) Mobile Messenger (Operational) Web Messenger (Operational) Phone (Operational) Apps and Integrations (Operational) REST API (Operational) Omnichannel (Operational) Help Center (Operational) Reporting (Operational) Outbound (Operational)
-
resolved Apr 11, 2026, 03:50 PM UTC
Status: Resolved 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 Affected components Mobile Messenger (Operational) Reporting (Operational) REST API (Operational) Tickets (Operational) Omnichannel (Operational) Knowledge Hub (Operational) Outbound (Operational) Other (Operational) Webhooks (Operational) Apps and Integrations (Operational) Web Messenger (Operational) Fin AI Agent (Operational) Inbox (Operational) Phone (Operational) Copilot (Operational) Help Center (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 11, 2026, 03:50 PM UTC
- Resolved
- Apr 11, 2026, 03:50 PM UTC
- Duration
- —
Affected: Fin AI AgentInboxWeb MessengerMobile MessengerWebhooksREST APIPhoneCopilotTicketsOmnichannelHelp CenterApps and IntegrationsReportingKnowledge HubOutboundOther
Timeline · 2 updates
-
resolved Apr 11, 2026, 03:48 PM UTC
Status: Resolved 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. Affected components Other (Operational) Web Messenger (Operational) Omnichannel (Operational) Knowledge Hub (Operational) Outbound (Operational) Fin AI Agent (Operational) Webhooks (Operational) Copilot (Operational) Reporting (Operational) Mobile Messenger (Operational) Inbox (Operational) Phone (Operational) REST API (Operational) Tickets (Operational) Help Center (Operational) Apps and Integrations (Operational)
-
resolved Apr 11, 2026, 03:50 PM UTC
Status: Resolved 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 Affected components REST API (Operational) Omnichannel (Operational) Apps and Integrations (Operational) Reporting (Operational) Other (Operational) Inbox (Operational) Phone (Operational) Tickets (Operational) Knowledge Hub (Operational) Web Messenger (Operational) Webhooks (Operational) Copilot (Operational) Mobile Messenger (Operational) Fin AI Agent (Operational) Help Center (Operational) Outbound (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 11, 2026, 03:48 PM UTC
- Resolved
- Apr 11, 2026, 03:48 PM UTC
- Duration
- —
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2026, 07:35 AM UTC
- Resolved
- Apr 09, 2026, 07:35 AM UTC
- Duration
- —
Affected: Inbox
Timeline · 3 updates
-
investigating Apr 08, 2026, 06:22 PM UTC
Status: Investigating 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. Affected components Inbox (Partial outage)
-
investigating Apr 08, 2026, 07:17 PM UTC
Status: Investigating 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. Affected components Inbox (Partial outage)
-
resolved Apr 09, 2026, 07:35 AM UTC
Status: Resolved 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. Affected components Inbox (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2026, 07:35 AM UTC
- Resolved
- Apr 09, 2026, 07:35 AM UTC
- Duration
- —
Affected: Inbox
Timeline · 3 updates
-
investigating Apr 08, 2026, 06:22 PM UTC
Status: Investigating 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. Affected components Inbox (Partial outage)
-
investigating Apr 08, 2026, 07:17 PM UTC
Status: Investigating 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. Affected components Inbox (Partial outage)
-
resolved Apr 09, 2026, 07:35 AM UTC
Status: Resolved 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. Affected components Inbox (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2026, 07:35 AM UTC
- Resolved
- Apr 09, 2026, 07:35 AM UTC
- Duration
- —
Affected: Inbox
Timeline · 3 updates
-
investigating Apr 08, 2026, 06:22 PM UTC
Status: Investigating 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. Affected components Inbox (Partial outage)
-
investigating Apr 08, 2026, 07:17 PM UTC
Status: Investigating 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. Affected components Inbox (Partial outage)
-
resolved Apr 09, 2026, 07:35 AM UTC
Status: Resolved 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. Affected components Inbox (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 08, 2026, 06:22 PM UTC
- Resolved
- Apr 09, 2026, 07:35 AM UTC
- Duration
- 13h 12m
Read the full incident report →
- Detected by Pingoru
- Mar 30, 2026, 02:17 PM UTC
- Resolved
- Mar 30, 2026, 02:13 PM UTC
- Duration
- —
Read the full incident report →
- Detected by Pingoru
- Mar 30, 2026, 02:13 PM UTC
- Resolved
- Mar 30, 2026, 02:13 PM UTC
- Duration
- —
Affected: Fin AI AgentInboxWeb MessengerMobile MessengerWebhooksREST APIPhoneCopilotTicketsOmnichannelHelp CenterApps and IntegrationsReportingKnowledge HubOutboundOther
Timeline · 1 update
-
resolved Mar 30, 2026, 02:13 PM UTC
Status: Resolved 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. Affected components Mobile Messenger (Operational) Fin AI Agent (Operational) Help Center (Operational) Knowledge Hub (Operational) Outbound (Operational) Webhooks (Operational) REST API (Operational) Reporting (Operational) Web Messenger (Operational) Inbox (Operational) Phone (Operational) Copilot (Operational) Apps and Integrations (Operational) Other (Operational) Tickets (Operational) Omnichannel (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 20, 2026, 07:52 PM UTC
- Resolved
- Mar 20, 2026, 07:52 PM UTC
- Duration
- —
Affected: Inbox
Timeline · 3 updates
-
investigating Mar 20, 2026, 06:43 PM UTC
Status: Investigating We're seeing errors and latency issues with Intercom Inbox. Our team is aware and investigating the issue. We’ll update you here as soon as we have more specific information. Affected components Inbox (Degraded performance)
-
investigating Mar 20, 2026, 07:32 PM UTC
Status: Investigating We’re actively investigating errors and elevated latency affecting Inbox and working to identify the root cause. We’ll provide an update as soon as we have more information Affected components Inbox (Degraded performance)
-
resolved Mar 20, 2026, 07:52 PM UTC
Status: Resolved 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 Affected components Inbox (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 20, 2026, 07:26 PM UTC
- Resolved
- Mar 20, 2026, 07:26 PM UTC
- Duration
- —
Affected: Reporting
Timeline · 2 updates
-
monitoring Mar 20, 2026, 03:05 PM UTC
Status: Monitoring Reporting data is delayed in the EU hosting region. We're expecting it to be recovered by 17:00 UTC. Affected components Reporting (Degraded performance)
-
resolved Mar 20, 2026, 07:26 PM UTC
Status: Resolved Reporting data is back up to date. Affected components Reporting (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 20, 2026, 06:43 PM UTC
- Resolved
- Mar 20, 2026, 07:52 PM UTC
- Duration
- 1h 9m
Read the full incident report →
- Detected by Pingoru
- Mar 20, 2026, 05:04 PM UTC
- Resolved
- Mar 20, 2026, 05:04 PM UTC
- Duration
- —
Affected: InboxWeb MessengerMobile Messenger
Timeline · 2 updates
-
identified Mar 20, 2026, 04:47 PM UTC
Status: Identified The Intercom Inbox and other features in the European hosting region had two waves of errors between 16:35:30 - 16:36:00 UTC and 16:38:50 - 16:39:40 UTC. We have identified the cause. Affected components Web Messenger (Partial outage) Inbox (Partial outage) Mobile Messenger (Partial outage)
-
resolved Mar 20, 2026, 05:04 PM UTC
Status: Resolved This issue should now be resolved and all services are restored to normal functionality. Affected components Mobile Messenger (Operational) Web Messenger (Operational) Inbox (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 20, 2026, 04:47 PM UTC
- Resolved
- Mar 20, 2026, 05:04 PM UTC
- Duration
- 16m
Read the full incident report →
- Detected by Pingoru
- Mar 20, 2026, 03:05 PM UTC
- Resolved
- Mar 20, 2026, 07:26 PM UTC
- Duration
- 4h 20m
Read the full incident report →
- Detected by Pingoru
- Mar 16, 2026, 05:50 PM UTC
- Resolved
- Mar 16, 2026, 05:50 PM UTC
- Duration
- —
Affected: Inbox
Timeline · 3 updates
-
investigating Mar 16, 2026, 03:50 PM UTC
Status: Investigating The Intercom Inbox is experiencing difficulties in the European hosting region. Our team is aware of the issue and are currently investigating. We will update you here when we have more information. Affected components Inbox (Full outage)
-
monitoring Mar 16, 2026, 04:16 PM UTC
Status: Monitoring The inbox is now accessible since 16:07 UTC Affected components Inbox (Full outage)
-
resolved Mar 16, 2026, 05:50 PM UTC
Status: Resolved This incident is resolved. The Inbox had high latency and errors between 15:44 UTC and 16:07 UTC. The Messenger was impacted between 16:03 UTC and 16:09 UTC. We will provide a root cause analysis here within 48 hours. Affected components Inbox (Operational)
Read the full incident report →