GitBook incident: API operations are slower than usual

1. resolvedOct 28, 2026, 23:48 UTC

   The incident on Cloudflare is solved and our monitoring confirms that things are back to normal.

2. monitoringOct 28, 2026, 14:28 UTC

   We have routed parts of our API connection to other regions to improve stability while this gets fixed by Cloudflare. We continue to monitor the situation as it progresses.

3. identifiedOct 28, 2026, 09:15 UTC

   Our API is responding slower than usual due to a known incident on Cloudflare. Any operations going through the affected region are slower or timing out. We are monitoring the incident closely. Cloudflare incident: <https://www.cloudflarestatus.com/incidents/snth5ero95rz>

What APIStatus.watch saw

• Oct 28, 2026, 09:19 UTCoperational → degraded

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Sanity: Studio, Dashboard, Content Agent, & Manage timeoutsCritical · Oct 28, 2026, 11:49 UTC
• GitHub: Disruption with some Copilot servicesCritical · Oct 28, 2026, 14:12 UTC
• Vimeo: Delays processing new video uploadsCritical · Oct 28, 2026, 19:57 UTC
• New Relic: Next-Gen Entity Platform IssuesMajor · Oct 28, 2026, 09:35 UTC
• Shippo: DPD UK Service DegradationMajor · Oct 28, 2026, 15:30 UTC
• Datadog: Metrics query are disruptedMajor · Oct 28, 2026, 16:10 UTC
• Cursor: Multiple services degradedMajor · Oct 28, 2026, 21:15 UTC
• Shippo: La Poste Service DegradationMajor · Oct 28, 2026, 23:00 UTC
• Akamai: Edge Delivery issues between Indonesia and SingaporeMinor · Oct 25, 2026, 13:44 UTC
• Linode: Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2)Minor · Oct 25, 2026, 13:54 UTC

How often does GitBook have incidents?

GitBook reported 7 incidents in the last 90 days, 5 of them major or critical. A typical incident lasted 7h 18m. See GitBook's uptime and incident history