GitBook outage: Public content not loading or taking longer to load

1. resolvedOct 21, 2025, 07:31 UTC

   GitBook is back to normal and fully functional.

2. monitoringOct 20, 2025, 10:55 UTC

   We are seeing improvements in loading times and performance overall following updates on AWS' outage. We continue to monitor the performance.

3. identifiedOct 20, 2025, 09:16 UTC

   We are aware of issues in loading public content in GitBook. Our team has identified the issue, and it's related to an issue in AWS, currently affecting several upstream providers. More details on the AWS outage here: https://health.aws.amazon.com/health/status Our team is looking into mitigation options.

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.

• Vimeo: AI and Create services unavailableCritical · Oct 20, 2025, 07:55 UTC
• Convex: Many Convex backends are downMajor · Oct 20, 2025, 07:22 UTC
• Airtable: Airtable is partially unavailableMajor · Oct 20, 2025, 07:25 UTC
• 1Password: Intermittent performance issues with 1Password.comMajor · Oct 20, 2025, 09:05 UTC
• Mux: Mux Player embeds increased error ratesMajor · Oct 20, 2025, 09:39 UTC
• Convex: Usage info on Convex dashboard is unavailableMajor · Oct 20, 2025, 14:48 UTC
• Upstash: Upstash Console issuesMajor · Oct 20, 2025, 14:52 UTC
• Pusher: MT1 cluster - increased latencyMajor · Oct 20, 2025, 17:26 UTC
• Pinecone: Some users may be unable to access the Pinecone web console. All API services remain fully operational.Major · Oct 20, 2025, 17:43 UTC
• Miro: User search degradationMajor · Oct 20, 2025, 17:47 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