We are experiencing High Traffic

I often get this, using coalias for white-labelling the product, reached out to bubble’s support and coalias as well and no-one is able to gave me any answers and they basically drop the blame to one-another… does anyone have seen this issue as well and can someone let me know how can I resolve it… multiple clients are sending me this and can not launch until this is resolve, would highly appreciate some help on this, thanks.

I hate to be that guy but… I’t probably co-alias

I think so too, it always happens on my white-label domain, never on my main bubble app

This definitely isn’t a Bubble error message

Yeah… I think it’s the co-alias too :sweat_smile:

Maybe @gaimed can help!

Wonder what % of Bubble support tickets are due to plugins, extensions, and other 3rd party addons.

15.7%. Interestingly around 7.2% are for custom code.

After meeting with Coalias Support to investigate, they concluded that the issue is caused by Bubble triggering an HTTP 429 “Too Many Requests” rate limit.

Since we are on a Coalias Enterprise plan, we should be using enterprise routes. Previously, we were using dynamic routes (/∗), which was causing the rate-limiting error. Switching over to static routes seems to have resolved the issue for now. That said, I still need to reach out to Bubble support to investigate why their system is rate-limiting these requests.

This is happened to one my “dedicated” servers, due to multiple users login to the app at same time.

I got 3 options -

  1. Whitelist the IP Ranges to disable this check , Can’t predict user to login from a specific IP all time..
  2. Accept this new way of Life
  3. Bring your own cloudflare

We accepted option 2 :slight_smile:

Getting a Coalias dedicated plan only affects domain routing. You are still limited by your Bubble app’s plan. App’s in the shared cluster have tighter limits than a dedicated plan.

If Coalias’s routing is hitting your Bubble app with high traffic, expect to get an appropriate response from your Bubble app.

Can I suggest you use these guys instead?

A much more sensible pricing model and none metered billing, and proper reverse lookups.