← Gemini status page

Gemini REST · depth degradation, 2 min on 20 NOV 2026

Gemini REST · depth — p95 1612ms over the last five minutes, 4.7× 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 16:08 UTC. It lasted 2 min and ended 20 NOV 2026 16:10 UTC, when the component started answering again.

DEGRADEDREST · depth · https://api.gemini.com/v1/book/btcusd?limit_bids=20&limit_asks=20
DURATION
2 min
STARTED
20 NOV 2026 16:08 UTC
ENDED
20 NOV 2026 16:10 UTC
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

  1. 20 NOV 2026 16:08 UTC
    up24 opened the incident at degraded.
  2. 20 NOV 2026 16:10 UTC
    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, 0 of 2,233 checks failed.

— p50‑ ‑ p95
axis 0 – 5000ms
15:39 · 20 NOV16:09 · 20 NOV16:40 · 20 NOV

REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 20 NOV 2026 15:38 UTC to 20 NOV 2026 16:40 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 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.