Gemini WS · connection degradation, 6 min on 14 NOV 2026
Gemini WS — 6.7% of windows failing over the last five minutes (conn) — from Carlstadt, US and Lauterbourg, FR. up24 opened this incident from its own measurements of Gemini's public API on 14 NOV 2026 22:56 UTC. It lasted 6 min and ended 14 NOV 2026 23:03 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded, conn.
- 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, 34 of 2,394 ten-second windows failed: conn ×34.
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 publishes a status feed and nothing in it lines up with this incident. That is not proof they stayed silent; it is what their feed says.
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 — 2 recorded transitions — and nothing on it is reported by Gemini.