Gemini REST · depth degradation, 20s on 08 SEP 2026
Gemini REST · depth — p95 1717ms over the last five minutes, 5.6× the 7-day baseline of 306ms — from every region. up24 opened this incident from its own measurements of Gemini's public API on 08 SEP 2026 13:35 UTC. It lasted 20s and ended 08 SEP 2026 13:35 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, 0 of 2,157 checks failed: no error class was recorded against them.
REST latency for the failing endpoint, per minute, from 08 SEP 2026 13:05 UTC to 08 SEP 2026 14:05 UTC. The gap in the line is where nothing answered.
DID GEMINI SAY SO?
Gemini acknowledged the same event 4h 05m after 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 — 4 recorded transitions — and nothing on it is reported by Gemini.