Gemini REST · depth degradation, 42 min on 16 SEP 2026
Gemini REST · depth — intermittently degraded: 4 episodes in the last hour, most recently p95 1601ms over the last five minutes, 5× the 7-day baseline of 323ms — from Lauterbourg, FR and Carlstadt, US. up24 opened this incident from its own measurements of Gemini's public API on 16 SEP 2026 18:15 UTC. It lasted 42 min and ended 16 SEP 2026 18:57 UTC, when the component started answering again.
WHAT HAPPENED
- Gemini published its own notice.
- Gemini marked its notice resolved.
- 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.
HOW IT FAILED
Over the window, 1 of 4,517 checks failed: timeout ×1.
REST latency for the failing endpoint, per minute, from 16 SEP 2026 17:32 UTC to 16 SEP 2026 19:39 UTC. The gap in the line is where nothing answered.
DID GEMINI SAY SO?
Gemini acknowledged the same event 1h 40m before up24 opened this incident, on 16 SEP 2026 16:35 UTC: “Credit Card Support Calls Unavailable”. Matching is by time window, and their notice is linked so the pairing can be judged rather than taken on faith.
Credit Card Support Calls Unavailable · 16 SEP 2026 16:35 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.