what do you mean?… you can have your own status page too - but you’d have to update that?
Its back online for my clients here.
Quite a fast response. *I would still rather pay for a tiny dedicated/vps when possible.
1 Like
I didn’t know this was possible. Could you please enlighten us on how to do this?
Make it known your service has a status page, just like Bubble has made it know that they have their own. Then when your customers experience downtime, they can check your status page for updates assuming you’re keeping that up to date.
I see. I thought you were referring to being able to edit and design the actual downtime message
No, that’s some generic error message
It’s not about having our own status page. Some of us are building under the illusion that we own our apps, when really, we don’t. We’re paying for that illusion (which is part of the appeal of Bubble), but when something breaks, it’s our businesses and our users who take the hit.
When my clients see “report this code,” they send it to me and I can do absolutely nothing with it. I check the forum, see Bubble are rolling back a bad deploy, and by then there’s no point in me sending anything.
I usually just tell my clients, “we’re doing some quick updates on a Friday night (here in the UK), bear with us,”.
(sorry deleted messages were trying to upload the screenshot)
This is pretty much the case with any SaaS app unless you’re hosting it yourself in your own data center that you control. It’s just a layer of abstraction.
Your app is hosted by Bubble which is hosted by AWS.
So in cases like this, the only thing you can really say is “Our host is experiencing an outage and are working to resolve it” since it’s not something you control directly. This is pretty much the same case as any other services with a dependency on another service. Similar to the AWS outage we saw last week, the same principle applies - all these other services blamed AWS because that was the root of the issue. Similarly, here, the host is Bubble.
1 Like
Look, I totally agree, and as you can see from my reply to my user, I’m not expecting 100% uptime or pretending this stuff doesn’t happen. I’m just suggesting that the response page reflects our position a bit better.
Right now, the default message makes it look like it’s an issue on our end, and that’s what my users see. Just a suggestion 
BTW I’m a big bubble advocate
99% uptime is really, really bad. In case anyone is thinking dedicated solves this, we were down for 21 minutes this afternoon. I’m not entirely sure what dedicated really even means anymore.
4 Likes
Yeah… agreed… they need an SLA at least for dedicated lol so there’s consequences to downtime
This. I’m glad all the scripts and everything worked well for the forum banners 
but we have a real business with real consequences when these events occur.
1 Like
You can communicate to your customer that it’s an issue with your host. You don’t have to say it’s your issue, sure it inherently affects your service, but you’re not the root cause
Here’s an example: App outage - TicketingNest Status
I delayed them knowing bubble had this sorted, so in a sense I did what you are saying! But my point is that the page my users saw tonight could do with a better message, IMO. This isn’t an attack on Bubble, it’s a suggestion from a long-time ‘bubbler’ with a lot of users.
Look, I build, but I’m not an agency or a ‘Bubble developer’. I’m the kind of person Bubble appeals to… a non-developer who can build an app, turn it into a business, and actually make money from it. So I might be wrong, but I figured this feedback could be useful from a business owner’s perspective. Wasn’t after an argument or an issue. Just feedback
1 Like
Did you have to manually update the statuses for the link you shared? It seemed very close to what Bubble posted on their status page, but translated in a way that is better for us as App owners that were affected by Bubble?
Just curious if you had to manually do this or if there is an automated solution that could be used and then just add a link, but I guess we are still at the mercy of Bubble since they control the error messaging that our end users see when they go to our website.
How would your users know to go to that link that you have instead of the url they were intending to go to?
1 Like
Not fully manual. The first message was automated. I use incident.io (coincidentally, Bubble does too now), and I have alarms set up on New Relic where if it detects downtime in a specific number of locations around the globe, it sets off an alarm.
That alarm triggers an incident.io incident that pages me through various methods (critical alert push, phone call, text, slack, email, etc). Then I acknowledge it and usually investigate to see what’s going on - in this case, it was Bubble being down, so I published an incident update with that info and monitored what was going on.
Similar to how, when Bubble goes down, we go to status.bubble.io or the forum - people usually Google Bubble down or Bubble Status, something like that, and the first thing that pops up is Bubble’s status page. Pretty much the same here, but in my support email auto responder, I also link the status page there too
99% sounds good until you realize it’s about 4 days a year
1 Like
Fwiw this is basically the only downtime our dedicated clients have had in the last year
1 Like
Same here @georgecollier
That’s great, however, that has not been our experience. We’ve had multiple outages.
3 Likes