Gemini REST · depth degradation, ongoing since 26 OCT 2026
Gemini REST · depth — intermittently degraded: 3 episodes since it opened, most recently p95 1905ms over the last five minutes, 6.3× the 7-day baseline of 302ms — from Lauterbourg, FR and Carlstadt, US. up24 opened this incident from its own measurements of Gemini's public API on 26 OCT 2026 14:10 UTC. It is still open, 1h 59m in.
WHAT HAPPENED
- up24 opened the incident at degraded.
HOW IT FAILED
Over the window, 0 of 4,642 checks failed.
REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 26 OCT 2026 12:11 UTC to 26 OCT 2026 16:09 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 484 incidents for Gemini in the last 90 days; 31 line up with something Gemini published within six hours, and the rest have no published report near them. At the median, Gemini's own notice came 1h 23m 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 — 1 recorded transitions — and nothing on it is reported by Gemini.