Gemini WS · trade degradation, 2h 07m on 18 NOV 2026
Gemini WS · trade — 6.7% of windows stalled over the last five minutes (stalled) — from every region. up24 opened this incident from its own measurements of Gemini's public API on 18 NOV 2026 05:11 UTC. It lasted 2h 07m and ended 18 NOV 2026 07:18 UTC, when the component started answering again.
WHAT HAPPENED
- Gemini published its own notice.
- Gemini marked its notice resolved.
- up24 opened the incident at degraded, stalled.
- The component started answering again. up24 dates the incident from this moment, not from when its clearing rule finished.
HOW IT FAILED
Over the window, 421 of 6,894 ten-second windows failed: stalled ×418, conn ×3.
A stream has no latency of its own — a feed either delivers or it does not — so this is Gemini's REST endpoints over the same window, per minute, as the median across them, measured from Lauterbourg, FR. It answers the question the timeline cannot: whether the rest of the exchange was fine while this feed was down.
DID GEMINI SAY SO?
Gemini published a notice within six hours of this incident, on 18 NOV 2026 00:56 UTC: “Account Service Unavailable”. It is paired by time alone, within six hours — nothing checks that it is about this fault, so it is linked to be judged rather than taken on faith.
Account Service Unavailable · 18 NOV 2026 00:56 UTC
up24 opened 435 incidents for Gemini in the last 90 days; 61 line up with something Gemini published within six hours, and the rest have no published report near them. Pairing is by time alone — nothing checks that a notice is about the fault up24 measured, so none of it should be read as a scoop . Every entry links to the venue's own notice so the pairing can be judged.
GEMINI — OTHER INCIDENTS
Measured by up24's own probe against Gemini's public API, btcusd against USD, every 5s. This page is generated from the incident's own rows — 4 recorded transitions — and nothing on it is reported by Gemini.