Intercom's Fin Procedures feature ran slow for 24 minutes on 30 October 2026. Intercom flagged the problem itself and the fault sat on their side, not yours.
Started
18:06 UTC
Duration
Lasted 24m
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 opened an incident at 18:06 UTC, saying it was investigating slowness with Fin Procedures. At 18:22 UTC it posted that Fin Procedures was working as normal again, closing the incident after 24 minutes. That is the entire record: two updates, no further detail on what caused the slowdown, and no component list published alongside the incident. No user reports were filed during the window, so there is nothing from your side to cross-check against Intercom's own account. Intercom's status page does not say why Fin Procedures slowed down, only that it did and then it didn't. One filing from the vendor is what you get here, and it is thin: a start, a resolution, no cause. Over the past 90 days Intercom has logged 9 incidents with a median duration of 27 minutes, so this one came in a touch faster than typical but well within the normal range for them. Across all time Intercom has filed 355 incidents, averaging 4.6 a month, which tells you Fin Procedures and other components go through incidents like this fairly often. Nothing here marks this one out as unusual except that it resolved on the quicker side.
Learning
UptimeRobot's own 30 day data shows 3 incidents against Intercom, all resolved, with a median duration of 24m, a figure close to what played out here. That consistency matters because a feature like Fin Procedures can slow down or fail inside Intercom's infrastructure without your own uptime checks against your product ever showing red, since your checks are watching your endpoints, not Intercom's internal processing. If your product calls into Fin Procedures and that call hangs or errors, the first sign you get is usually a support ticket or a slow page, not an alert, because nothing on your side has actually gone down. That is the general shape of this kind of failure: the provider's internal feature degrades while your service keeps answering fine. Watching your own endpoints tells you your half is up. It does not tell you whether a dependency like Fin Procedures inside Intercom is the thing quietly slowing your users down. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.