From observing their slicer and suite i think the software part of the business lags the hardware part pretty badly.
How would you resonably expect the average user to come to any useful conclusion along those lines in this scenario?
It would just appear as a connection issue, how exactly does someone get from “My Bambu stuff isn’t working” to “The ha-bambulab integration has a bug that’s hammering the server, so I’ve been temporarily banned”
What lkraus describes is actually a common industry practice. Many online services, from large platforms like YouTube to small websites that rely on cloud infrastructure, use rate limiting. When too many requests come from a single source, the system will usually slow down that IP address or user account first and, if necessary, temporarily block it for a certain period.
The advantage of this approach is that it only affects a small number of users, instead of causing the entire cloud service to become unstable. Ideally, a cloud platform should be able to detect when a specific user is generating an unusually high number of requests and handle that traffic separately.
In fact, Bambu is one of the few services that seems to struggle with this. That is also why they started using Cloudflare for the forum a few months ago, which was definitely a step in the right direction.
With proper rate limiting in place, there would probably still be some complaints in the forum, but only from a handful of affected users rather than from the entire user base being impacted.
The cloud also reports back the reason why someone is being throttled - even when someone is put on hold. After an hour, he might even be able to reconnect.
Here’s an example: if I intentionally send too many requests to a well-known website - it doesn’t matter which one it is - In my test, I send 20 requests in a short time frame. The bouncer says: No!
That’s a lot of text, but it was actually summed up in just one sentence…