Gemini REST · ticker degradation, 50 min on 06 NOV 2026
Gemini REST · ticker — intermittently degraded: 4 episodes since it opened, most recently p95 1264ms over the last five minutes, 4.1× 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 06 NOV 2026 14:43 UTC. It lasted 50 min and ended 06 NOV 2026 15:33 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded.
- The component started answering again. up24 dates the incident from this moment, not from when its clearing rule finished.
- Gemini published its own notice.
- Gemini marked its notice resolved.
HOW IT FAILED
Over the window, 2 of 5,400 checks failed: timeout ×2.
REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 06 NOV 2026 13:53 UTC to 06 NOV 2026 16:23 UTC. The gap in the line is where nothing answered.
DID GEMINI SAY SO?
Gemini published a notice within six hours of this incident, on 06 NOV 2026 19:10 UTC: “Crypto Withdrawals and Deposits Paused via EVM chain(excluding Ethereum)”. It is paired by time alone, within six hours — nothing checks that it is about this fault, so it is linked to be judged rather than taken on faith.
Crypto Withdrawals and Deposits Paused via EVM chain(excluding Ethereum) · 06 NOV 2026 19:10 UTC
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 — 4 recorded transitions — and nothing on it is reported by Gemini.