← Gemini status page

Gemini REST · depth degradation, ongoing since 20 NOV 2026

Gemini REST · depth — p95 1583ms over the last five minutes, 4.6× the 7-day baseline of 346ms — from Lauterbourg, FR and Carlstadt, US. up24 opened this incident from its own measurements of Gemini's public API on 20 NOV 2026 20:52 UTC. It is still open, 1h 00m in.

DEGRADEDREST · depth · https://api.gemini.com/v1/book/btcusd?limit_bids=20&limit_asks=20
DURATION
1h 00m
STARTED
20 NOV 2026 20:52 UTC
ENDED
ONGOING
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

  1. 20 NOV 2026 20:52 UTC
    up24 opened the incident at degraded.

HOW IT FAILED

Over the window, 73 of 4,318 checks failed: timeout ×72, http_5xx ×1.

— p50‑ ‑ p95
axis 0 – 5000ms
19:52 · 20 NOV20:51 · 20 NOV21:51 · 20 NOV

REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 20 NOV 2026 19:51 UTC to 20 NOV 2026 21:52 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 441 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 — 1 recorded transitions — and nothing on it is reported by Gemini.