<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>GitBook incidents — Vendor Status Watch</title><link>https://approjects-vendor-status-watch.static.hf.space/v/gitbook.html</link><description>Incidents from GitBook's public status page, polled daily.</description><lastBuildDate>Wed, 16 Sep 2026 12:28:20 +0000</lastBuildDate><item><title>App and published docs unavailable [resolved]</title><link>https://www.gitbookstatus.com</link><guid isPermaLink="false">gitbook:2026-09-05T18:56:14Z</guid><pubDate>Sat, 05 Sep 2026 18:56:14 +0000</pubDate><description>The incident is now fully resolved, all services are now up and stable.</description></item><item><title>GitHub outage affecting Git Sync [resolved]</title><link>https://www.gitbookstatus.com</link><guid isPermaLink="false">gitbook:2026-08-17T13:56:04Z</guid><pubDate>Mon, 17 Aug 2026 13:56:04 +0000</pubDate><description>The GitHub operations should be returning to normal as its service is back online. We’ll keep monitoring for any updates to the incident.

 

GitHub Incident status: &lt;https://www.githubstatus.com/incidents/zkxwbgr0cnmx&gt;</description></item><item><title>GitBook webapp is returning 500 [resolved]</title><link>https://www.gitbookstatus.com</link><guid isPermaLink="false">gitbook:2026-06-25T11:34:57Z</guid><pubDate>Thu, 25 Jun 2026 11:34:57 +0000</pubDate><description>The incident has been resolved and systems are fully operational.</description></item><item><title>Sites are failing intermittently with 500 Internal Server Error [resolved]</title><link>https://www.gitbookstatus.com</link><guid isPermaLink="false">gitbook:2026-06-22T14:58:06Z</guid><pubDate>Mon, 22 Jun 2026 14:58:06 +0000</pubDate><description>The fix released has solved the issue, all systems should be operational now.</description></item><item><title>Increased API error rate [resolved]</title><link>https://www.gitbookstatus.com</link><guid isPermaLink="false">gitbook:2026-06-02T14:40:51Z</guid><pubDate>Tue, 02 Jun 2026 14:40:51 +0000</pubDate><description>The incident has been resolved, all systems have returned to normal.</description></item><item><title>Degraded database performance [resolved]</title><link>https://www.gitbookstatus.com</link><guid isPermaLink="false">gitbook:2026-05-08T15:52:44Z</guid><pubDate>Fri, 08 May 2026 15:52:44 +0000</pubDate><description>The fix has improved the performance back to their normal levels.</description></item><item><title>500 errors on some *.gitbook.io published sites [resolved]</title><link>https://www.gitbookstatus.com</link><guid isPermaLink="false">gitbook:2026-05-04T11:55:06Z</guid><pubDate>Mon, 04 May 2026 11:55:06 +0000</pubDate><description>We issued a fix and have monitored the results of that fix. Pages are now loading at normal rates and our logs are looking healthy. </description></item><item><title>Git Sync executions are delayed due to third-party outage [resolved]</title><link>https://www.gitbookstatus.com</link><guid isPermaLink="false">gitbook:2026-04-15T15:34:16Z</guid><pubDate>Wed, 15 Apr 2026 15:34:16 +0000</pubDate><description>The Inngest incident causing Git Sync delays has been resolved. Everything should be back to normal!

Please note that any syncs that didn&#x27;t go through during the incident won&#x27;t be retried automatically, so you&#x27;ll need to push again to trigger a new sync. If you&#x27;re still seeing any issues, reach out and we&#x27;ll take a look!</description></item><item><title>Degraded API performance [resolved]</title><link>https://www.gitbookstatus.com</link><guid isPermaLink="false">gitbook:2026-03-27T14:43:39Z</guid><pubDate>Fri, 27 Mar 2026 14:43:39 +0000</pubDate><description>Indicators are pointing to a healthy state now after the fix. Everything should be operating well.</description></item><item><title>Documentation sites with a custom domain returned a 404 error [resolved]</title><link>https://www.gitbookstatus.com</link><guid isPermaLink="false">gitbook:2026-03-06T16:56:58Z</guid><pubDate>Fri, 06 Mar 2026 16:56:58 +0000</pubDate><description>Between 14:36 and 14:43 UTC, all GitBook documentation sites using a custom domain were returning a 404 &quot;Not Found&quot; error, making documentation unavailable to users. The issue was caused by a problem introduced by an upstream provider that affected our deployment. The incident was resolved by rolling back the deployment, after which all sites were confirmed to be fully operational.</description></item><item><title>Site wide outage [resolved]</title><link>https://www.gitbookstatus.com</link><guid isPermaLink="false">gitbook:2026-02-26T17:15:40Z</guid><pubDate>Thu, 26 Feb 2026 17:15:40 +0000</pubDate><description>Both the application and published content have recovered fully after the fix was released and should be working as expected.</description></item><item><title>App and Public content failures due to Cloudflare outage [resolved]</title><link>https://www.gitbookstatus.com</link><guid isPermaLink="false">gitbook:2025-12-05T09:12:43Z</guid><pubDate>Fri, 05 Dec 2025 09:12:43 +0000</pubDate><description>[Cloudflare have resolved](https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q) the incident and we have seen full recovery of public content and the app.</description></item><item><title>Intermittent change request failures [resolved]</title><link>https://www.gitbookstatus.com</link><guid isPermaLink="false">gitbook:2025-11-18T12:55:36Z</guid><pubDate>Tue, 18 Nov 2025 12:55:36 +0000</pubDate><description>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. </description></item><item><title>Public content not loading or taking longer to load [resolved]</title><link>https://www.gitbookstatus.com</link><guid isPermaLink="false">gitbook:2025-10-20T09:16:02Z</guid><pubDate>Mon, 20 Oct 2025 09:16:02 +0000</pubDate><description>GitBook is back to normal and fully functional.</description></item><item><title>All AI based features including GitBook Assistant or AI search are failing with &quot;something went wrong&quot; [resolved]</title><link>https://www.gitbookstatus.com</link><guid isPermaLink="false">gitbook:2025-09-16T07:07:32Z</guid><pubDate>Tue, 16 Sep 2025 07:07:32 +0000</pubDate><description>The issue was identified and fixed. All AI features are working as expected. </description></item></channel></rss>