Incoming emails in HubSpot are no longer delayed and fully operational. We’ve identified and addressed the cause of the issue and the incident has now been fully resolved.
Jan 18, 06:46 EST
Incoming emails in HubSpot are continuing to experience delays of up to 2 hours, impacting both Conversations and email replies logged to records. All inboxes that we are able to reconnect to have been successfully reconnected at this time.
Jan 17, 22:00 EST
Incoming emails in HubSpot are continuing to experience delays of up to 1.5 hours, impacting both Conversations and email replies logged to records. There are also a small number of inboxes that we are unable to re-connect - if your inbox is still disconnected, reconnecting it manually will fix the issue.
Jan 17, 20:13 EST
Some incoming emails in Conversations are delayed. Sequences scheduled to send during this period were unenrolled and will need to be re-enrolled.
You also may have received an email asking you to reconnect your inbox as a result of this issue. You do not need to take any further action as your inbox will be automatically reconnected.
Jan 17, 18:15 EST
We've identified and resolved the root cause of this outage with inbox and calendar connections. Inboxes and calendars connected to the CRM should now be reconnected, and we are working to resolve inboxes connected to Conversations. To manually fix your inbox with Conversations, please reconnect your inbox in your Conversations inbox settings.
Jan 17, 17:28 EST
We have identified the cause of this outage and are working to resolve this for all users. In the meanwhile, please reconnect your inbox and calendar by going to Settings in the top navigation, into Integrations, then Email integrations.
Jan 17, 17:14 EST
Starting at 3:22PM ET January 17 2019, some connections to Gmail and O365 inboxes and calendars are temporarily unavailable. This affects sequences sending, sending email from the Contact, Company and Deal records and Conversations, and Meetings. We are currently investigating and will update this incident when we know more detail.
Jan 17, 16:19 EST