All Systems Operational

Authorization Operational
API Operational
File manager FSP API Operational
Co-editing Operational
Developer Portal ? 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

Scheduled Maintenance

Last brownout for legacy auth deprecation Jan 13, 2026 02:00-21:00 EST

As part of our transition to a more secure authentication system, we are phasing out the Beefree SDK’s legacy (v1) auth process. This includes a series of scheduled brownouts, ending with its permanent removal in January 2026.

On January 13, 2026, all auth traffic will be temporarily rerouted to our /loginv2 endpoint during two brownout windows, lasting 6 hours each:
- First window starts at 11:00 PM PST* / 2:00 AM EST / 7:00 AM UTC / 8:00 AM CET / 12:30 PM IST
- Second window starts at 12:00 PM PST / 3:00 PM EST / 8:00 PM UTC / 9:00 PM CST / 1:30 AM IST
*The brownout will start on January 12 at 11:00 PM on Pacific Standard Time.

If you are still using the legacy endpoint (https://auth.getbee.io/apiauth), you may experience temporary authentication failures during these windows. This is a warning event to help identify lingering dependencies and help your team prepare for the full transition.

To avoid service interruptions, update your integration to use the new V2 authentication flow before the first brownout.

đź”— Learn more about the V2 Auth process and why we are making this change:
https://devportal.beefree.io/hc/en-us/articles/20094954610450-Changes-to-the-Authorization-Process

đź”— You can find full Implementation details in our developer documentation:
https://docs.beefree.io/beefree-sdk/getting-started/readme/installation/authorization-process-in-detail

đź“… Final cutover:
- January 27, 2026 – Legacy auth permanently removed.
Posted on Nov 04, 2025 - 10:31 EST
Nov 8, 2025

No incidents reported today.

Nov 7, 2025

No incidents reported.

Nov 6, 2025

No incidents reported.

Nov 5, 2025

No incidents reported.

Nov 4, 2025

No incidents reported.

Nov 3, 2025

No incidents reported.

Nov 2, 2025

No incidents reported.

Nov 1, 2025

No incidents reported.

Oct 31, 2025
Update on Co-Editing Service Stability
Resolved - Although the incident is now marked as Resolved, we remain in a monitoring phase to confirm that the issue does not recur. Our co-editing service will continue to operate on the old version, which is fully stable and functioning as expected.

We're leaving no stone unturned and are dedicating substantial resources to strengthening our co-editing infrastructure.
Oct 31, 16:38 EDT
Update - After careful evaluation, we have decided to continue utilizing the previous version of our co-editing service for at least the next several days. This approach will provide us with additional time to ensure system stability, thoroughly investigate and resolve any potential issues, and implement measures to minimize disruptions.

Our goal is to reduce—and ideally eliminate—instances where the editor crashes due to a co-editing service failure.
Oct 31, 15:30 EDT
Monitoring - Due to recent issues with the latest version of our co-editing service, we’re temporarily routing traffic to a previous version.
This older version offers lower performance but higher stability, which helps us minimize the risk of a total service outage while we address the underlying problems.

Known Issues in the Older Version
Intermittent “Connecting…” messages: Some users on specific network types may see this message, accompanied by corresponding entries in the onError callback logs.
Duplicate user icons: In some implementations, refreshing the browser can cause duplicate user avatars to appear.

What This Means
We understand these issues may look like a regression in behavior, and we recognize the potential discomfort for users. Our priority is to maintain continuous availability of the co-editing experience while we work on a stable fix for the new version.
Oct 31, 14:02 EDT
Coediting and Template Loading Issues
Resolved - The issue affecting the Coediting functionality and causing templates not to load correctly in instances where Coediting was enabled has been fully resolved.

After 30 minutes of monitoring, the service has remained stable, and all systems are now operating normally.

Thank you for your patience while we worked to restore the service.
Oct 31, 13:10 EDT
Monitoring - We have identified and resolved the issue that was affecting the Coediting functionality and causing templates not to load correctly in instances where Coediting was enabled.

The service is now fully operational, and we are currently monitoring to ensure stability.
Oct 31, 12:37 EDT
Investigating - We are investigating a service disruption affecting the Coediting functionality. In instances where Coediting is enabled, users may experience issues with templates not loading correctly.

Our team is actively working to identify the cause and restore full functionality as soon as possible. We will provide updates here as soon as more information becomes available.

Thank you for your patience.
Oct 31, 12:31 EDT
Oct 30, 2025

No incidents reported.

Oct 29, 2025

No incidents reported.

Oct 28, 2025

No incidents reported.

Oct 27, 2025
Co-editing Issues
Resolved - The issue has been resolved and our service has returned to normal. Our team is investigating the root cause and will provide additional details as they become available.
Oct 27, 15:54 EDT
Investigating - We experienced a brief disruption with a real-time data streaming service. This may have impacted customers’ ability to use the builder and/or our co-editing service.
Oct 27, 15:29 EDT
Oct 26, 2025

No incidents reported.

Oct 25, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage