Base44 Outage History
5 incidents recorded over the last 365 days, 5 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.
Every Recorded Base44 Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 13, 2026 | Ongoing incidentWe’re performing maintenance to improve our services. Most apps are working normally. During this time, some apps may load more slowly. Pages with a lot of data may also briefly show a “too many requests” message, so… | 19h 12m | Resolved |
| Oct 13, 2026 | Ongoing incidentWe’re seeing intermittent slowness across the platform. Building and published apps may load slowly at times. Our team is working on it. | 2h 34m | Resolved |
| Sep 9, 2026 | Ongoing incidentSome users are unable to load the app preview in the editor or reach published apps on *.base44.app. The preview may stay on "Loading your app". This depends on the user's network and does not affect all users. Your… | 44 min | Resolved |
| Aug 20, 2026 | Ongoing incidentWe are investigating a current outage affecting our platform. Our team is actively working to find the cause and restore normal service as quickly as possible. | 4 min | Resolved |
| Aug 17, 2026 | Ongoing incidentWe're investigating elevated errors affecting the creation and startup of apps in the platform — some users may experience failures or significant delays when opening, editing, or previewing apps, and we're actively… | 56 min | Resolved |
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 Base44 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 Base44 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 Base44 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 Base44 outage in this window ran 19h 12m, against a mean recovery of 4h 42m. If you depend on Base44 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.