Information listed here rarely shows the outages that many of us experience
Sorry, I cannot help with that one. I was sharing the link for @chuckkay.
I finally managed to get my printer connected to the internet again. I had opened a support ticket over this when it wouldn’t reconnect no matter what. After flipping over to a mobile hot spot, then back (failed on the flip back) I had to tweak my router settings so that it would connect. Keep in mind, I have a domain controller on my network (a VM) that performs DNS and DHCP services/functions for most of the network. Originally, I had the router providing those services for the upper band of the network (IP 225 and above). I set that back and changed the secondary DNS server of the router to one from Google (8.8.8.8). NOW the printer is connecting up to the internet. At least as of this moment.
Honestly, I have little confidence that this will remain connected after any power cycling. The fact that WE cannot see what’s really going on within the network connection of the printer is no small item (at least for those more technologically skilled). Add to that how it’s using the ancient 2.4GHz band when not a wireless device, is not a minor item. 5GHz has been out for more than a decade already. Chips for that are very low cost. As are chips to allow us to connect over an ethernet cable. Having the option to hard wire the printer to the network would resolve issues for many of us. Plus, using a Gb ethernet connection would be significantly faster than what it currently uses for speed.
Yes, but that does not mean 2.4 is obsolete. The bands have very different performance characteristics. As an industry, IoT devices have continued to standardize on 2.4 because the signal travels further and bandwidth capacity is not typically a concern. Bambu is using an off the shelf IoT chipset for their networking.
Last 3D printer I had (before getting the X1 Carbon) also had an ethernet port (1Gb connection) AND USB port so you didn’t need to connect it to ANY network. Or, you could just plug a cable into it and NOT need to worry about the wireless network connecting.
I’m in the IT field, so NOT having the ability to look into the network settings is a serious negative mark on these units. Even if they placed it under an “advanced” section, with warnings and such, it would be better than dumbing it down to the degree it is. I would think that there’s a good percentage of users that ARE tech savvy enough to take advantage of those settings. They could also offer MORE information for when the damned thing cannot connect to the internet, but DOES connect to the router. Especially when every other item connecting to that same router is going online without ANY issue at all.
Someone decided to go with the lowest option on connectivity for these units. There’s plenty of IoT boards out there with different options. With what these units cost, they could spend the couple dollars more to get the richer feature set on them.
But this is not your previous printer… You bought this one, and the specs are well documented. I don’t understand buying a technical product and then complaining after the fact that expectations are somehow not met on a documented configuration item. None of us were part of or have access into Bambu’s requirements gathering, business cases, or overall project scope that resulted in the final product that ultimately we accepted by spending our money on. Making armchair judgment about why a technical design decision turned out the way it did would be purely speculative.
This pruduct utilizes a 2.4Ghz IoT chipset. This product was designed to be a cloud connected consumer device. Since launch some good progress has been made on allowing a local area network only mode. Sneaker Net is also supported. There are plenty of alternatives if these are incompatible with your needs or expectations.
1 Like
Were you unaware of this situation when you purchased your machine? I was and have had minimal issues with it. My only suggestion would be that BBL send out a message to users when their network has a hiccup so we don’t waste our time looking for a problem in our own systems which doesn’t exist.
You could check the status page as the first step of troubleshooting your own systems. And while not as convenient as an email, they do have an RSS feed or updates via a webhook. Both could probably be configured somewhere (like Zapier) to send out emails if you require a notification for every service interruption.
1 Like
Yeah, it’s been mostly down all morning for me, and the status page is all green… so… Perhaps it’s just a coincidence. 
It’s only happened 3 times for me . The first time I was unaware of the status page. The other two times the status page indicated that all was well.
They not only can’t be bothered to send out a group email but they also don’t have time to update their own status page.
I think the idea of the status page is to manually check for issues when it matters to you (like when you’re printing). Not sure sending an email for every single issue would be something most people would want – unless they are in fact printing 24-7.
1 Like
Yeah, exactly… at least, nice idea. However, any time I’ve had problems with the cloud service the status page says everything is cool.
Quite possible too, but that’s not what @kljjbb mentioned above.
That’s exactly what I was saying above. They don’t seem to have time to update their status page when there is a cloud issue. I’m not sure how I could make it any more plain. Also if you don’t want messages when the cloud is down, there is a box you can uncheck 
Don’t get me wrong. I am a big fan of my X1C and AMS but not so much BBL’s support.
I have been starting print jobs all day today. Four of them throughout the day. Never once failed to go thru the cloud service. I’m in North America.
1 Like
Chances are very good that cloud issues/outages may only affect a subset of users, though.
Based on what l have seen before on this forum, but when the service is down this place blows up with loads of angry users. Here and on reddit. But that is not happening from what I can see over there or here. 
1 Like
Hey, online guy here, I wanted to send to print and got an error. I saw status code 502 and immediately knew this was cloud outage.
Bambu status page didn’t show it. I clicked again and it was sent. Temporary failures may not show on that page.
Check your error output next time. Everything above 500 is server fault (cloud/bambulab issue):
500 => bambu service failed to perform the task
502 => something broke, availability to what you want broke
503 => server maintenance
504 => something timed out, too much traffic or failed load balancing
could be the new version of studio and firmware released and being pulled by every BL user?
