Operational HubSpot status
hubspot.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
HubSpot looks fine itself, but Amazon Web Services, a provider it may run on (inferred), reports major outage. Watch for knock-on effects.
confidence: low Vendor: operational · users: normal · routing: no data · upstream providers: major.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) Amazon Web Services: Major outage
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Integrations
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 57 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “The Salesforce integration is unavailable for some customers”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
- Amazon Web Services reports an issue. HubSpot may depend on it (inferred from public sources). Coincidence, not causation. evidence confidence: low
What we don't know: what is happening inside HubSpot's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.
Coincidence, not causation: signals that overlap in time are shown side by side, not as proof of cause.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data · upstream providers: major. Vendor status and outside signals roughly agree.
Who depends on whom
HubSpot may run on Google Cloud, Amazon Web Services (inferred). We don't map other services that depend on HubSpot. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on HubSpot or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with HubSpot. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
The Salesforce integration is unavailable for some customers
none resolved · started · resolved
6 updates
- identified
We have identified an issue with our Salesforce integration. Some customers may find that their integration has been unexpectedly disconnected and is temporarily unavailable in the App Marketplace. We're actively investigating the cause and working to restore full functionality.
- identified
We have identified the issue with our Salesforce integration causing it to be unavailable for some customers since 9:26AM EST today. We're addressing the cause of this issue and expect all data to refresh once back online. We will be back with an update within 1 hour.
- identified
We have identified the issue with our Salesforce integration. We are continuing to work on addressing the cause and restore full functionality. We will be back with an update within 30 minutes.
- identified
We have identified the issue with our Salesforce integration. We are continuing to work on restoring full functionality.
- identified
We have identified the issue with our Salesforce integration. We continue working to restore full functionality. We will be back with an update within an hour. The information on this page reflects our understanding of the incident and impact at the time of the update.
- resolved
Between 09:26 AM EDT (UTC -04:00) and 05:21 PM EDT, some customers in North America, Europe, the Asian Pacific experienced issues with our Salesforce integration. This was caused by a bad system configuration change. As of 05:21 PM EDT, our systems are working properly and the incident has been fully resolved. HubSpot conducts a thorough review after each incident to understand the cause and prevent it from happening again. Learn more about HubSpot's commitment to reliability at www.HubSpot.com/reliability. The information on this page reflects our understanding of the incident and impact at the time of the update.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.