← Gemini status page

Gemini REST · ticker degradation, 4 min on 19 NOV 2026

Gemini REST · ticker — 42% of checks failing over the last minute (timeout) — from Singapore, SG and Lauterbourg, FR — not graded an outage until it has failed for 2 minutes. up24 opened this incident from its own measurements of Gemini's public API on 19 NOV 2026 19:26 UTC. It lasted 4 min and ended 19 NOV 2026 19:30 UTC, when the component started answering again.

DEGRADEDREST · ticker · https://api.gemini.com/v2/ticker/btcusd
DURATION
4 min
STARTED
19 NOV 2026 19:26 UTC
ENDED
19 NOV 2026 19:30 UTC
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

  1. 19 NOV 2026 19:26 UTC
    up24 opened the incident at degraded, timeout.
  2. 19 NOV 2026 19:30 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, 10 of 2,304 checks failed: timeout ×10.

— p50‑ ‑ p95
axis 0 – 2000ms
18:57 · 19 NOV19:28 · 19 NOV20:00 · 19 NOV

REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 19 NOV 2026 18:56 UTC to 19 NOV 2026 20:00 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.