Gemini REST · ticker outage, 6 min on 08 SEP 2026
Gemini REST · ticker — 25% of checks failing over the last minute (http_5xx) — from Singapore, SG and Lauterbourg, FR. up24 opened this incident from its own measurements of Gemini's public API on 08 SEP 2026 19:57 UTC. It lasted 6 min and ended 08 SEP 2026 20:04 UTC, when the component started answering again.
WHAT HAPPENED
- Gemini published its own notice.
- up24 opened the incident at degraded, http_5xx.
- up24 raised it to outage — the same incident, not a second one.
- The component started answering again. up24 dates the incident from this moment, not from when its clearing rule finished.
- Gemini marked its notice resolved.
HOW IT FAILED
Over the window, 29 of 2,408 checks failed: http_5xx ×17, timeout ×12.
REST latency for the failing endpoint, per minute, from 08 SEP 2026 19:27 UTC to 08 SEP 2026 20:34 UTC. The gap in the line is where nothing answered.
DID GEMINI SAY SO?
Gemini acknowledged the same event 2h 17m before up24 opened this incident, on 08 SEP 2026 17:40 UTC: “Delayed Cosmos Deposits and Withdrawals”. Matching is by time window, and their notice is linked so the pairing can be judged rather than taken on faith.
Delayed Cosmos Deposits and Withdrawals · 08 SEP 2026 17:40 UTC
up24 opened 421 incidents for Gemini in the last 90 days; 30 fall within six hours of something Gemini published, and the rest were never mentioned. At the median, Gemini's own notice came 1h 20m before up24 opened its incident. Pairing is by time alone — nothing checks that a notice is about the fault up24 measured, so the 11 that up24 timestamped first are not scoops. 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 — 5 recorded transitions — and nothing on it is reported by Gemini.