If you run on Salesforce GovCloud, you may have lost access starting at 22:06 UTC. Salesforce says the fault sits with a third-party infrastructure provider handling .mil network connectivity, not with its own stack, and the incident is still open as of its last update.
Started
22:06 UTC
Duration
Ongoing
Source
IsDown
Next time
Salesforce is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: USA9402, USA9404S, USA9406S
What happened?
Salesforce opened this incident at 22:06 UTC on 1 October 2026, flagging GovCloud performance degradation across three components: USA9402, USA9404S and USA9406S. At 22:19 UTC it posted its only update so far, saying it is aware of an issue affecting .mil network connectivity to some Salesforce GovCloud environments. Salesforce's wording is specific: customers on affected network paths may be unable to access Salesforce services, or may see intermittent connectivity instead of a hard outage. The company says it has engaged the global infrastructure provider that serves a subset of government agencies and is monitoring for recovery. No further update has been filed, so the incident remains open with that single statement as the only account on record. No user reports were filed during this window, which fits an incident scoped to .mil network paths rather than the general Salesforce user base. There is no duration yet because Salesforce has not marked this resolved. Over the past 90 days Salesforce has logged 128 incidents with a median duration of 2 hours 31 minutes, so there is a track record to compare against, but nothing says this one will match it. Across all time Salesforce has recorded 2,457 incidents, which gives you a sense of how routine incident filings are for a platform this size, though that number says nothing about severity.
Learning
This incident sits in the network path between .mil-connected agencies and Salesforce's GovCloud infrastructure, a layer that a routine check against your own endpoints would never see, because your product and your monitoring can both be healthy while the connection between a specific government network and Salesforce's provider is broken. Over the last 30 days, external checks against Salesforce logged 39 incidents with 36 resolved and a median duration of 3 hours 12 minutes, numbers that come from watching Salesforce's side directly rather than waiting for your own users to complain. That is the general shape of this kind of failure: a third party in the chain degrades, access drops for a defined slice of traffic, and nothing in your own stack shows a fault because there isn't one there. Salesforce's own status page is the only account of what happened and why, and one filing from the vendor carries real weight but is not independent confirmation. If your team only watches your own application, an outage like this looks like nothing until support tickets start arriving. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
