All Systems Operational

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

First brownout for legacy auth deprecation Sep 24, 2025 03:00-12:00 EDT

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 September 24, 2025, all auth traffic will be temporarily rerouted to our /loginv2 endpoint during two brownout windows, lasting 1 hour each:
- First window starts at 12:00 AM PDT / 3:00 AM EDT / 7:00 AM UTC / 9:00 AM CEST / 12:30 PM IST
- Second window starts at 9:00 AM PDT / 12:00 PM EDT / 4:00 PM UTC / 6:00 PM CEST / 9:30 PM IST

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

πŸ“… Upcoming brownouts and final cutover:
- October 15, 2025 – V2-only auth for 6 hours.
- January 13, 2026 – V2-only auth for 12 hours.
- January 27, 2026 – Legacy auth permanently removed.

Posted on Jun 25, 2025 - 11:12 EDT
Jul 1, 2025

No incidents reported today.

Jun 30, 2025

No incidents reported.

Jun 29, 2025

No incidents reported.

Jun 28, 2025

No incidents reported.

Jun 27, 2025

No incidents reported.

Jun 26, 2025

No incidents reported.

Jun 25, 2025

No incidents reported.

Jun 24, 2025

No incidents reported.

Jun 23, 2025

No incidents reported.

Jun 22, 2025

No incidents reported.

Jun 21, 2025

No incidents reported.

Jun 20, 2025
Resolved - We would like to extend our sincere apologies for any inconvenience or concern caused by any incident you were notified of today. After a thorough review, we have identified that the issue was the result of a false alarm, which triggered our automated systems.

Please be assured that our systems remain fully operational, and we are actively implementing updates and safeguards to prevent similar occurrences in the future. Our team is committed to maintaining the reliability and integrity of our services, and we deeply regret any disruption this may have caused.

We appreciate your understanding and patience as we continue to improve our processes.

Jun 20, 11:28 EDT
Jun 19, 2025

No incidents reported.

Jun 18, 2025

No incidents reported.

Jun 17, 2025

No incidents reported.