Bambu Cloud Down? How to Keep Printing Anyway
Short version
On July 20, 2026, Bambu Lab's MQTT service failed twice in one evening, blocking owners from starting prints for roughly two hours; four days later an AWS outage disrupted services again. Prints that were already running kept going: outages hit the start command, not the print itself. You have two ways around any cloud outage. Right now, mid-outage: export the sliced file in Bambu Studio, put it on the microSD card or USB drive, and start it from the printer screen. For next time: enable LAN mode, and Bambu Studio talks to your printer directly over your home network, no internet required.
- Title
- Bambu Cloud Down? How to Keep Printing Anyway
- Section
- Troubleshooting
- Published
- Last updated
- Note
- Troubleshooting, works on every Bambu model
- Sources
- Listed under the article
- Page
- Status
- Not affiliated with Bambu Lab
What happened on July 20
Starting around 15:41 UTC, Bambu's status page confirmed an issue with its MQTT serviceA lightweight publish/subscribe messaging protocol. In cloud mode, the "start print" command from Bambu Studio or the Handy app travels through Bambu's MQTT servers to reach your printer. that prevented users from starting print jobs. It was declared resolved at 16:42 UTC, then came back 45 minutes later. The second round took a configuration rollback and the replacement of a misbehaving server to fix. By 18:30 UTC everything was back to normal.
- MQTT outages, one root cause
- 2
- of blocked print starts
- ~2 h
- reports of running prints failing
- 0
Bambu's post-mortem: one faulty node
Bambu published its post-mortem on July 30. A single node in the MQTT cluster developed intermittent network failures. The first fix cleared the backlog but left the node in the cluster, so the same fault came back; removing and replacing the node (17:53 UTC) ended it. Bambu calls the two outages "two recurrences of the same intermittent fault" and plans a multi-region deployment of the service over the coming months.
And July 20 was not a one-off. On July 24, an upstream network outage at AWS disrupted Bambu services for about two and a half hours (10:57 to 13:18 UTC, per the status page): slow loading, timeouts and errors for some users while Bambu failed over to healthy regions. Different cause, same lesson. Three outages from two causes in five days is not a crisis, but it is a pattern worth being prepared for. The most recent entry: on September 27, network instability in an AWS region caused intermittent print timeouts from 00:30 to 01:07 UTC for a small fraction of requests.
Why a cloud outage blocks your prints
In the default cloud mode, the print command does not go straight from your slicer to your printer. When you hit print in Bambu Studio or the Handy app, the command travels to Bambu's servers and back down to your printer over MQTT, even if the printer sits two feet from your PC. That design is what enables printing from anywhere, but it also means Bambu's servers are in the critical path: when MQTT is down, uploads to the cloud fail and the start command never arrives. That is exactly what users saw on July 20, with printers showing as connected while new jobs failed on the upload to the cloud. Since Bambu Studio 2.8.2 (August 14, 2026), Studio automatically tries switching to LAN mode to keep sending the print when the cloud service is abnormal or the network is unstable, per Bambu's release notes (see our Studio 2.8.2 rundown). The July 20 outage predates that release, and the two routes below work with any Studio version.
The important nuance: once a job has started, it runs from the printer itself. A cloud outage does not touch prints already in progress. The problem is purely getting a new job onto the machine, and for that you have two cloud-free routes.
The fastest workaround: print from microSD or USB
This works mid-outage, needs no settings change, and every Bambu printer supports it, via microSD card or USB drive depending on the model:
- Slice your model in Bambu Studio as usual.
- Instead of hitting print, open the small arrow next to the print button and choose Export plate sliced file. You get a
.gcode.3mffile. - Save it to the printer's storage: the microSD card on printers with a card slot (A1, A1 mini, A2L, P1 and X1 series), a USB flash drive on the H2 series, P2S and X2D, which have built-in storage and a USB port instead of a card slot.
- Put the card back in the printer, open the files/folder menu on the printer screen, pick the file, and print.
Keep a card reader in the drawer
The whole workflow is only annoying if you cannot read a microSD card. A $6 USB reader turns "cloud is down" into a 60-second detour. On the X1 series the slot sits right next to the touchscreen; check your model's manual if you have never pulled the card before.
The permanent option: LAN mode
LAN mode (officially "LAN Only") makes the printer and Bambu Studio talk directly over your local network: sending files, monitoring, and controlling the printer all work without internet access. It is also the setup Bambu itself recommends for people printing confidential models. The toggle lives on the printer's own screen, not in the cloud, so you can enable it during an outage.
Step 1: enable it on the printer
The menu path differs slightly by series (per Bambu's official wiki):
| Series | Where to find it |
|---|---|
| H2 / P2S / X series | Settings › LAN Only, turn it on. Optionally enable LAN mode liveview. |
| P1P / P1S | Settings › WLAN › LAN Only Mode › ON, confirm with "Yes". Note the access code shown here. |
| A1 / A1 mini / A2L | Settings, scroll to LAN Only Mode (page 3 on A1 screens), turn it on until the toggle shows green. |
Step 2: bind it in Bambu Studio
- Open the printer list on the Device page. The LAN-mode printer appears with a lock icon in front of its name. Bambu says discovery can take 20 to 60 seconds, occasionally longer.
- Enter the printer's 8-digit access code (shown on the printer screen in the LAN Only settings) and confirm.
- Turn on "LAN Only Liveview" if you want the camera feed inside Studio.
Caution
Two catches worth knowing
X1 series: starting a LAN-mode print from Studio requires the microSD card to be inserted; the printer stages the job on the card. Same network for automatic discovery: Studio lists a LAN-mode printer by itself only when both sit on the same local network; guest Wi-Fi and isolated VLANs often block that discovery. On a different subnet or VLAN, use Device → No Printer → Bind with Access Code and enter the printer's IP address and access code from its LAN Only page (Bambu's access code guide). Bambu's wiki still says Studio does not store the IP, so you would enter it again after every restart; the Bambu Studio 2.7.1 release notes (June 1, 2026) say LAN connection information is now saved locally, so LAN printers no longer need re-binding after a restart. If your Studio still forgets the printer, enter IP and access code again.
What you give up in LAN mode
What still works
- Sending prints from Bambu Studio on your network
- Monitoring and camera liveview in Studio
- Full printer control (temperatures, speed, AMS)
- Printing from local storage (microSD or USB), always
- Immunity to every future cloud outage
What stops working
- The Bambu Handy app (not available in LAN mode)
- Starting prints remotely from outside your network
- Cloud print history
- Sending directly from MakerWorld (it goes through your Bambu account)
- X1 AI failure detection updates lag behind the cloud-connected version
None of this is one-way. LAN mode is a toggle, not a commitment: if you miss the Handy app, switch back the same way you switched on. Some owners run LAN mode permanently for privacy; others flip it on only when the cloud misbehaves.
Third-party slicers need one more switch
On current firmware with Bambu's authorization system (X1 series from 01.08.05.00, P1 series from 01.08.02.00, A1 and A1 mini from 01.05.00.00, plus the H2 series and P2S), third-party software like OrcaSlicer needs Developer Mode enabled alongside LAN mode before it may control the printer. The toggle sits on the same LAN Only settings page. If you go that route and Orca keeps forgetting your access code, that is a known config quirk with a two-minute fix we covered here. Background on why the authorization layer exists is in our Bambu Connect explainer.
| Printer | Bambu's authorization system from |
|---|---|
| X1 series | 01.08.05.00 |
| P1 series | 01.08.02.00 |
| A1 and A1 mini | 01.05.00.00 |
| H2 series and P2S | same Developer Mode switch, no version given |
Versions as documented in our OrcaSlicer article; it gives none for the H2 series and P2S and does not cover the X2D and A2L.
Not the first outage, probably not the last
Cloud dependence has bitten Bambu owners before. In August 2023, a cloud outage did not just block new jobs: after recovery, queued commands fired on their own and some idle printers started unattended prints, in some cases printing onto plates that still held finished parts. Bambu published a full investigation and has since added safeguards, and to be clear, nothing of that sort happened on July 20. But the pattern is the point: any cloud-routed printer is only as available as its cloud.
Bookmark the status page
Before restarting your router or re-flashing anything, check status.bambulab.com. It breaks "Printer Services" into binding, cloud printing, remote control, and live view, and it offers email and RSS subscriptions. If the fault is on Bambu's side, no amount of local troubleshooting will fix it.
The bottom line
Bambu's cloud went down for two hours and the internet noticed, but the printers themselves were fine the whole time. Keep a microSD card and reader (or, on H2/P2S/X2D, a USB stick) handy for the quick fix, and know where the LAN Only toggle lives for the permanent one. Ten minutes of setup today means the next outage costs you nothing but a shrug.
Common questions
Does a Bambu cloud outage stop a print that is already running?
No. Once a print has started, the job runs from the printer itself and does not need the cloud connection. The July 20, 2026 MQTT outage only prevented users from starting new print jobs; prints that were already running kept going.
Can Bambu Lab printers print without the cloud?
Yes, two ways. The quickest is exporting the sliced file from Bambu Studio to the microSD card or USB drive (depending on the model) and starting it from the printer screen, which needs no settings change. The permanent way is LAN mode, where Bambu Studio talks to the printer directly over your local network using the printer's 8-digit access code.
What do I lose in LAN-only mode?
The Bambu Handy app, starting prints remotely from outside your local network, and the cloud print history. Sending straight from MakerWorld also depends on the cloud. You can switch back to cloud mode at any time from the same settings menu.
Sources
Bambu Lab status page (status.bambulab.com) for the July 20 incident timeline, quoted times UTC, and the post-mortem posted there on July 30; Bambu Lab Wiki "How to enable LAN Mode on Bambu Lab printers" for LAN mode behavior, per-series menu paths, binding steps, and the X1 microSD requirement; Bambu Lab Wiki P1/A1 "How to print from SD card" manuals for the export workflow; Bambu Lab blog "Initial Investigation in the Bambu Cloud Temporary Outage" (Aug 2023) for the earlier incident; DownDetector via DesignTAXI for the report surge timing; Bambu Lab Wiki "How to Connect the Printer Using the Access Code" for binding by IP address and access code; Bambu Studio 2.8.2 release notes on GitHub (v02.08.02.60, August 14, 2026) for the automatic LAN fallback; Bambu Studio 2.7.1 release notes on GitHub (v02.07.01.57, June 1, 2026) for saved LAN connection information. Firmware version thresholds for the authorization system as documented in our OrcaSlicer article. We have not independently reproduced the outage behavior on every model; menu paths follow Bambu's official documentation.