Snapshot 256551
Normalized text
Scripts and page chrome removed; this is what change detection compares.
Subscribe to UpdatesSubscribe All Systems Operational Authorization Operational API Operational File manager FSP API Operational Co-editing Operational SDK Console Operational Support site Operational 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 Past Incidents Nov 11, 2026 No incidents reported today. Nov 10, 2026 No incidents reported. Nov 9, 2026 No incidents reported. Nov 8, 2026 No incidents reported. Nov 7, 2026 No incidents reported. Nov 6, 2026 No incidents reported. Nov 5, 2026 No incidents reported. Nov 4, 2026 Upcoming shutdown of legacy multiparser and bumper endpoints Completed - The scheduled maintenance has been completed. Nov 4, 12:00 EST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Nov 4, 04:00 EST Scheduled - 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. Nov 3, 09:01 EST Nov 3, 2026 Some Beefree SDK documentation pages may be temporarily unavailable Resolved - Our documentation hosting provider has restored full service, and our documentation site is now operating normally. Pages that were intermittently returning errors are loading as expected again. Nov 3, 12:24 EST 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 3, 10:23 EST Nov 2, 2026 No incidents reported. Nov 1, 2026 No incidents reported. Oct 31, 2026 No incidents reported. Oct 30, 2026 No incidents reported. Oct 29, 2026 No incidents reported. Oct 28, 2026 Multiparser Outage Resolved - The root cause of the issue has been pinpointed, and our team has implemented contingencies to prevent it from recurring while we work on a definitive fix. The system is now operational, and we will keep monitoring, although we don't expect further disruption. Oct 28, 10:50 EDT Investigating - Starting today at 14:03:27 UTC, some users may have experienced issues accessing design previews in the editors or exporting HTML, and you might have seen elevated API error rates on the "message/html" endpoint or with the onSave() callback due to an outage affecting our Multiparser, the service that translates Beefree JSON into HTML. We are investigating the root cause and planning contingencies to solve the issue. Thank you for your patience Oct 28, 10:23 EDT Upcoming shutdown of legacy multiparser and bumper endpoints Completed - The scheduled maintenance has been completed. Oct 28, 10:33 EDT Scheduled - 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: October 15, 2026, at 7:00 AM PDT / 10:00 AM EDT / 4:00 PM CEST: a short 2-hour brownout, for an initial check. November 3, 2026 (exact time will be shared closer to the date): a longer brownout lasting approximately 8 hours, for more thorough validation. If you have any questions, feel free to reach out to our Support Team at sdksupport@beefree.io. Oct 14, 08:51 EDT Incident History Powered by Atlassian Statuspage