System Status
All Systems Operational

About This Site

This is Intercom's status page, where you can get updates on how our systems are doing. If there are interruptions to service, we will post a note here.

As always, if you are experiencing any issues with Intercom, don't hesitate to get in touch with us at team@intercom.io and we'll get back to you as soon as we can.

Intercom Messenger Operational
90 days ago
99.99 % uptime
Today
Web Messenger ? Operational
90 days ago
99.99 % uptime
Today
Mobile Messenger ? Operational
90 days ago
100.0 % uptime
Today
Intercom Web Application ? Operational
90 days ago
100.0 % uptime
Today
Intercom APIs ? Operational
90 days ago
100.0 % uptime
Today
Intercom Mobile APIs ? Operational
90 days ago
100.0 % uptime
Today
Intercom message delivery ? Operational
90 days ago
99.11 % uptime
Today
Small message delivery ? Operational
90 days ago
98.94 % uptime
Today
Medium message delivery ? Operational
90 days ago
98.94 % uptime
Today
Large message delivery ? Operational
90 days ago
98.94 % uptime
Today
Admin notifications ? Operational
90 days ago
99.63 % uptime
Today
Intercom Webhooks Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
had a major outage
had a partial outage
REST API response time
Fetching
Mobile API response time
Fetching
Javascript API response time
Fetching
Web Application response time
Fetching
Webhook Delivery Time
Fetching
Small Message Delivery Times ?
Fetching
Medium Message Delivery Times ?
Fetching
Large Message Delivery Times ?
Fetching
Javascript API uptime
Fetching
Web Application uptime
Fetching
REST API uptime
Fetching
Mobile API uptime
Fetching
Past Incidents
Jun 19, 2019
Completed - The scheduled maintenance has been completed.
Jun 19, 08:26 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 19, 07:00 UTC
Scheduled - Between 2019-06-19 0700 UTC and 2019-06-19 0830 UTC, Intercom will be unavailable to access due to some maintenance required on our core database services.

What is the impact?
Our main database cluster will be entirely down for a period of time. To facilitate a safe change, we will also be removing all web/API server capacity. This will impact all Intercom features, and they will not be accessible during the downtime.

How long will the downtime last?
Intercom will be fully unavailable for all customers during the maintenance window while we perform the change. Once the change is complete we will then start to scale back up our server fleets and start serving requests again. During this recovery time, Intercom will be unavailable to some but not all customers. Some but not all message delivery may be delayed.

What will the exact experience be for our customers during the change?
Team mates already in the Intercom app - will receive an Intercom error message in their browsers and will not be able to use the platform.
Team mates trying to load the Intercom app - will receive a generic 503 “service unavailable” message in their browser
End users on a website where the Intercom messenger is installed - will experience the messenger appearing, but the components in the messenger will not load and/or be available to interact with
Developers trying to use the API - will receive a 503 “service unavailable” error in their response
What will happen messages that are scheduled to send during this time?
They will be delayed for the duration of the downtime.

What will happen to e-mails that get sent in?
They will be queued up and processed/delivered once the platform is back up.
Jun 17, 12:36 UTC
Jun 18, 2019
Resolved - Between 2019-06-14 and 2019-06-17, customers would have experienced issues with Attachments in Intercom, in both in-app conversations, and emails. This was due to engineering work undertaken to prevent the reoccurrence of emails being sent via Intercom being flagged as "malicious" when sent to Gmail or GSuite hosted email addresses.

As part of the work performed, we now only allow download of the following filetypes from Intercom by default:
.pdf, .png, .jpg, .gif, .txt

For customers who require the use of additional filetypes, you can add custom filetypes to be supported on your Intercom Workspace. This is available to set by Intercom Teammates who have Full-Access permissions, and can be done here: https://app.intercom.io/a/apps/_/settings/attachment-settings.

File attachments that are sent via Email will now render the link for new email sent. There is one exception to this - if a new conversation is created using email, and that email contains an attachment that is not part of the receiving workspaces's whitelisted filetypes, notification emails sent as a result of this will not link to the file due to it not being whitelisted.

This incident is now resolved and all services are working as expected.
Jun 18, 16:44 UTC
Update - Here is an update on the current status of attachments in Intercom.

At the moment, we continue to block attachments from being downloaded via Intercom in certain scenarios.

In email - we are not rendering the link to attached files of any type, for all email sent via Intercom. This includes links sent into Intercom customer workspaces, as well as emails sent from Intercom customer workspaces.

In the Inbox product - we are allowing all files to be uploaded, but only files with the following extensions are available for download by default:
.pdf, .png, .jpg, .gif, .txt

However - for customers impacted by this restriction, you can add custom filetypes to be supported on your Intercom Workspace. This is available to set by Intercom Teammates who have Full-Access permissions, and can be done here: https://app.intercom.io/a/apps/_/settings/attachment-settings.

Whitelisted filetypes should be accessible straight away. If you have any trouble accessing files after you have whitelisted them, please get in touch with our Intercom Support team by using the Messenger while you're logged into Intercom. We have also created a new Help Center article here that explains this too - https://www.intercom.com/help/articles/3074152-unsupported-attachment-filetypes

In addition to this - we have shipped a new error page for users affected by downloads being blocked which explains that the file is blocked due to being an unsupported file type.
Jun 17, 13:00 UTC
Update - As an update to our efforts to mitigate this issue, we are now allowing only specific filetypes to be accessible as attachments:

- .pdf, .png, .jpg, .gif, .txt

While attachments will not be accessible via email, customers will see attachments available in the Inbox and only the filetypes listed above will be accessible by default.

For customers who might still see these filetypes being blocked from download specifically by the Google Chrome browser, using another browser should allow these files to be downloaded.

We have also added a new settings page which will allow you to add additional filetypes to be allowed for your workspace. You can find that settings page here: https://app.intercom.io/a/apps/_/settings/attachment-settings
Jun 14, 18:43 UTC
Update - As an update to our efforts to mitigate this issue, we have blocked downloads of all attachment types apart from PDFs, Images and Videos. Customers will see attachments available in the Inbox but those files will be inaccessible.

For customers who might still see PDFs, Images or Videos being blocked from download specifically by the Google Chrome browser, using another browser should allow these files to be downloaded.

This is a temporary restriction in place to aid our engineering efforts to solve the root cause of this issue.
Jun 14, 10:23 UTC
Update - We are continuing to monitor for any further issues.
Jun 14, 00:23 UTC
Update - We are continuing to work with Google services to improve and maintain our sending quality. Due to this ongoing work, we have temporarily prevented direct access to attachments from emails sent from within Intercom workspaces.

Any workflows that rely on directly linked attachments in emails coming from Intercom will be temporarily disrupted.

The list of filetypes that will be impacted by this are:
- doc, xslx, docm, docx, xlsm, exe
- html, htm, php, js
- zip, gz, 7z, rar, z, zls, tar
- arj, iso, ace, apk
- IMG, img, uue, cab
- gz, jar, vb, vbe, bat, hta, py, sfx
- msi, msp, com, cmd, jse, ps1, ps1xml
- ps2, ps2xml, psc1, psc2, lnk, inf, scr, sh


Attachments will still be accessible while in the Intercom web application as expected. Google Chrome may temporarily prevent downloading certain filetypes.
Jun 13, 23:26 UTC
Monitoring - We are working with Gmail and GSuite services to improve and maintain our sending quality.

Workflows that rely on receiving inbound email attachments coming into Intercom will be temporarily disrupted.
Jun 13, 18:39 UTC
Jun 16, 2019

No incidents reported.

Jun 15, 2019

No incidents reported.

Jun 12, 2019
Completed - Our Upstream Email Provider, Sparkpost, has completed their maintenance, and all services are working as expected. For more information about Sparkpost's maintenance, please see their Status Page update at https://status.sparkpost.com/incidents/ylybhn2jb9j4
Jun 12, 15:31 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 12, 13:00 UTC
Scheduled - Between 2019-06-12 1300 UTC and 2019-06-12 1700 UTC, one of our upstream providers, Sparkpost, will be performing maintenance on their infrastructure. Sparkpost's maintenance notification is available here - https://status.sparkpost.com/incidents/ylybhn2jb9j4

New Intercom workspaces created during this time will experience delays in sending verification emails, invites to teammates, or emails to customers through Intercom. Once Sparkpost's maintenance is complete, we will retry to send all queued email content.

Customers with workspaces created before this maintenance will be unaffected.
Jun 12, 13:00 UTC
Jun 11, 2019

No incidents reported.

Jun 10, 2019
Resolved - Our Engineering teams have now re-enabled the download of attachments created through emails sent to Intercom workspaces. Customers might find that links to attachments in older emails will no longer download directly, but these attachments will still be available through accessing the conversation in Intercom. This issue is now resolved and services are working as expected.
Jun 10, 12:35 UTC
Monitoring - Between approximately 2019-06-09 0000 UTC and 2019-06-10 0230 UTC, emails sent to Gmail or GSuite email addresses via Intercom would have appeared with a banner in GMail indicating that the email contained "dangerous" content. We have worked with Google to resolve the cause of this, and this banner is no longer appearing on emails sent via Intercom.

While we continue to work to resolve the root cause, we have temporarily prevented the download of attachments that were created through emails coming into Intercom workspaces which match any of the filetypes in the list below.

Attachment filetypes that are temporarily prevented include:
- doc, xslx, docm, docx, xlsm, exe
- html, htm, php, js
- zip, gz, 7z, rar, z, zls, tar
- arj, iso, ace, apk
- IMG, img, uue, cab

Workflows that rely on receiving inbound email attachments coming into Intercom will be temporarily disrupted.
Jun 10, 09:29 UTC
Investigating - We are investigating a reoccurrence of email delivery issues related to customer files sent via Intercom being flagged as malicious by Google.

Known Impacted Email Services include:
- Emails sent via Intercom to GSuite or Gmail addresses.

Email Services Not Impacted:
- Transactional emails sent from Intercom itself
- Conversation summaries from Inbox conversations
- Emails sent via Messages to non Gmail or GSuite addresses
Jun 9, 09:36 UTC
Resolved - Between 2019-06-10 10 25 UTC and 2019-06-10 10:55 UTC our API was down due to a deployment failure, which in turn affected apps and webhooks. The API, apps and webhooks are back fully operational with certain apps not updating in real time while we process the backlog.
Jun 10, 12:04 UTC
Monitoring - We have identified the cause of this issue to be a code change and have successfully rolled back at approximately 2019-06-10 11 00 UTC. The API is now back up and operational but customers will still experience some delays with webhooks. We will continue to monitor until we are fully operational again.
Jun 10, 11:22 UTC
Investigating - We're currently investigating an issue with our API, starting at approximately 2019-06-10 10 25 UTC. Users will experience issues with Webhooks and Apps during this time
Jun 10, 10:55 UTC
Jun 8, 2019

No incidents reported.

Jun 7, 2019

No incidents reported.

Jun 6, 2019

No incidents reported.

Jun 5, 2019

No incidents reported.