- Detected by Pingoru
- Jun 12, 2026, 07:13 PM UTC
- Resolved
- Jun 12, 2026, 07:13 PM UTC
- Duration
- —
Affected: OmnichannelOutbound
Timeline · 2 updates
-
identified Jun 12, 2026, 02:30 PM UTC
Status: Identified There are currently delays in sending and receiving messages to/from Meta properties (Facebook, Instagram, WhatsApp) due to issues on their side. We're monitoring the situation. Affected components Omnichannel (Degraded performance) Outbound (Degraded performance)
-
resolved Jun 12, 2026, 07:13 PM UTC
Status: Resolved Meta services are back up and running, and we’ve caught up on queued messages. Affected components Omnichannel (Operational) Outbound (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2026, 07:13 PM UTC
- Resolved
- Jun 12, 2026, 07:13 PM UTC
- Duration
- —
Affected: OmnichannelOutbound
Timeline · 2 updates
-
identified Jun 12, 2026, 02:30 PM UTC
Status: Identified There are currently delays in sending and receiving messages to/from Meta properties (Facebook, Instagram, WhatsApp) due to issues on their side. We're monitoring the situation. Affected components Omnichannel (Degraded performance) Outbound (Degraded performance)
-
resolved Jun 12, 2026, 07:13 PM UTC
Status: Resolved Meta services are back up and running, and we’ve caught up on queued messages. Affected components Omnichannel (Operational) Outbound (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2026, 07:13 PM UTC
- Resolved
- Jun 12, 2026, 07:13 PM UTC
- Duration
- —
Affected: OmnichannelOutbound
Timeline · 2 updates
-
identified Jun 12, 2026, 02:30 PM UTC
Status: Identified There are currently delays in sending and receiving messages to/from Meta properties (Facebook, Instagram, WhatsApp) due to issues on their side. We're monitoring the situation. Affected components Omnichannel (Degraded performance) Outbound (Degraded performance)
-
resolved Jun 12, 2026, 07:13 PM UTC
Status: Resolved Meta services are back up and running, and we’ve caught up on queued messages. Affected components Omnichannel (Operational) Outbound (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 11, 2026, 10:33 AM UTC
- Resolved
- Jun 11, 2026, 10:33 AM UTC
- Duration
- —
Affected: Mobile Messenger
Timeline · 2 updates
-
identified Jun 11, 2026, 09:54 AM UTC
Status: Identified We are investing a high rate of errors in the mobile SDK endpoints and mobile push functionality in the EU and Australian hosting regions. Affected components Mobile Messenger (Partial outage)
-
resolved Jun 11, 2026, 10:33 AM UTC
Status: Resolved For EU customers between 09:34 - 10:18UTC, and AU customers between 09:36 - 10:06UTC Mobile SDK endpoints and mobile push were impaired. This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to [email protected]: mailto:[email protected] if you have any further questions or if you’re still seeing any unexpected behaviour Affected components Mobile Messenger (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 11, 2026, 10:33 AM UTC
- Resolved
- Jun 11, 2026, 10:33 AM UTC
- Duration
- —
Affected: Mobile Messenger
Timeline · 2 updates
-
identified Jun 11, 2026, 09:54 AM UTC
Status: Identified We are investing a high rate of errors in the mobile SDK endpoints and mobile push functionality in the EU and Australian hosting regions. Affected components Mobile Messenger (Partial outage)
-
resolved Jun 11, 2026, 10:33 AM UTC
Status: Resolved For EU customers between 09:34 - 10:18UTC, and AU customers between 09:36 - 10:06UTC Mobile SDK endpoints and mobile push were impaired. This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to [email protected]: mailto:[email protected] if you have any further questions or if you’re still seeing any unexpected behaviour Affected components Mobile Messenger (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 04:15 PM UTC
- Resolved
- Jun 10, 2026, 04:15 PM UTC
- Duration
- —
Affected: Inbox
Timeline · 2 updates
-
monitoring Jun 10, 2026, 01:19 PM UTC
Status: Monitoring 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. Affected components Inbox (Degraded performance)
-
resolved Jun 10, 2026, 04:15 PM UTC
Status: Resolved 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. Affected components Inbox (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 04:15 PM UTC
- Resolved
- Jun 10, 2026, 04:15 PM UTC
- Duration
- —
Affected: Inbox
Timeline · 2 updates
-
monitoring Jun 10, 2026, 01:19 PM UTC
Status: Monitoring 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. Affected components Inbox (Degraded performance)
-
resolved Jun 10, 2026, 04:15 PM UTC
Status: Resolved 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. Affected components Inbox (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 04:15 PM UTC
- Resolved
- Jun 10, 2026, 04:15 PM UTC
- Duration
- —
Affected: Inbox
Timeline · 2 updates
-
monitoring Jun 10, 2026, 01:19 PM UTC
Status: Monitoring 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. Affected components Inbox (Degraded performance)
-
resolved Jun 10, 2026, 04:15 PM UTC
Status: Resolved 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. Affected components Inbox (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 08, 2026, 11:53 AM UTC
- Resolved
- Jun 08, 2026, 11:53 AM UTC
- Duration
- —
Affected: Mobile MessengerREST API
Timeline · 10 updates
Read the full incident report →
- Detected by Pingoru
- Jun 08, 2026, 11:53 AM UTC
- Resolved
- Jun 08, 2026, 11:53 AM UTC
- Duration
- —
Affected: Mobile MessengerREST API
Timeline · 10 updates
Read the full incident report →
- Detected by Pingoru
- Jun 08, 2026, 11:53 AM UTC
- Resolved
- Jun 08, 2026, 11:53 AM UTC
- Duration
- —
Affected: Mobile MessengerREST API
Timeline · 10 updates
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 01:23 PM UTC
- Resolved
- Jun 01, 2026, 01:23 PM UTC
- Duration
- —
Affected: Fin AI AgentInbox
Timeline · 5 updates
-
investigating Jun 01, 2026, 11:03 AM UTC
Status: Investigating 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. Affected components Fin AI Agent (Degraded performance)
-
identified Jun 01, 2026, 11:31 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) Inbox (Degraded performance)
-
monitoring Jun 01, 2026, 11:58 AM UTC
Status: Monitoring 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. Affected components Fin AI Agent (Degraded performance) Inbox (Degraded performance)
-
monitoring Jun 01, 2026, 12:43 PM UTC
Status: Monitoring 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. Affected components Fin AI Agent (Degraded performance) Inbox (Degraded performance)
-
resolved Jun 01, 2026, 01:23 PM UTC
Status: Resolved 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 Affected components Fin AI Agent (Operational) Inbox (Operational)
Read the full incident report →
- Detected by Pingoru
- May 21, 2026, 07:25 PM UTC
- Resolved
- May 21, 2026, 07:25 PM UTC
- Duration
- —
Affected: Reporting
Timeline · 2 updates
-
identified May 21, 2026, 11:09 AM UTC
Status: Identified 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. Affected components Reporting (Degraded performance)
-
resolved May 21, 2026, 07:25 PM UTC
Status: Resolved The issue is resolved, reporting data is up to date. Affected components Reporting (Operational)
Read the full incident report →
- Detected by Pingoru
- May 20, 2026, 10:17 AM UTC
- Resolved
- May 20, 2026, 10:17 AM UTC
- Duration
- —
Affected: Inbox
Timeline · 2 updates
-
monitoring May 20, 2026, 10:16 AM UTC
Status: Monitoring Between 09:08 - 09:28 UTC, images were not loading in the Intercom inbox. Apologies for the disruption. Affected components Inbox (Degraded performance)
-
resolved May 20, 2026, 10:17 AM UTC
Status: Resolved The issue is resolved. Affected components Inbox (Operational)
Read the full incident report →
- Detected by Pingoru
- May 20, 2026, 10:17 AM UTC
- Resolved
- May 20, 2026, 10:17 AM UTC
- Duration
- —
Affected: Inbox
Timeline · 2 updates
-
monitoring May 20, 2026, 10:16 AM UTC
Status: Monitoring Between 09:08 - 09:28 UTC, images were not loading in the Intercom inbox. Apologies for the disruption. Affected components Inbox (Degraded performance)
-
resolved May 20, 2026, 10:17 AM UTC
Status: Resolved The issue is resolved. Affected components Inbox (Operational)
Read the full incident report →
- Detected by Pingoru
- May 20, 2026, 10:17 AM UTC
- Resolved
- May 20, 2026, 10:17 AM UTC
- Duration
- —
Affected: Inbox
Timeline · 2 updates
-
monitoring May 20, 2026, 10:16 AM UTC
Status: Monitoring Between 09:08 - 09:28 UTC, images were not loading in the Intercom inbox. Apologies for the disruption. Affected components Inbox (Degraded performance)
-
resolved May 20, 2026, 10:17 AM UTC
Status: Resolved The issue is resolved. Affected components Inbox (Operational)
Read the full incident report →
- 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 →
