On this page
Intercom powers the live chat, support inbox, and onboarding flows for thousands of SaaS products. When it goes down — the chat widget disappears from your site, support agents lose access to their inbox, and automated messages stop firing. Worse: your customers see a broken experience while your team scrambles to figure out whether it's a configuration problem or a full outage.
Here's how to check Intercom's status right now, understand exactly what's broken, and ensure you're always the first to know.
Is Intercom Down Right Now?
Check these sources in order:
- Statusfield — Intercom status: review the latest recorded status, available components and incident history.
- Twitter/X — search
Intercom downsorted by Latest. Customers and support teams report broken chat widgets within minutes of an outage. - Downdetector — aggregates user reports; useful for confirmation, but no component detail.
What Actually Breaks During an Intercom Outage
Intercom is a distributed platform. A degradation in one component doesn't always mean everything is offline — knowing which piece is broken lets you react faster and communicate clearly with your team.
| Component | What it does | Impact when down |
|---|---|---|
| Messenger widget | The chat bubble on your website or app | Widget fails to load; customers can't initiate conversations |
| Inbox | Agent workspace for managing support conversations | Support team can't reply; conversations queue with no visibility |
| Outbound Messaging | Automated in-app messages, push, and email campaigns | Onboarding sequences, product tours, and drip campaigns stop firing |
| Help Center | Hosted self-service article base | Help articles become inaccessible; support deflection breaks |
| Conversations API | Programmatic access to conversations, contacts, events | Custom integrations, CRM syncs, and automations fail |
| Notifications | Email and mobile push notifications for new conversations | Agents miss new conversations; response times increase |
| Identity verification | Secure user identity (HMAC-based) for Messenger | Verified users can't be identified; Messenger may be blocked |
| Bots & Workflows | Resolution Bot, Custom Bots, automated routing rules | Bot-first support flows break; conversations route incorrectly |
| Product Tours | Interactive in-app onboarding flows | New user onboarding steps don't trigger |
Intercom Error Symptoms and What They Mean
| What you see | What it usually means |
|---|---|
| Chat widget spinner loops or doesn't appear | Messenger is down or blocked — check Statusfield |
"Failed to fetch" in browser console on widget.intercom.io | CDN or Messenger delivery degraded; may resolve in minutes |
| Inbox shows "Something went wrong" | Inbox API or backend degraded; agents cannot load conversations |
| Conversations load but replies won't send | Conversation write API is degraded; reads may work while writes fail |
| Automated messages not sending on schedule | Outbound messaging queue is backed up or stopped |
| Help Center returns 503 | Help Center hosting degraded; consider adding a fallback link in your footer |
| Identity verification users getting "not verified" | HMAC verification service degraded; may need to temporarily disable identity verification |
| Webhook events stop arriving | Webhook delivery is lagging or paused — events will replay once service recovers |
Intercom's Reliability Track Record
The platform typically maintains above 99.9% uptime for its core Messenger and Inbox components, but incidents do occur — particularly around Outbound Messaging and Workflow automation during periods of high load.
Notable patterns:
- Messenger CDN slowdowns — usually resolve within 30 minutes; widget loads slowly before failing completely.
- Inbox degradation during high-volume events — product launches or marketing campaigns can spike inbound volume and cause processing delays.
- API rate limit cascades — integrations that hit rate limits during an incident can trigger cascading failures in CRM sync workflows.
The component breakdown above is detailed enough to tell you which part of the product is affected — always check Statusfield before assuming a full outage.
How to Stay Ahead of Intercom Outages
When Intercom goes down, you need to know within seconds — not after a customer tweets at you.
Statusfield monitors Intercom continuously and delivers alerts to Slack, Discord, email, or webhook when a degradation is detected. Eligible new accounts can start a free trial — no credit card required. See current plans for monitor limits and included notification channels.
→ Monitor Intercom on Statusfield Eligible first-time customers can start a free trial. Continued monitoring requires a paid plan.
FAQ
Why is my Intercom chat widget not loading?
The most likely causes are: (1) Intercom Messenger is experiencing an outage — check Statusfield; (2) a Content Security Policy (CSP) on your site is blocking widget.intercom.io; (3) an ad blocker or browser extension is blocking the Intercom script. Open your browser's developer console and look for network errors on widget.intercom.io to narrow it down.
Is Intercom down for everyone or just me?
Check Statusfield for known incidents. If it shows operational, try loading the Intercom Messenger from a different network or browser — a local firewall, VPN, or ISP block can cause symptoms that look like a global outage.
How long do Intercom outages typically last?
Most Intercom Messenger incidents resolve within 15–60 minutes. Deeper backend degradations affecting Inbox or Outbound Messaging can last 1–3 hours. Major incidents are rare — monitor via Statusfield for incident history.
What should I do if Intercom is down during a critical product launch?
Have a fallback plan: a static "Contact us at support@yourdomain.com" banner you can deploy in minutes, a Statusfield alert connected to your engineering Slack channel, and a brief customer-facing status page of your own (even a simple hosted page works). The cost of a 30-minute support blackout during a launch is high — proactive monitoring is the only reliable defense.
Will Intercom replay missed webhook events after an outage?
Yes — Intercom retries failed webhook deliveries for up to 24 hours. However, the retry schedule uses exponential backoff, so time-sensitive integrations (like CRM contact creation) may experience delays of several hours. Monitor your webhook delivery logs in the Intercom dashboard after any incident.
Keep your vendors in view.
Choose from 7,000+ services, follow the components you use, and configure alerts for your team.
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.