← Gemini status page

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

Gemini REST · ticker — p95 1507ms over the last five minutes, 4.9× the 7-day baseline of 307ms — from Singapore, SG and Carlstadt, US. up24 opened this incident from its own measurements of Gemini's public API on 05 NOV 2026 15:06 UTC. It lasted 4 min and ended 05 NOV 2026 15:10 UTC, when the component started answering again.

DEGRADEDREST · ticker · https://api.gemini.com/v2/ticker/btcusd
DURATION
4 min
STARTED
05 NOV 2026 15:06 UTC
ENDED
05 NOV 2026 15:10 UTC
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

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

— p50‑ ‑ p95
axis 0 – 5000ms
14:37 · 05 NOV15:08 · 05 NOV15:40 · 05 NOV

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