Gemini REST · depth degradation, 4 min on 31 AUG 2026
Gemini REST · depth — intermittently degraded: 2 episodes in the last hour, most recently p95 1104ms over five minutes, 12.3× the 7-day baseline of 90ms — from Lauterbourg, FR and Carlstadt, US. up24 opened this incident from its own measurements of Gemini's public API on 31 AUG 2026 00:01 UTC. It lasted 4 min and ended 31 AUG 2026 00:05 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.
HOW IT FAILED
Over the window, 0 of 2,302 checks failed: no error class was recorded against them.
REST latency for the failing endpoint, per minute, from 30 AUG 2026 23:31 UTC to 31 AUG 2026 00:35 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 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 — 2 recorded transitions — and nothing on it is reported by Gemini.