← Gemini status page

Gemini REST · ping degradation, 54 min on 20 NOV 2026

Gemini REST · ping — p95 1678ms over the last five minutes, 4.4× the 7-day baseline of 383ms — from Lauterbourg, FR and Carlstadt, US. up24 opened this incident from its own measurements of Gemini's public API on 20 NOV 2026 20:55 UTC. It lasted 54 min and ended 20 NOV 2026 21:49 UTC, when the component started answering again.

DEGRADEDREST · ping · https://api.gemini.com/v1/symbols/details/btcusd
DURATION
54 min
STARTED
20 NOV 2026 20:55 UTC
ENDED
20 NOV 2026 21:49 UTC
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

  1. 20 NOV 2026 20:55 UTC
    up24 opened the incident at degraded.
  2. 20 NOV 2026 21:49 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, 75 of 3,996 checks failed: timeout ×75.

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

REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 20 NOV 2026 20:00 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 — 2 recorded transitions — and nothing on it is reported by Gemini.