Beefree SDK Status

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

May 13, 2026

No incidents reported today.

May 12, 2026

No incidents reported.

May 11, 2026

Sessions with co-editing enabled fail to start

Resolved - Following our investigation, we've confirmed that the SDK co-editing functionality was not impacted by the issue reported earlier. Co-editing can remain enabled in your SDK Configuration. We apologize for any confusion this may have caused.
May 11, 05:03 EDT

Update - Our team is continuing to investigate the issue with the co-editing functionality. As a temporary measure, editor access can still be restored by disabling co-editing in the SDK configuration.
May 11, 04:37 EDT

Investigating - We are currently experiencing an issue with the co-editing functionality. As a result, any editor session initialized with co-editing enabled will fail to start. While our team works on a resolution, editor access can be restored by disabling co-editing in the SDK configuration. We'll share further updates as soon as we have more information.
May 11, 04:03 EDT

May 10, 2026

No incidents reported.

May 9, 2026

No incidents reported.

May 8, 2026

No incidents reported.

May 7, 2026

No incidents reported.

May 6, 2026

No incidents reported.

May 5, 2026

No incidents reported.

May 4, 2026

No incidents reported.

May 3, 2026

No incidents reported.

May 2, 2026

No incidents reported.

May 1, 2026

No incidents reported.

Apr 30, 2026

Builder loading issue

Postmortem - Read details
May 7, 09:59 EDT

Resolved - Between 9:14 and 9:46 UTC, an internal update caused the builder to fail loading on new instances. Users who already had the builder open were not affected. We rolled back the change, and service was fully restored. Total duration: 32 minutes.

Timeline:
Identified (9:14 UTC): An internal update caused the builder to fail loading on new instances. Users who already had the builder open were not affected.
Monitoring (9:40 UTC): We rolled back the change and started monitoring recovery.
Resolved (9:46 UTC): Service fully restored.
Apr 30, 05:14 EDT

Apr 29, 2026

No incidents reported.