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

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

Oct 27, 2026

No incidents reported.

Oct 26, 2026

No incidents reported.

Oct 25, 2026

No incidents reported.

Oct 24, 2026

No incidents reported.

Oct 23, 2026

No incidents reported.

Oct 22, 2026

No incidents reported.

Oct 21, 2026

No incidents reported.

Oct 20, 2026

No incidents reported.

Oct 19, 2026

No incidents reported.

Oct 18, 2026

No incidents reported.

Oct 17, 2026

No incidents reported.

Oct 16, 2026

No incidents reported.

Oct 15, 2026

No incidents reported.

Oct 14, 2026

Beefree SDK unavailable (502 or 504 errors)
Postmortem - Read details
Oct 14, 11:49 EDT
Resolved - The issue has been resolved. The 502 and 504 errors were caused by a configuration issue in our gateway, which our team has fixed. The Beefree SDK is back online, and all services are operating normally.
Oct 14, 08:30 EDT
Investigating - We’re currently experiencing an issue that makes the Beefree SDK unreachable. Requests to the SDK return a 502 Bad Gateway or 504 Gateway Timeout error, so the editor may fail to load or respond.

Our team is already investigating the cause and working to restore service as quickly as possible. We’ll post an update here as soon as we have more information.
Oct 14, 08:24 EDT
Incident History Powered by Atlassian Statuspage