- Detected by Pingoru
- Mar 05, 2026, 05:01 PM UTC
- Resolved
- Mar 05, 2026, 05:01 PM UTC
- Duration
- —
Affected: InboxReporting
Timeline · 4 updates
-
investigating Mar 05, 2026, 03:56 PM UTC
Status: Investigating We're seeing issues loading Workflows and Reports that access Conversation Attributes. 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) Reporting (Degraded performance)
-
investigating Mar 05, 2026, 04:25 PM UTC
Status: Investigating We're continuing to see issues with Reports and Workflows and our team continuing to investigate. We’ll keep you updated here as we know more. Affected components Inbox (Partial outage) Reporting (Partial outage)
-
identified Mar 05, 2026, 04:46 PM UTC
Status: Identified We have identified the root cause of the issue and are implementing a fix. We've limited the impact to specific Custom Reports. We’ll update you here once we’ve confirmed our fix has been effective. Affected components Inbox (Operational) Reporting (Partial outage)
-
resolved Mar 05, 2026, 05:01 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) Reporting (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 05, 2026, 03:56 PM UTC
- Resolved
- Mar 05, 2026, 05:01 PM UTC
- Duration
- 1h 5m
Read the full incident report →
- Detected by Pingoru
- Mar 04, 2026, 11:35 AM UTC
- Resolved
- Mar 04, 2026, 11:35 AM UTC
- Duration
- —
Read the full incident report →
- Detected by Pingoru
- Mar 04, 2026, 11:35 AM UTC
- Resolved
- Mar 04, 2026, 11:35 AM UTC
- Duration
- —
Affected: Fin AI AgentInboxWeb MessengerMobile MessengerWebhooksREST APIPhoneCopilotTicketsOmnichannelHelp CenterApps and IntegrationsReportingKnowledge HubOutboundOther
Timeline · 2 updates
-
identified Mar 04, 2026, 10:52 AM UTC
Status: Identified We have identified a problem loading User and Conversation Data within the Helpdesk. Our team is aware and investigating the issue. We’ll update you here as soon as we have more specific information. Affected components Omnichannel (Operational) Other (Operational) Knowledge Hub (Operational) Mobile Messenger (Operational) Web Messenger (Operational) Fin AI Agent (Operational) Webhooks (Operational) Copilot (Operational) Tickets (Operational) Reporting (Operational) Inbox (Partial outage) Phone (Operational) Help Center (Operational) Apps and Integrations (Operational) Outbound (Operational) REST API (Operational)
-
resolved Mar 04, 2026, 11:35 AM UTC
Status: Resolved From 10:52 - 11:35 UTC, User Data and Conversation Data would not load in the Helpdesk. There were also failures in Ticket Creation. 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) REST API (Operational) Outbound (Operational) Omnichannel (Operational) Web Messenger (Operational) Fin AI Agent (Operational) Phone (Operational) Webhooks (Operational) Copilot (Operational) Tickets (Operational) Other (Operational) Inbox (Operational) Help Center (Operational) Apps and Integrations (Operational) Reporting (Operational) Knowledge Hub (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 04, 2026, 11:35 AM UTC
- Resolved
- Mar 04, 2026, 11:35 AM UTC
- Duration
- —
Affected: Fin AI AgentInboxWeb MessengerMobile MessengerWebhooksREST APIPhoneCopilotTicketsOmnichannelHelp CenterApps and IntegrationsReportingKnowledge HubOutboundOther
Timeline · 2 updates
-
identified Mar 04, 2026, 10:52 AM UTC
Status: Identified We have identified a problem loading User and Conversation Data within the Helpdesk. 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 (Operational) Reporting (Operational) Knowledge Hub (Operational) Web Messenger (Operational) Fin AI Agent (Operational) Webhooks (Operational) Tickets (Operational) Help Center (Operational) Outbound (Operational) Inbox (Partial outage) Copilot (Operational) Omnichannel (Operational) Other (Operational) Mobile Messenger (Operational) Phone (Operational) Apps and Integrations (Operational)
-
resolved Mar 04, 2026, 11:35 AM UTC
Status: Resolved From 10:52 - 11:35 UTC, User Data and Conversation Data would not load in the Helpdesk. There were also failures in Ticket Creation. 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 Web Messenger (Operational) Inbox (Operational) Help Center (Operational) Fin AI Agent (Operational) Phone (Operational) REST API (Operational) Omnichannel (Operational) Webhooks (Operational) Copilot (Operational) Reporting (Operational) Outbound (Operational) Mobile Messenger (Operational) Tickets (Operational) Apps and Integrations (Operational) Knowledge Hub (Operational) Other (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 04, 2026, 11:35 AM UTC
- Resolved
- Mar 04, 2026, 11:35 AM UTC
- Duration
- —
Affected: Fin AI AgentInboxWeb MessengerMobile MessengerWebhooksREST APIPhoneCopilotTicketsOmnichannelHelp CenterApps and IntegrationsReportingKnowledge HubOutboundOther
Timeline · 2 updates
-
identified Mar 04, 2026, 10:52 AM UTC
Status: Identified We have identified a problem loading User and Conversation Data within the Helpdesk. Our team is aware and investigating the issue. We’ll update you here as soon as we have more specific information. Affected components Fin AI Agent (Operational) Omnichannel (Operational) Phone (Operational) Help Center (Operational) Inbox (Partial outage) Webhooks (Operational) Copilot (Operational) Apps and Integrations (Operational) Reporting (Operational) Other (Operational) REST API (Operational) Tickets (Operational) Knowledge Hub (Operational) Outbound (Operational) Mobile Messenger (Operational) Web Messenger (Operational)
-
resolved Mar 04, 2026, 11:35 AM UTC
Status: Resolved From 10:52 - 11:35 UTC, User Data and Conversation Data would not load in the Helpdesk. There were also failures in Ticket Creation. 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 Apps and Integrations (Operational) Knowledge Hub (Operational) Mobile Messenger (Operational) Webhooks (Operational) Copilot (Operational) Other (Operational) Phone (Operational) Omnichannel (Operational) Help Center (Operational) Outbound (Operational) Fin AI Agent (Operational) Inbox (Operational) Reporting (Operational) Web Messenger (Operational) REST API (Operational) Tickets (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 02:08 PM UTC
- Resolved
- Mar 03, 2026, 02:08 PM UTC
- Duration
- —
Affected: Fin AI AgentInbox
Timeline · 4 updates
-
investigating Mar 03, 2026, 01:04 PM UTC
Status: Investigating We're investigating delays in processing conversations in Intercom in the USA hosting region. This will delay conversations reaching the inbox and being processed by Fin. Affected components Fin AI Agent (Degraded performance) Inbox (Degraded performance)
-
identified Mar 03, 2026, 01:34 PM UTC
Status: Identified We're continuing to investigate delayed conversation processing. Affected components Fin AI Agent (Degraded performance) Inbox (Degraded performance)
-
monitoring Mar 03, 2026, 01:50 PM UTC
Status: Monitoring We've fixed conversation processing and are monitoring the situation. Affected components Fin AI Agent (Degraded performance) Inbox (Degraded performance)
-
resolved Mar 03, 2026, 02:08 PM UTC
Status: Resolved Between 12:32 UTC and 13:11 UTC there were intermittent delays in conversation processing of up to a few minutes, across all of Intercom and Fin in the USA hosting region. The cause of the problem has been mitigated and we're immediately working on a deeper fix. Affected components Fin AI Agent (Operational) Inbox (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 01:04 PM UTC
- Resolved
- Mar 03, 2026, 02:08 PM UTC
- Duration
- 1h 3m
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 05:00 AM UTC
- Resolved
- Mar 03, 2026, 05:00 AM UTC
- Duration
- —
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 05:00 AM UTC
- Resolved
- Mar 03, 2026, 05:00 AM UTC
- Duration
- —
Affected: Fin AI AgentInboxWeb MessengerMobile MessengerWebhooksREST APIPhoneCopilotTicketsOmnichannelHelp CenterApps and IntegrationsReportingKnowledge HubOutboundOther
Timeline · 2 updates
-
identified Mar 02, 2026, 04:30 PM UTC
Status: Identified Fin is currently experiencing difficulties. Fin may be slow to respond or escalate a conversation. Our team is aware of the issue and are currently investigating. We will update you here when we have more information. Affected components Apps and Integrations (Operational) Reporting (Operational) Outbound (Operational) Mobile Messenger (Operational) REST API (Operational) Help Center (Operational) Knowledge Hub (Operational) Web Messenger (Operational) Inbox (Operational) Webhooks (Operational) Other (Operational) Fin AI Agent (Degraded performance) Phone (Operational) Copilot (Operational) Tickets (Operational) Omnichannel (Operational)
-
resolved Mar 03, 2026, 05:00 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 Mobile Messenger (Operational) Knowledge Hub (Operational) Web Messenger (Operational) Fin AI Agent (Operational) Help Center (Operational) Phone (Operational) REST API (Operational) Copilot (Operational) Omnichannel (Operational) Reporting (Operational) Outbound (Operational) Inbox (Operational) Webhooks (Operational) Tickets (Operational) Apps and Integrations (Operational) Other (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2026, 05:53 PM UTC
- Resolved
- Feb 27, 2026, 05:53 PM UTC
- Duration
- —
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2026, 05:53 PM UTC
- Resolved
- Feb 27, 2026, 05:53 PM UTC
- Duration
- —
Affected: Fin AI AgentInboxWeb MessengerMobile MessengerWebhooksREST APIPhoneCopilotTicketsOmnichannelHelp CenterApps and IntegrationsReportingKnowledge HubOutboundOther
Timeline · 2 updates
-
investigating Feb 27, 2026, 04:44 PM UTC
Status: Investigating We're receiving reports that there is an issue routing inbound phone calls. Our team is aware and investigating the issue. We’ll update you here as soon as we have more specific information. Affected components Web Messenger (Operational) Fin AI Agent (Operational) Webhooks (Operational) Copilot (Operational) Omnichannel (Operational) Help Center (Operational) Other (Operational) Inbox (Operational) Tickets (Operational) Knowledge Hub (Operational) Apps and Integrations (Operational) Mobile Messenger (Operational) REST API (Operational) Phone (Partial outage) Outbound (Operational) Reporting (Operational)
-
resolved Feb 27, 2026, 05:53 PM UTC
Status: Resolved The team has shipped a fix and all phone calls should be properly routed now. Affected components Inbox (Operational) Webhooks (Operational) Copilot (Operational) Apps and Integrations (Operational) Web Messenger (Operational) Phone (Operational) REST API (Operational) Outbound (Operational) Fin AI Agent (Operational) Tickets (Operational) Omnichannel (Operational) Reporting (Operational) Other (Operational) Mobile Messenger (Operational) Help Center (Operational) Knowledge Hub (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2026, 05:53 PM UTC
- Resolved
- Feb 27, 2026, 05:53 PM UTC
- Duration
- —
Affected: Fin AI AgentInboxWeb MessengerMobile MessengerWebhooksREST APIPhoneCopilotTicketsOmnichannelHelp CenterApps and IntegrationsReportingKnowledge HubOutboundOther
Timeline · 2 updates
-
investigating Feb 27, 2026, 04:44 PM UTC
Status: Investigating We're receiving reports that there is an issue routing inbound phone calls. Our team is aware and investigating the issue. We’ll update you here as soon as we have more specific information. Affected components Help Center (Operational) Reporting (Operational) REST API (Operational) Web Messenger (Operational) Fin AI Agent (Operational) Copilot (Operational) Other (Operational) Mobile Messenger (Operational) Inbox (Operational) Webhooks (Operational) Omnichannel (Operational) Apps and Integrations (Operational) Knowledge Hub (Operational) Outbound (Operational) Phone (Partial outage) Tickets (Operational)
-
resolved Feb 27, 2026, 05:53 PM UTC
Status: Resolved The team has shipped a fix and all phone calls should be properly routed now. Affected components Web Messenger (Operational) Webhooks (Operational) Omnichannel (Operational) Reporting (Operational) Mobile Messenger (Operational) Tickets (Operational) Help Center (Operational) Apps and Integrations (Operational) Knowledge Hub (Operational) Other (Operational) Fin AI Agent (Operational) Inbox (Operational) Outbound (Operational) Phone (Operational) REST API (Operational) Copilot (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2026, 05:53 PM UTC
- Resolved
- Feb 27, 2026, 05:53 PM UTC
- Duration
- —
Affected: Fin AI AgentInboxWeb MessengerMobile MessengerWebhooksREST APIPhoneCopilotTicketsOmnichannelHelp CenterApps and IntegrationsReportingKnowledge HubOutboundOther
Timeline · 2 updates
-
investigating Feb 27, 2026, 04:44 PM UTC
Status: Investigating We're receiving reports that there is an issue routing inbound phone calls. Our team is aware and investigating the issue. We’ll update you here as soon as we have more specific information. Affected components Phone (Partial outage) Webhooks (Operational) REST API (Operational) Fin AI Agent (Operational) Inbox (Operational) Copilot (Operational) Help Center (Operational) Outbound (Operational) Tickets (Operational) Omnichannel (Operational) Reporting (Operational) Other (Operational) Mobile Messenger (Operational) Apps and Integrations (Operational) Knowledge Hub (Operational) Web Messenger (Operational)
-
resolved Feb 27, 2026, 05:53 PM UTC
Status: Resolved The team has shipped a fix and all phone calls should be properly routed now. Affected components Webhooks (Operational) REST API (Operational) Help Center (Operational) Mobile Messenger (Operational) Copilot (Operational) Outbound (Operational) Other (Operational) Fin AI Agent (Operational) Inbox (Operational) Phone (Operational) Omnichannel (Operational) Apps and Integrations (Operational) Knowledge Hub (Operational) Web Messenger (Operational) Tickets (Operational) Reporting (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2026, 02:01 PM UTC
- Resolved
- Feb 27, 2026, 02:01 PM UTC
- Duration
- —
Affected: Fin AI Agent
Timeline · 3 updates
-
investigating Feb 27, 2026, 01:16 PM UTC
Status: Investigating We're seeing issues with Fin where it is escalating to support teams more than usual. Our team is aware and investigating the issue. We’ll update you here as soon as we have more specific information. Affected components Fin AI Agent (Degraded performance)
-
monitoring Feb 27, 2026, 01:38 PM 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 Feb 27, 2026, 02:01 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 Fin AI Agent (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2026, 01:16 PM UTC
- Resolved
- Feb 27, 2026, 02:01 PM UTC
- Duration
- 44m
Read the full incident report →
- Detected by Pingoru
- Feb 24, 2026, 07:51 PM UTC
- Resolved
- Feb 24, 2026, 07:51 PM UTC
- Duration
- —
Affected: OmnichannelOutboundOther
Timeline · 3 updates
-
identified Feb 24, 2026, 07:32 PM UTC
Status: Identified Intercom's outbound email provider is experiencing an outage, impacting workspaces hosted in Intercom's USA and Australia regions. All outbound emails including administrative emails such as sign-up verification and notifications are affected. We're monitoring the situation. Affected components Omnichannel (Partial outage) Outbound (Partial outage) Other (Partial outage)
-
monitoring Feb 24, 2026, 07:43 PM UTC
Status: Monitoring Things are looking better now and we're processing our backlogs. Affected components Omnichannel (Partial outage) Outbound (Partial outage) Other (Partial outage)
-
resolved Feb 24, 2026, 07:51 PM UTC
Status: Resolved Email sending was delayed between 18:53 UTC - 19:33 UTC. Email sending is back to normal. Affected components Omnichannel (Operational) Outbound (Operational) Other (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 24, 2026, 07:51 PM UTC
- Resolved
- Feb 24, 2026, 07:51 PM UTC
- Duration
- —
Affected: OmnichannelOutboundOther
Timeline · 3 updates
-
identified Feb 24, 2026, 07:32 PM UTC
Status: Identified Intercom's outbound email provider is experiencing an outage, impacting workspaces hosted in Intercom's USA and Australia regions. All outbound emails including administrative emails such as sign-up verification and notifications are affected. We're monitoring the situation. Affected components Omnichannel (Partial outage) Outbound (Partial outage) Other (Partial outage)
-
monitoring Feb 24, 2026, 07:43 PM UTC
Status: Monitoring Things are looking better now and we're processing our backlogs. Affected components Omnichannel (Partial outage) Outbound (Partial outage) Other (Partial outage)
-
resolved Feb 24, 2026, 07:51 PM UTC
Status: Resolved Email sending was delayed between 18:53 UTC - 19:33 UTC. Email sending is back to normal. Affected components Omnichannel (Operational) Outbound (Operational) Other (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 24, 2026, 07:32 PM UTC
- Resolved
- Feb 24, 2026, 07:51 PM UTC
- Duration
- 18m
Read the full incident report →
- Detected by Pingoru
- Feb 08, 2026, 03:51 PM UTC
- Resolved
- Feb 08, 2026, 03:51 PM UTC
- Duration
- —
Affected: Omnichannel
Timeline · 3 updates
-
investigating Feb 06, 2026, 05:43 PM UTC
Status: Investigating Customers who are using the WhatsApp channel are currently experiencing issues receiving media types. We have disabling the ability to send all media types until we resolve the issue. Our team is aware and investigating the issue. We’ll update you here as soon as we have more specific information. Affected components Omnichannel (Degraded performance)
-
monitoring Feb 08, 2026, 03:44 PM 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 Omnichannel (Degraded performance)
-
resolved Feb 08, 2026, 03:51 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 Omnichannel (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 08, 2026, 03:51 PM UTC
- Resolved
- Feb 08, 2026, 03:51 PM UTC
- Duration
- —
Affected: Omnichannel
Timeline · 3 updates
-
investigating Feb 06, 2026, 05:43 PM UTC
Status: Investigating Customers who are using the WhatsApp channel are currently experiencing issues receiving media types. We have disabling the ability to send all media types until we resolve the issue. Our team is aware and investigating the issue. We’ll update you here as soon as we have more specific information. Affected components Omnichannel (Degraded performance)
-
monitoring Feb 08, 2026, 03:44 PM 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 Omnichannel (Degraded performance)
-
resolved Feb 08, 2026, 03:51 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 Omnichannel (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 08, 2026, 03:51 PM UTC
- Resolved
- Feb 08, 2026, 03:51 PM UTC
- Duration
- —
Affected: Omnichannel
Timeline · 3 updates
-
investigating Feb 06, 2026, 05:43 PM UTC
Status: Investigating Customers who are using the WhatsApp channel are currently experiencing issues receiving media types. We have disabling the ability to send all media types until we resolve the issue. Our team is aware and investigating the issue. We’ll update you here as soon as we have more specific information. Affected components Omnichannel (Degraded performance)
-
monitoring Feb 08, 2026, 03:44 PM 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 Omnichannel (Degraded performance)
-
resolved Feb 08, 2026, 03:51 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 Omnichannel (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 06, 2026, 05:43 PM UTC
- Resolved
- Feb 08, 2026, 03:51 PM UTC
- Duration
- 1d 22h
Read the full incident report →
- Detected by Pingoru
- Jan 30, 2026, 05:53 PM UTC
- Resolved
- Jan 30, 2026, 05:53 PM UTC
- Duration
- —
Affected: Outbound
Timeline · 3 updates
-
investigating Jan 30, 2026, 04:22 PM UTC
Status: Investigating We are investigating reports of delayed and blocked sending of outbound email to Yahoo email addresses. We’ll update you here as soon as we have more specific information. Affected components Outbound (Degraded performance)
-
monitoring Jan 30, 2026, 05:39 PM 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 Outbound (Degraded performance)
-
resolved Jan 30, 2026, 05:53 PM UTC
Status: Resolved We've worked with Yahoo to fix a configuration issue on their side. 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 Outbound (Operational)
Read the full incident report →
- Detected by Pingoru
- Jan 30, 2026, 05:36 PM UTC
- Resolved
- Jan 30, 2026, 05:36 PM UTC
- Duration
- —
Affected: Omnichannel
Timeline · 2 updates
-
investigating Jan 30, 2026, 04:55 PM UTC
Status: Investigating We are investigating reports of connection issues for customers using Meta channels. We believe we are recovery mode and continuing to monitor. We’ll update you here as soon as we have more specific information. Affected components Omnichannel (Partial outage)
-
resolved Jan 30, 2026, 05:36 PM UTC
Status: Resolved On Friday 30th January between 15:12 GMT and 16:22 GMT customers using the WhatsApp channel in the US experienced connection issues with Intercom. We completed a standard key rotation and identified a key missing a permission that caused numbers to get disconnected. This caused the team to complete a revert which resolved the issue. This issue is now resolved, and all services are working as expected. Affected components Omnichannel (Operational)
Read the full incident report →