Intercom: Fin intermittent failures responding to first conversation messages
Affected components: 01J0R8NT6YMG2CAKJ20H40RP6W
Timeline of updates
- investigating
We're seeing issues with Fin Agent responding to the first message of new inbound Conversations. Our team is aware and investigating the issue. We’ll update you here as soon as we have more specific information.
- monitoring
We have implemented a fix and are monitoring for recovery. We’ll let you know when we are confident in our recovery.
- resolved
This issue should now be resolved and all services are restored to normal functionality.
Please don’t hesitate to reach out to team@fin.: mailto:team@fin.aiai if you have any further questions or if you’re still seeing any unexpected behaviour
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
0b92496c06e2343e…
Impact, status and times are the vendor’s own, as last archived. View on www.finstatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Intercom, started 2026-09-04 10:00 UTC, resolved after 5.9 h, 3 update(s).
- Title
- Fin intermittent failures responding to first conversation messages
- Vendor
- Intercom
- Date
- URL
- https://rewindex.com/company/intercom/incidents/01M1PFX639M0HRXYGFZG9E6YW0
Intercom profileRecent Intercom incidentsAll outages on September 4, 2026Intercom in September 2026MarkdownJSON