Hacker Newsnew | past | comments | ask | show | jobs | submit | more reassess_blind's commentslogin

The status page is hosted on AWS Cloudfront, right? It sure looks like Cloudfront was overwhelmed by the traffic spike, which is a bit concerning. Hope we'll see a post from their side.


CloudFront has quotas[0] and they likely just hit those quota limits. To request higher quotas requires a service ticket. If they have access logs enabled in CloudFront they could see what the exact error was.

And since it seems this is hosted by Atlassian, this would be up to Atlassian.

[0] https://docs.aws.amazon.com/AmazonCloudFront/latest/Develope...


How do you plan on mitigating a DDoS on your own servers?


Alright kids, breathe...a DDoS attack isn't the end of the world, it's just the internet throwing a tantrum. If you really don't want to use a fancy protection provider, you can still act like a grown-up: get your datacenter to filter trash at the edge, announce a more specific prefix with BGP so you can shift traffic, drop junk with strict ACLs, and turn on basic rate limiting so bots get bored. You can also tune your kernel so it doesn't faint at SYN storms, and if the firehose gets too big, pop out a more specific BGP prefix from a backup path or secondary router so you can pull production away from the burning IP.


Very quickly you'll find this doesn't work. Your DC will just null your IP. You'll switch to a new one and the attackers will too, the DC will null that one. You won't win at this game unless you're a very sizeable organization or are just willing to wait the attackers out, they will get bored eventually.


> pop out a more specific BGP prefix from a backup path or secondary router so you can pull production away from the burning IP.

This won't help against carpet bombing.

The only workable solution for enterprises is a combination of on-prem and cloud mitigation. Cloud to get all the big swaths of mitigation and to keep your pipe flowing, and on-prem to mitigate specific attack vectors like state exhaustion.


I never claimed to be an enterprise, nor did I suggest this was the best option for them. Cheers!


Worrying about a DDoS on your tiny setup is like a brand-new dev stressing over how they'll handle a billion requests per second...cute, but not exactly a real-world problem for 99.99% of you. It's one of those internet boogeyman myths people love to panic about.


That may have been true before the age of LLMs, but now crawler bots bring down any website in their path.


You turn off the screen. They can't hurt you if you don't see them


You wait for it to stop.


That is not what mitigating means.


he'll politely ask them to stop


Well, no. If they are unreliable to the point of being an outlier when compared to the alternatives then people will switch. At this stage they’re not an outlier.


Maybe not, but they are approaching it. I wouldn't use it for anything funded with my own cash, I no longer recommend it as a first choice, but I'm not suggesting it gets replaced yet. It's somewhat in the 'legacy tech' category now in terms of how I perceive it and deal with it.


They are often promoted as bing more reliable.


If you need DDoS mitigation then you essentially need to rely on a third party. Every third party will have inevitable downtime. For many it’s just whether you’d prefer to be down while everyone else is down or not.


How do you mitigate large scale DDoS?


I don't, since my stuff is reachable only within the company network/VPN. If I needed to though, I would consult the BSI list of official DDOS mitigation services [0] and evaluate each one before deciding. I would not auto-pick Cloudflare.

[0] (German) https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Cyber-Si...


When the solution you pick inevitably has downtime too you’re in the same boat.

DDoS mitigation is one of those areas that an on-prem solution just isn’t well suited to solve.


Yeah, but people aren't using Cloudflare just for DDOS Mitigation. Some are running pretty much everything over it, from DNS to edge caching to load balancing and even hosting. That's what I oppose mainly.


Unless you are really big, onprem stuff would be 90% internal anyway. For everything public you'd host your hardware in a datacenter with better high speed connectivity. And pretty much every single datacenter I interacted with in the last 5 years does have a DDOS protection solution that you can order for your network.


Who wants to join me at the Winchester for a pint, and wait for this all to blow over?


Got some red on you...


I’ve been DDoS’d countless times running a small scale, uncontroversial SaaS. Without them I would’ve had countless downtime periods with really no other way to mitigate.


Some people’s “being who they are” doesn’t get them any friends, and they don’t understand why. They want to connect with people, but their outwards personality may be unintentionally grating, exhausting, tiring, etc.

Socials skills are “skills” like any other and if you aren’t getting the desired result with your current skill set, what better way to improve than purposeful practice?


How long ago? I’d be going for a refund or credit card coverage if you’ve got it.


I don't feel like they owe me a refund in principle, at the end of the day I paid for subscription-free software and they delivered it, and I'm happy to do that exchange. I just don't like the changes and the future direction and that I won't be receiving updates to the one I'm currently using.


Ah, I thought you’d paid a one off fee.


Correct, owning the business will almost always be a better financial deal than working for the business.


Which business? The majority of businesses fail and never turn a profit. A success like Amazon is the exception, not the rule.


The business the person I was responding to was referring to?

I’m aware of the difficulties of running a business. I’d still always prefer to own the business rather than work within it despite that risk, which is why I do.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: