GitBook incident: Intermittent change request failures

1. resolvedNov 18, 2025, 15:46 UTC

   Cloudflare has [confirmed](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7) that the incident has now been resolved, and we are seeing that change requests are working as expected.

2. monitoringNov 18, 2025, 13:26 UTC

   We are still monitoring the current incident. Cloudflare has identified and is resolving the issue, and has updated its status page [here](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7).

3. identifiedNov 18, 2025, 12:55 UTC

   We've identified an ongoing incident with Cloudflare, who have updated their status page [here](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7). This is impacting change requests, where creating new requests or merging existing ones is working intermittently.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in GitBook's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Confluence: Elevated Errors in Confluence Whiteboards and Databases Due to Cloudflare OutageCritical · Nov 18, 2025, 13:32 UTC
• 1Password: 1password.com Website Access DegradationMajor · Nov 18, 2025, 12:06 UTC
• LogRocket: Dashboard instabilityMajor · Nov 18, 2025, 12:19 UTC
• ReadMe: Cloudflare outageMajor · Nov 18, 2025, 13:27 UTC
• Vimeo: Verification ErrorsMajor · Nov 18, 2025, 14:27 UTC
• 1Password: Item Usage Metrics Not Updating in Real TimeMinor · Nov 13, 2025, 23:55 UTC
• Datadog: Delayed Monitors NotificationsMinor · Nov 18, 2025, 13:17 UTC
• Miro: Ongoing incident with one of our providers - CloudflareMinor · Nov 18, 2025, 14:11 UTC

How often does GitBook have incidents?

GitBook reported 2 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 3h 42m. See GitBook's uptime and incident history