HubSpot: HubSpot notifications triggered from 3:52 to 4:05 PM GMT today were delayed in sending
Timeline of updates
- resolved
HubSpot notifications triggered from 3:52 to 4:05 PM GMT today were delayed in sending as a result of a database migration issue that has now been resolved. There was no data lost during this period and all notifications delayed in sending during this time period have now been fully processed. A small amount of these notifications may have been sent more than once.
From HubSpot’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.hubspot.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by HubSpot, started 2018-04-05 17:18 UTC, resolved after 0 min, 1 update(s).
- Title
- HubSpot notifications triggered from 3:52 to 4:05 PM GMT today were delayed in sending
- Vendor
- HubSpot
- Date
- URL
- https://rewindex.com/company/hubspot/incidents/n87yzx344jpc
HubSpot profileRecent HubSpot incidentsAll outages on April 5, 2018HubSpot in April 2018MarkdownJSON