My production and some of bubbles extension pages were doing it too
Bubble.io con este error me obligo a sacar una actualización que estaba preparando hace días, ya que justo está en la revisión del nuevo index de mi página. Creo que es importante una pantalla de respaldo cuando las cosas se caen.
You could set up an uptime tracker. Either use a paid/freemium one or just a google sheet one, and then automatically send out a “issue acknowledgement” email/text when your site goes down.
Or maybe Bubble could have that as part of their higher end tiers if they don’t have that already. 
yeah, my anti-virus is detecting it too.
Yes, my firewall appears to now be blocking bubble.
At least that appears to be the problem as I can no longer even establish a connection through my computer. I’ve tried clearing cache, cookies, and restarting with no success.
Attempts to visit bubble.io, and my app domain, won’t even establish a connection.
you can subscribe to outages here Bubble Status
“Secure Connection Failed” App and Editor still down for me
For people reporting that their firewall and antivirus is detecting issues with Bubble, mind sharing the specific vendor you are using? We’ll follow up and see if we can Bubble removed from whatever block list that vendor is using.
avast was catching it 5 minutes ago, but no longer. It just says
Secure Connection Failed
An error occurred during a connection to cbuspics.com. PR_CONNECT_RESET_ERROR
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
2 Likes
Thanks!
We seem to be good globally right now – we’re looking here: VirusTotal
… so hoping this clears up on its own as vendors update their own caches. Still looking into it though
@josh I am using AVAST.
Anyway, again, we’re incredibly sorry about this – this has been probably the worst two weeks in our history in terms of downtime. The incidents today seem to have been a result of someone maliciously trying to take us down: a DDoS attack a few hours ago, followed by someone reporting us to CloudFlare as phishing. We are talking to our account reps at CloudFlare to understand how this happened, since it’s a little surprising to us that our entire site got marked as a phishing site given that we’re a fairly large customer. We’re also looking into changes we can make to our caching infrastructure that would have allowed us to recover faster; some of the extended downtime was because the phishing warning page got cached at various levels of our stack, and we had to flush it out before things started working again.
We are putting a pause on routine code deployments temporarily while we put energy into shoring up reliability, since this level of downtime is not acceptable to us and we understand it erodes your trust in Bubble as a place to build your business
28 Likes
me too. It still detects it. Already sent an email to the devs.
We’ve filled out Avast’s form here: False Positive File Form. If anyone knows a faster way of getting to their attention, we’d be interested – we don’t have any contacts at Avast
2 Likes
Appreciate that message Josh. I know how hard it is to be a founder and deal with these issues - especially today’s issues that weren’t your fault. Love what Bubble has enabled me to do and look forward to continuing building on here.
6 Likes
Have the dedicated plans also been affected this time?
When I turn my avast off, it just says the site can’t be reached.
Someone probably had some text on their site that was pro-Trump so bubble got cancelled. 
1 Like
Mine appears to be back up (with avast running) Thanks for being on top of it.