Vendor reports: partial outageResolved · vendor status “resolved”Official status API
Connection attempts failing for multiple Basic tenants in GCP South America (southamerica-east1).
Reported by CockroachDB Cloud · Databases · source last read 3 min ago
- Vendor start
- Sep 17, 2026, 19:08 UTC
- Vendor's clock
- Resolved
- Sep 17, 2026, 20:39 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- 1 h 31 min
- From vendor start and resolution
Summary
Built from the facts below, no AI
Potential impact, not a confirmed outage of your systems.
What the vendor confirmed
Affected products and regions
What is unknown
- Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.
Last update in these facts: 2026-09-17 20:39 UTC · summary s1, evidence 50a948dd9b39073c
Evidence (7)
- E1CockroachDB Cloud reports partial outage. (vendor) source (opens in a new tab)
- E2Vendor title: "Connection attempts failing for multiple Basic tenants in GCP South America (southamerica-east1).". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2026-09-17 19:08 UTC. (vendor) source (opens in a new tab)
- E5Regions written in the title (inferred): southamerica-east1. (Statuswall) source (opens in a new tab)
- E6Components the vendor attached: CockroachDB Basic/Standard. (vendor) source (opens in a new tab)
- E7Vendor-reported resolution: 2026-09-17 20:39 UTC. (vendor) source (opens in a new tab)
Affected scope
southamerica-east1
Components: CockroachDB Basic/Standard
Read from region codes written in the incident title, so treat it as inferred.
Potential relevance
CockroachDB Cloud is not in your stack. Follow it to see whether reports like this fall inside the regions you use.
Timeline
Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.
- Sep 17, 2026, 19:08 UTCVendor-reported startVendor time
- Sep 17, 2026, 20:39 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.