Intercom's Inbox had trouble processing Bulk Actions for 27 minutes on 5 October 2026. Intercom's own status page flagged the delay, and the fault sat on their side, not yours.
Started
20:06 UTC
Duration
Lasted 27m
Source
IsDown
Next time
Intercom is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
What happened?
Intercom logged one incident on 5 October 2026, starting at 20:06 UTC and lasting 27 minutes. The title Intercom gave it was "Delays in processin Bulk Actions in the Inbox", which points to a specific feature, the Inbox's Bulk Actions tool, rather than the whole platform. Intercom filed a single update at 20:06 UTC: "We're seeing delays with processing of Bulk Actions. Our team is aware and investigating the issue. We'll update you here as soon as we have more specific information." No further update was logged, and no resolution message was published on the record we have, so that one filing carries the entire account of what happened. No components were listed as affected in the incident record. No user reports came in during the window, which for a delay confined to one bulk tool inside the Inbox is plausible, since it would only be visible to someone actively running bulk operations at that moment. Intercom has logged 8 incidents in the past 90 days with a median duration of 31 minutes, so this one came in slightly under that median. Across all time Intercom has logged 353 incidents, averaging 4.6 a month. This is a pattern of short, narrow incidents rather than one unusual event.
Learning
UptimeRobot's own 30 day checks on Intercom US show 3 incidents, all resolved, with a median duration of 27 minutes, matching almost exactly what happened here. That overlap tells you something useful: a delay confined to processing Bulk Actions inside the Inbox is a backend queueing problem, not a reachability problem, so an external uptime check hitting Intercom's endpoint can read green the whole time while a specific feature inside the product stalls. Watching your own integration or app for errors would not have caught this either, because the delay sits entirely inside Intercom's processing pipeline, upstream of anything your product controls. This is the general shape to watch for with Intercom: short, feature-scoped slowdowns that come and go inside 30 minutes, logged by Intercom itself rather than surfaced by broad outage symptoms. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
