Gemini REST · ticker degradation, 16 min on 20 NOV 2026
Gemini REST · ticker — p95 2209ms over the last five minutes, 6.2× the 7-day baseline of 355ms — from Lauterbourg, FR and Carlstadt, US. up24 opened this incident from its own measurements of Gemini's public API on 20 NOV 2026 20:27 UTC. It lasted 16 min and ended 20 NOV 2026 20:43 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded.
- 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, 14 of 1,728 checks failed: timeout ×12, http_5xx ×2.
REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 20 NOV 2026 19:57 UTC to 20 NOV 2026 20:46 UTC. The gap in the line is where nothing answered.
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 439 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.