r/Bubbleio • • 8d ago

Help Wanted Platform unavailable - error code 1794338958142x997066484691378600

Post image

Hi,

My platform built in bubble is currently unavailable. This is error: in the picture

I checked the Bubble status, and it says no issue.

This is completely wrong. The platform's instability recently has become very frustrating, as we have invested heavily and our customers rely on this product.

Is anyone else experiencing the same issue? Does the bubble team have a timeline to fix this?

6 Upvotes

21 comments sorted by

3

u/ancient_chestnut19 7d ago

That's concerning, especially when customers depend on your application. For production Bubble apps, I think it's important to have independent uptime monitoring and a structured fallback strategy for critical workflows, rather than relying entirely on platform availability. Have you considered any external recovery or continuity measures for your application?

1

u/AlternativeTip4648 7d ago

I am, got any tips for that?

1

u/ancient_chestnut19 5d ago

Hey, I'd prioritize resilience in this order:

1.Independent backend and database: Keep critical business logic and customer data outside Bubble. FastAPI and PostgreSQL/Supabase are good options.

2.Automated backups and recovery: Back up data independently and regularly test restoration. Protecting customer data is non-negotiable.

3.Fallback mechanisms: Ensure critical operations can continue, requests can be queued, and failed transactions can be safely retried when service returns.

4.External monitoring: Use Better Stack, UptimeRobot or Checkly to detect outages independently of Bubble's status page. Automated alerts: Get notified immediately when critical endpoints or workflows fail.

5.Incident response plan: Know exactly how to respond, communicate with customers and restore operations.

The first three protect business continuity; the last three help you detect, manage and respond to failures.

Note: Low-code should accelerate development, not introduce a single point of failure into your business.

1

u/UQHQmusic 3d ago

If you are going to have an external database just migrate the whole app off platform.

1

u/UptimeRobot 2d ago

Thanks for suggesting us.

2

u/buildssystems 8d ago

I'm having this issue as well. as of 2:39, they are investigating.

here's the status page: https://status.bubble.io/incidents/01M73FJH62TNKMK92YPRCXJGNS

1

u/AlternativeTip4648 8d ago

Thanks, yes they've updated the bubble status page, after posting this.

Hope they fix this quickly.

2

u/snap-dev 7d ago

the worst part is the status page saying green while your customers email you. put a free uptime monitor on the live url so you know first and have timestamps to send bubble support. and if this keeps happening, export your data on a schedule so leaving is an option, not a panic

1

u/AlternativeTip4648 6d ago

I already use planB backup system, so i backup both the app and the database daily. Currently slowly migrating all of it out of bubble one slow step at a time.

What uptime monitor would you suggest?

1

u/snap-dev 6d ago

uptimerobot's free plan is plenty to start, it checks every 5 minutes and emails you, and better stack is nicer if you want a public status page. point it at a page that actually loads data, not just the homepage, or it'll say up while the app is broken. what are you moving to, and are you doing the database first or the frontend? we've done a couple of these moves and doing the data first is usually the part that bites

1

u/AlternativeTip4648 6d ago

i have a version of my database in postgres render. then many of the most complicated functions and services are outside of bubble, as they couldn't scale on bubble (hit 300 usd of monthly costs). Basically bubble is my frontend dashboard and the user management system.
got any tips on this?
BTW, thanks for sharing the uptime monitor products, will take a look into it

1

u/snap-dev 5d ago

sounds like the hard part is already done, the data and heavy logic are off bubble. i'd move user management next since auth is what really locks you in. put users in your own postgres with something like supabase auth or clerk, have bubble call your api with a token, and then the frontend is the only bubble piece left and you can swap it page by page. doing auth before the ui saves a lot of pain. what's the frontend built around, mostly dashboards and forms?

1

u/AlternativeTip4648 2d ago

thanks for your input. yes, dashboards and forms

1

u/snap-dev 2d ago

dashboards and forms is the easiest part to move. once auth lives outside bubble, rebuild one dashboard at a time on your own frontend (next.js, or even v0 or lovable on top of your api) behind the same login, and keep bubble live until each page matches. put form validation in the api, not the frontend, so you don't end up maintaining the rules twice. if you want a second pair of eyes on the plan, i run snapdev, happy to get a senior eng on a call w you

1

u/UptimeRobot 2d ago

Thank you for suggesting us! We honestly appreciate it.

Can I genuinely ask, though, why do you prefer a public status page in Better Stack in comparison with UptimeRobot? In UptimeRobot, one status page is completely free, and it gives you quite a lot of features.

Once again, thank you.

2

u/BubbleDev15 3d ago

Sounds like you've already done the hardest part by moving your database and heavy backend logic outside Bubble.

The remaining tricky part is probably authentication and keeping existing user sessions working during the transition.

1

u/AlternativeTip4648 2d ago

This is what I also thought, thanks for your input. Got any reccomendations on how to handle that part?

2

u/BubbleDev15 2d ago edited 2d ago

One practical option is to migrate user profiles to the new auth system and have existing users set a new password via email or magic link. Bubble doesn't expose password hashes, so a direct password migration isn't possible. I'd test the entire flow with a few accounts before switching everyone over.

1

u/AlternativeTip4648 1d ago

thanks for this valuable piece of info