Those football playoffs are really getting out of hand…
Cloudflare Global Network experiencing issues
751–760 of 1001 posts
Re: Cloudflare Global Network experiencing issues
#752[dead]
Re: Cloudflare Global Network experiencing issues
#753and when i tell people they dont need cf for most of their sites they laugh at me. look whos laughing now. theyre down, im up
ahahahhaahah
Re: Cloudflare Global Network experiencing issues
#754I know this is bad, and some people's livelihood and lives rely on critical infrastructure, but when these things happen, I sometimes think GOOD!, let's all just take a breather for a minute yeh? Go outside.
Re: Cloudflare Global Network experiencing issues
#755[deleted]
Re: Cloudflare Global Network experiencing issues
#756Classic. I see issues. Vendor’s status page is all green. Go to HN to find the confirmation. Applies to AWS, GH, everyone. Edit: beautiful, this decentralised design of the internet.
I usually get notifications from the sales/CS team way before the status page/incident list has any blip. This time was not an exception
Re: Cloudflare Global Network experiencing issues
#757Those football playoffs are really getting out of hand… Ref: https://news.ycombinator.com/item?id=43157000
Good one!
Re: Cloudflare Global Network experiencing issues
#758Why are we seeing AWS, then Azure, then Cloudflare all going down just out of the blue? I know they go down occasionally, but it's typically not major outages like this...
Re: Cloudflare Global Network experiencing issues
#759[deleted]
Re: Cloudflare Global Network experiencing issues
#760Speaking of 5 9s, how would you achieve 5 9s for a basic CRUD app that doesn't need to scale, but still be globally accessible? No auth, micro services, email or 3rd party services. Just a classic backend connected to a db (any db tech, hosted wherever), that serves up some html.
It depends on the infrastructure you're running on. There was a post yesterday going fairly into depth how you do such calculations https://authress.io/knowledge-base/articles/2025/11/01/how-w...
You probably cannot achieve this with a single node, so you'll at least need to replicate it a few times to combat the normal 2-3 9s you get from a single node. But then you've got load balancers and dns, which can also serve as single point of failure, as seen with cloudflare.
Depending on the database type and choice, it varies. If you've got a single node of postgres, you can likely never achieve more than 2-3 9s (aws guarantees 3 9s for a multi-az RDS). But if you do multi-master cockroach etc, you can maybe achieve 5 9s just on the database layer, or using spanner. But you'll basically need to have 5 9s which means quite a bit of redundancy in all the layers going to and from your app and data. The database and DNS being the most difficult.
Reliable DNS provider with 5 9s of uptime guarantees -> multi-master load balancer each with 3 9s, -> each load balancer serving 3 or more apps each with 3 9s of availability, going to a database(s) with 5 9s.
This page from google shows their uptime guarantees for big tables, 3 9s for a single region with a cluster. 4 9s for multi cluster and 5 9s for multi region
https://docs.cloud.google.com/architecture/infra-reliability...
In general it doesn't matter really what you're running, it is all about redundancy. Whether that is instances, cloud vendor, region, zone etc.