Google Cloud (Vertex AI) status — and how to poll it yourself
Snapshot: Nov 2, 2026 7:20 AM ET · Statuses shown are build-time snapshots — they refresh on each site rebuild. Live auto-refresh ships post-launch.
At this snapshot, 9 of the 9 providers on our status board reported fully operational. Here is where Google Cloud (Vertex AI) stood, and how to get the same answer from its status API without a browser.
| Status page | https://status.cloud.google.com |
| Snapshot status | Operational 0 ongoing incidents in feed; 0 affecting Vertex/AI products (as of Nov 2, 2026 7:20 AM ET) |
| Components | no component feed (incident list only) |
| Status API format | gcp-incidents |
| JSON endpoint | https://status.cloud.google.com/incidents.json |
| Verification | verified — live fetch on 2026-11-02 |
Polling Google Cloud (Vertex AI)'s status programmatically
Google Cloud public incidents feed. GET /incidents.json returns an incident list (no per-component feed) — filter entries whose affected products include Vertex AI.
curl -s https://status.cloud.google.com/incidents.jsonEverything above was verified against the live endpoint on 2026-11-02 — nothing is inferred from platform defaults. If the endpoint moved, tell us.
Model retirements — Google Cloud (Vertex AI)
Google Vertex AI accounts for 31 of the 129 announced retirements in our deprecations table: 5 dated retirements still ahead as of 2026-11-02, 21 already past. 5 more rows carry hedged wording (e.g. “May 19, 2027 or later”) kept verbatim from the provider's docs. Every row cites the provider's own deprecations page.
| Next to retire | Date | Replacement |
|---|---|---|
gemini-live-2.5-flash-native-audio | 2026-12-13 | — |
text-embedding-005 | 2027-04-01 | — |
text-embedding-004 | 2027-04-01 | — |
Full table: all 129 rows, filterable, with CSV/JSON download →