Bambu Cloud Postmortem: What Third-Party Tools Can Still Do

Published Last updated

Short version

From November 9, 2026, Bambu Lab's cloud was flooded with requests to one endpoint, the list of print jobs: about 34 times the normal traffic within an hour, roughly 20 million requests a day at the peak. The source was a bug in version 2.3.0 of ha-bambulab, the community Home Assistant integration, which sent those requests under OrcaSlicer's name. Bambu blocked that identity, some users were affected, and ha-bambulab 2.4.0 fixed the bug on November 11. If you run the integration, update to 2.4.0 or newer; OrcaSlicer was not the cause. Bambu's postmortem of November 12 also restates its rules: third-party tools may keep reading printer status within reasonable limits, while starting prints, live video, binding and firmware updates go through Bambu Connect.

The factor 34 times, labeled Bambu cloud traffic in one hour, with the tag Postmortem and the date November 12, 2026
Bambu's figure for the rise in cloud traffic, from its postmortem of November 12, 2026.

What happened

On November 12, 2026, Bambu Lab posted a postmortem in its forum about “abnormal traffic” earlier that week. Requests to its cloud “surged roughly 34-fold in just one hour” and peaked at roughly 20 million requests a day, still growing. Almost all of them hit one endpoint, GET /v1/user-service/my/tasks, which returns the status of print jobs. They came from many home internet connections, and they carried the client identity of OrcaSlicer and an older version of Bambu's network plug-in.

At that pace, Bambu writes, the service was “only hours away” from becoming unavailable, which would have put everyday printing at risk for its users. It blocked the anomalous traffic after an urgent review. “Some users were affected while we adjusted the policy,” the post says, without saying how many or for how long.

Rise within one hour
about 34×
Peak, requests a day
about 20 million
First rise
Nov 9, 2026
Fix, ha-bambulab 2.4.0
Nov 11, 2026
Timeline from November 8 to 13, 2026: ha-bambulab 2.3.0 ships on November 8; from November 9 requests to Bambu's print job list climb under OrcaSlicer's identity; on November 10 Bambu asks OrcaSlicer and warns of a block; by November 11 Bambu has blocked the identity and asks ha-bambulab, which ships the fix in 2.4.0 the same day; Bambu publishes its postmortem on November 12; a 2.4.1 beta on November 13 adds the version number to the integration's user agentNov 8Nov 9Nov 10Nov 11Nov 12Nov 13ha-bambulabRequestsBambu12345671ha-bambulab 2.3.0 ships with a wider trigger for fetching the print job from the cloud2Requests to the print job list start to climb, under OrcaSlicer's identity3Bambu asks OrcaSlicer on GitHub and warns it will block the requests4Bambu has blocked the identity and asks ha-bambulab5ha-bambulab 2.4.0 reverts the change and sends its own user agent6Bambu publishes its postmortem in the forum7ha-bambulab 2.4.1 beta adds its version number to the user agentDay cells in UTC; the rise is drawn schematically Timeline from November 8 to 13, 2026: ha-bambulab 2.3.0 ships on November 8; from November 9 requests to Bambu's print job list climb under OrcaSlicer's identity; on November 10 Bambu asks OrcaSlicer and warns of a block; by November 11 Bambu has blocked the identity and asks ha-bambulab, which ships the fix in 2.4.0 the same day; Bambu publishes its postmortem on November 12; a 2.4.1 beta on November 13 adds the version number to the integration's user agent8910111213Novha-bambulabRequestsBambu12345671ha-bambulab 2.3.0 ships2Requests start to climb, under OrcaSlicer's name3Bambu asks OrcaSlicer, warns of a block4Bambu has blocked it, asks ha-bambulab5ha-bambulab 2.4.0 fixes it6Bambu's postmortem72.4.1 beta: version in the user agentDays in UTC; rise drawn schematically
Fig. 1Two days from the first rise to the fix. Bambu looked at OrcaSlicer first, because the requests carried its name; the trail led to the Home Assistant integration.
  • Dates in UTC, from the GitHub issues and releases and Bambu's forum post; the block date is the latest it can be (Bambu's issue of November 11 says the identity was already blocked).
  • Bambu gives no traffic curve, only the rise of about 34 times in one hour and the peak of about 20 million requests a day.

The order of events is public on GitHub. On November 10, Bambu opened an issue in the OrcaSlicer repository: requests from OrcaSlicer clients had risen at least 30-fold since the OrcaSlicer 2.5.0 release, and without a fix Bambu would “have no choice but to block these requests.” OrcaSlicer's maintainers traced the endpoint and found that OrcaSlicer asks for the task list in one place only, its Multi-device page, which is off by default. On November 11 one of them pointed to version 2.3.0 of ha-bambulab, and Bambu opened an issue there the same day.

The bug in ha-bambulab

ha-bambulab is the community integration that brings Bambu printers into Home Assistant; it connects through Bambu's cloud or in LAN mode. It is meant to ask the cloud for the current print job once per print. Bambu's issue shows what changed in 2.3.0, released November 8: the trigger for that request now also covered printers in the paused and finished states. A printer that stayed finished, with a job file the integration could not match, met the condition again on every status message it sent, and each time the integration requested the task list.

A maintainer confirmed it within a few hours: the change had turned “what should have been a one-time call per print” into a repeating one. The change was reverted, and the integration got its own user agentThe name a program sends with each web request to say what it is. Before 2.4.0, ha-bambulab sent the same identity as OrcaSlicer with Bambu's network plug-in.. Version 2.4.0 went out at 16:40 UTC on November 11, together with H3C support; its release notes call the fix critical and say the new user agent lets the integration connect again. A 2.4.1 beta on November 13 adds the integration's version number to that user agent.

Why OrcaSlicer was suspected first

The requests looked like OrcaSlicer because the integration presented itself as OrcaSlicer. Bambu's issue lists the headers it sent, among them X-BBL-Client-Name: OrcaSlicer and the user agent of version 01.09.05.01 of Bambu's network plug-in, and adds that other projects copy this identity too. So Bambu went to the OrcaSlicer team first, and the block applied to that identity, whichever program sent it. The OrcaSlicer maintainers and the ha-bambulab maintainer both say OrcaSlicer itself was not the cause.

Bambu's lesson in the postmortem is aimed at developers: third-party software should “use its own identifier and say who it is.” That gets a problem to the right project faster and keeps a block from catching unrelated users.

What third-party tools may still do

The postmortem also restates where Bambu draws the line for software it does not make. Monitoring stays open; actions that change what the printer does go through Bambu Connect, the desktop app that came with Bambu's authorization system in 2025. Table 1 puts the postmortem next to Bambu's wiki page on third-party integration.

Table 1. What third-party software may do with a Bambu printer, by Bambu's rules
FunctionBambu's ruleSource
Read status: temperature, position, speed, progressAllowed “within reasonable usage limits”; if the service is at risk, Bambu may rate-limit or pause accessPostmortem
Status pushes for tools like Home AssistantNot affected by the authorization systemWiki
Start a print from software other than Bambu StudioThrough Bambu Connect, over the cloud or LANPostmortem, wiki
Live video from the printer cameraNot for direct access; slicers can build in Bambu's current network plug-inPostmortem, wiki
Firmware updatesNot for direct access; the network plug-in or the microSD cardPostmortem, wiki
Bind or unbind the printerNot for direct accessPostmortem, wiki
Everything, in Developer ModeThird-party software works unchanged, but the printer runs in LAN mode only, without Bambu CloudWiki

Our take

Handled in the open, with a limit nobody can see

Bambu dealt with this one publicly: issues on GitHub, a fix within two days, a postmortem with numbers, and monitoring left open for tools like Home Assistant. The weak spot is “reasonable usage limits.” Bambu publishes no number, so a tool finds the limit when it gets blocked, and this week the block first landed on the wrong name. ha-bambulab also runs in LAN mode, which talks to the printer on your own network.

What to do now

  1. Home Assistant with ha-bambulab: updateInstall 2.4.0 or newer. Its release notes say the new user agent lets the integration connect to Bambu's cloud again.
  2. OrcaSlicer: nothing to changeIts maintainers and the ha-bambulab maintainer agree that OrcaSlicer was not the source.
  3. Cloud blocked or down againBambu's notes on the July 2026 outages report blocked print starts, not stopped prints, so a running print should keep going. Start new ones from the microSD card or switch to LAN mode, as in our cloud outage guide.
  4. Building a toolSend your own identifier, as Bambu asks, and request from the cloud only what your users need.

Sources

5 sources, including Bambu's forum postmortem and the GitHub issues at OrcaSlicer and ha-bambulab.

ShowHide
Title
Bambu Cloud Postmortem: What Third-Party Tools Can Still Do
Section
News
By
BambuHub editorial
Published
Last updated
Type
Cloud, software
Basis
Bambu's postmortem and the GitHub issues
Sources
Listed under the article
Page
Status
Not affiliated with Bambu Lab

More from BambuHub

All news