Gemini REST · ping degradation, 2 min on 26 OCT 2026
Gemini REST · ping — 9.1% of checks failing over the last five minutes (timeout) — from Lauterbourg, FR only; 2 regions had too little evidence. up24 opened this incident from its own measurements of Gemini's public API on 26 OCT 2026 22:12 UTC. It lasted 2 min and ended 26 OCT 2026 22:14 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded, timeout.
- 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 872 checks failed.
REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 26 OCT 2026 21:42 UTC to 26 OCT 2026 22:44 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 485 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 — 2 recorded transitions — and nothing on it is reported by Gemini.