Is Base44 down? Where to check its status, and what to do in an outage

The short version

To see whether Base44 is down right now, open Base44’s official status page: status.base44.com. It shows the current state of each part of the platform and the history of past incidents. You can subscribe to updates by email, phone, RSS or Slack.

If the status page says everything is working but your app isn’t, the problem is more likely in your app or your account: a recent change, credits that have run out, or a feature your plan doesn’t include. The checks below help you tell which, and what to do in either case.

Where to check Base44’s status

1. The status page. status.base44.com lists each component separately, as of October 2026: Application Preview, Billing, Builder, Data, Files & Images Serving, File Uploads, Hosting, Login, Platform, Published Applications and Website. A problem can hit one of them, such as Login or the Builder, while the rest work. The incident history shows past incidents and their updates. Base44’s troubleshooting guide tells you to check this page first.
2. Base44’s Discord. Base44’s docs point to its Discord community for reported outages.
3. Support. For a problem only you seem to have, submit a ticket with your app link, when it started and any error messages.
4. Developers: Base44’s developer docs also point to GitHub Discussions for questions about the CLI and backend.

Third-party “down detector” sites collect reports from users. They can hint that something is wrong, but they aren’t Base44’s own account of an incident.

Is it Base44 or your app?

Start with a quick test. Open your published app in a private browser window, on a different device or network if you can. Check the status page. Then see whether your other apps, and the editor’s preview, behave the same way. If everything is broken everywhere and the status page shows an incident, it’s Base44. If one app fails and the rest work, look at that app.

Base44’s troubleshooting documentation matches common symptoms to causes:

If something is wrong and there’s no clear error, Base44 suggests typing “Something is wrong” in the AI chat, which analyzes the app and suggests fixes. On the Free plan, automatic fixes use message credits, so don’t repeat them over and over.

If your app is slow rather than down, check whether it’s slow everywhere or only on certain pages. A platform-wide slowdown shows up across your apps and usually on the status page. One slow page often means that page loads a lot of data or runs something heavy, which you can ask the AI chat to look at.

What to do during an outage

1. Confirm it and subscribe. Check the status page, then subscribe to updates so you hear when it’s resolved.
2. Hold off on changes. Big edits, republishing or repeated automatic fixes during an incident can make it harder to tell later what broke and why.
3. Tell your users. A short note on your own channels, such as email, social media or a banner on your website, saves you a lot of support questions.
4. Afterwards, check your data and flows. Sign in, open your main pages, and check that recent records saved and that emails and scheduled jobs ran. On 20 August 2025, Israel Hayom reported that during an overnight outage, users saw 502 errors and Google sign-in problems and reported missing data. Base44 said at the time that the data would be restored.
5. Report anything still wrong. Send a support ticket with your app link, the time, what you see and any console errors.
6. Keep your own exports. Regular CSV exports of your important tables, plus a copy of your code if your plan includes it, mean a bad day can’t cost you your work. Our guide to exporting from Base44 shows how.

If outages, slowdowns or credit errors keep affecting a business-critical app, our guide to whether Base44 is production-ready covers the limits worth knowing before you scale.

Apps on your own hosting have their own outages

An app moved off Base44, onto your own hosting, doesn’t depend on Base44’s servers, so a Base44 incident doesn’t take it down. It does have its own dependencies. Your hosting provider, database, email provider and AI provider can each have incidents, and they publish their own status pages, such as Railway’s and Resend’s. You, or whoever looks after the app, are also the one who notices and responds.

During a move with Unbase44 there is one link back to Base44: each user’s first sign-in on the new app is checked against Base44 once, so that first sign-in needs Base44 to be reachable. After that, the new app checks passwords itself. Running your own app moves the responsibility for uptime to you; it doesn’t remove it. Our guide to self-hosting a Base44 app covers what that involves.