Bambu Lab Outage History

20 incidents recorded over the last 365 days, 11 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Bambu Lab status100.00% uptime history

Every Recorded Bambu Lab Incident

Bambu Lab incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 27, 2026Intermittent timeouts affecting printing services due to AWS regional network instabilityBetween 00:30 and 01:07 UTC on September 27, 2026, network instability in an AWS region caused intermittent timeouts for printing and certain related operations. This issue was limited in scope—only a small fraction of…-228 minResolved
Sep 11, 2026Model loading errors on MakerWorldThe root cause has been identified as an abnormality in a middleware service, which caused timeouts and related errors for some MakerWorld features. This incident affected users accessing MakerWorld through web browser…5h 19mResolved
Aug 20, 2026Some of our store sites are currently experiencing issuesThis incident has been resolved.8h 45mResolved
Aug 11, 2026Scheduled Maintenance for ForumThe scheduled maintenance has been completed.30 minScheduled
Aug 5, 2026Scheduled Maintenance for AU StoreThe scheduled maintenance has been completed.1h 0mScheduled
Jul 31, 2026Scheduled Maintenance for UK StoreThe scheduled maintenance has been completed.1h 0mScheduled
Jul 28, 2026Scheduled Maintenance for EU StoreThe scheduled maintenance has been completed.1h 0mScheduled
Jul 24, 2026AWS Service DisruptionThis incident has been resolved.2h 21mResolved
Jul 23, 2026Scheduled Maintenance for JP StoreThe scheduled maintenance has been completed.1h 0mScheduled
Jul 23, 2026Scheduled Maintenance for CA & US StoreThe scheduled maintenance has been completed.1h 0mScheduled
Jul 20, 2026MQTT service disruption preventing users from starting prints (recurring)#### Summary On 2026-07-20, our MQTT device-connectivity service experienced two connection disruptions originating from the same root cause. A single node in the service cluster developed intermittent network…9h 31mResolved
Jul 20, 2026MQTT service disruption preventing users from starting printsThis incident has been resolved.16 minResolved
Jul 2, 2026ISP Network Disruption in Parts of Europe Impacting Cloud Service AccessThis incident has been resolved.3h 25mResolved
Jun 22, 2026Maintenance for Bambu Lab Community ForumThe scheduled maintenance has been completed.30 minScheduled
May 19, 2026Europe & South Africa → AWS Network IssuesThe issue has been fully resolved. It has been confirmed as a network configuration issue on the carrier side. All affected regions have returned to normal. We apologize for any inconvenience caused.4h 13mResolved
May 10, 2026Network Issues Affecting Bambu Lab Cloud Services in Parts of EuropeThis incident has been resolved.12h 4mResolved
Apr 21, 2026Maintenance for Bambu Lab Community ForumThe scheduled maintenance has been completed.1h 0mScheduled
Jan 8, 2026Maintenance for Bambu Lab Community ForumThe scheduled maintenance has been completed.1h 0mScheduled
Dec 5, 2025Network OutageThe incident has been resolved.47 minResolved
Nov 18, 2025Partial Connectivity Issues for Users in Some RegionsThis incident has been resolved.13h 15mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Bambu Lab incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Bambu Lab Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Bambu Lab acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Bambu Lab outage in this window ran 13h 15m, against a mean recovery of 3h 35m. If you depend on Bambu Lab in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.