Is there an Beefree SDK outage?
Beefree SDK status: Systems Active
Last checked: 6 minutes ago
Get notified about any outages, downtime or incidents for Beefree SDK and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 6 minutes ago
Get notified about any outages, downtime or incidents for Beefree SDK and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Beefree SDK.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| API | Active |
| Authorization | Active |
| Developer Portal | Active |
| File manager FSP API | Active |
| Support site | Active |
| Third-party components | Active |
| AWS cloudFront | Active |
| AWS ec2-eu-west-1 | Active |
| AWS rds-eu-west-1 | Active |
| AWS route53 | Active |
| AWS s3-eu-west-1 | Active |
| Filestack API | Active |
View the latest incidents for Beefree SDK and check for official updates:
Description: On March 25th, 2019, the BEE Plugin system experienced a rare downtime event. System up-time is of paramount importance to us, and we are very sorry for what happened. As some of you know, many applications within MailUp Group \(BEE's parent company\) rely on BEE Plugin - just like you do. When there is any degradation of performance or outage of any kind, our own company is negatively affected, just like you are. So we owe it to you - and to us - to aim for the highest level of availability and performance. And we are very much committed to that. The March 25th issue occurred within - and was isolated to - legacy infrastructure, which had been scheduled for an upgrade on March 9th. As previously communicated, the March 9th upgrade was successful, but had to be rolled back to assist customers using BEE Plugin authorization tokens in undocumented ways. We decided to roll back because we are committed to supporting each and every BEE Plugin customer with a smooth migration when the system is upgraded. As Murphy's Law dictates, one of the very portions of the system that was scheduled to be upgraded on March 9 - which relies extensively on [Redis](https://redis.io) for in-memory data storage - failed on March 25. Despite very extensive research, we have so far been unable to exactly pinpoint why Redis became unresponsive within our AWS environment. This portion of the BEE Plugin system will be replaced with a new-generation infrastructure on [April 6](https://support.beefree.io/hc/en-us/articles/360022828272-April-6-2019-Scheduled-Maintenance). Extra resources have been deployed in the meantime to ensure that no further downtime events occur between now and April 6. Once again, we sincerely apologize for the downtime. If you have any questions, certainly reach out. All the best, The BEE Team
Status: Postmortem
Impact: Major | Started At: March 26, 2019, 9:26 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: March 26, 2019, 7:08 a.m.
Description: Amazon Web Services resolved the connectivity problems that caused the FSP API service degradation. The service is running without errors or performance issues.
Status: Resolved
Impact: Minor | Started At: Sept. 26, 2018, 9:07 a.m.
Description: We found that one of the load-balanced machines in our AWS environment had become corrupted, which led to the intermittent issues. The AWS environment has been updated and the issue appears to have been resolved. In the short term, we implemented a few changes to minimize any chances of recurrence of this problem: - We increased the authorization token life to 120 seconds. - We modified the UID validator endpoint so that it will trigger a retry request if authorization fails. In the medium term, we plan to review the entire authorization system to make it even more robust and scalable.
Status: Resolved
Impact: None | Started At: Dec. 18, 2017, 9:33 p.m.
Description: We found that one of the load-balanced machines in our AWS environment had become corrupted, which led to the intermittent issues. The AWS environment has been updated and the issue appears to have been resolved. In the short term, we implemented a few changes to minimize any chances of recurrence of this problem: - We increased the authorization token life to 120 seconds. - We modified the UID validator endpoint so that it will trigger a retry request if authorization fails. In the medium term, we plan to review the entire authorization system to make it even more robust and scalable.
Status: Resolved
Impact: None | Started At: Dec. 18, 2017, 9:33 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
