Identified - GitBook, our documentation hosting provider, is currently experiencing a platform-wide service disruption. As a result, some pages on our docs site may intermittently return errors (500s) while GitBook works to restore full service.
We’re monitoring the situation and will update this notice as we learn more. You can also follow GitBook’s own status updates at status.gitbook.com.
Nov 03, 2026 - 10:23 EST
We’re monitoring the situation and will update this notice as we learn more. You can also follow GitBook’s own status updates at status.gitbook.com.
Nov 03, 2026 - 10:23 EST
Authorization
Operational
API
Operational
File manager FSP API
Operational
Co-editing
Operational
SDK Console
Operational
Support site
Degraded Performance
Other services
Operational
Third-party components
Operational
AWS CloudFront
Operational
AWS s3-eu-west-1
Operational
AWS Route53
Operational
AWS ec2-eu-west-1
Operational
Filestack API
Operational
AWS rds-eu-west-1
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Upcoming shutdown of legacy multiparser and bumper endpoints Nov 4, 2026 04:00-12:00 EST
As part of ongoing improvements to our SDK infrastructure and deployment model, we're retiring a set of endpoints that will no longer be reachable after December 14, 2026. After that date, these endpoints will be permanently decommissioned, and any calls to them will start failing.
We'd encourage you to check whether your integration depends on any of these calls, so their removal doesn't cause unexpected issues. The Content Services API and the editor instance methods already cover the same needs and are fully documented.
Endpoints being retired:
Multiparser
https://bee-multiparser.getbee.io
https://delayed-bee-multiparser.getbee.io
Paths starting with /api/v3/parser/ (/email, /page, /popup)
Bumper
https://bee-bumper.getbee.io
https://delayed-bee-bumper.getbee.io
Paths including /message and /bump-row
To help you confirm the impact ahead of time, we’ll run two brownout windows in the weeks leading up to the shutdown, temporarily disabling these endpoints so you can verify whether your integration depends on them, rather than finding out on the shutdown date itself:
On November 4, 2026, at 01:00 AM PDT / 04:00 AM EDT / 10:00 AM CEST, we will run an 8-hour brownout to allow you to verify the correct migration to the new services.
If you have any questions, feel free to reach out to our Support Team at sdksupport@beefree.io.
Posted on Nov 03, 2026 - 09:01 EST
We'd encourage you to check whether your integration depends on any of these calls, so their removal doesn't cause unexpected issues. The Content Services API and the editor instance methods already cover the same needs and are fully documented.
Endpoints being retired:
Multiparser
https://bee-multiparser.getbee.io
https://delayed-bee-multiparser.getbee.io
Paths starting with /api/v3/parser/ (/email, /page, /popup)
Bumper
https://bee-bumper.getbee.io
https://delayed-bee-bumper.getbee.io
Paths including /message and /bump-row
To help you confirm the impact ahead of time, we’ll run two brownout windows in the weeks leading up to the shutdown, temporarily disabling these endpoints so you can verify whether your integration depends on them, rather than finding out on the shutdown date itself:
On November 4, 2026, at 01:00 AM PDT / 04:00 AM EDT / 10:00 AM CEST, we will run an 8-hour brownout to allow you to verify the correct migration to the new services.
If you have any questions, feel free to reach out to our Support Team at sdksupport@beefree.io.
Posted on Nov 03, 2026 - 09:01 EST