AWS North Virginia data center outage – resolved

https://www.cnbc.com/2026/05/08/aws-outage-data-center-fanduel-coinbase.html

by christhecaribou • 3 months ago

267 198 3 months ago

cnbc.com

https://health.aws.amazon.com/health/status?t=2026-05-07

https://www.theregister.com/off-prem/2026/05/08/aws-warns-of...

https://www.reuters.com/business/retail-consumer/amazon-clou...

merek2• 3 months ago

AWS EC2 outage in use1-az4 (us-east-1)

https://news.ycombinator.com/item?id=48057294

tcp_handshaker• 3 months ago

I bet post-mortem will say vibe coding confused fahrenheit and celsius, we run too hot...

geodel• 2 months ago

Now I totally understand the issue. I will set temperature 70K. Using SI unit of temperature is the best practice.

fabian2k2• 3 months ago

I thought cooling was pretty much pre-planned in any data center, and you simply don't install more stuff than you can cool?

So did some cooling equipment fail here or was there an external reason for the overheating? Or does Amazon overbook the cooling in their data centers?

DevelopingElk• 3 months ago

One of the data center's cooling loops broke.

bdangubic• 3 months ago

No backups?

AdamJacobMuller6• 3 months ago

This is almost definitely an issue of equipment failure.

Cooling in datacenters is like everything else both over and under provisioned.

It's overprovisioned in the sense that the big heat exchange units are N+1 (or in very critical and smaller load facilities 2N/3N). This is done because you need to regularly take these down for maintenance work and they have a relatively high failure rate compared to traditional DC components and require mechanical repairs that require specialized labor and long lead times. In a bigger facility its not uncommon to have cooling be N+3 or more when N becomes a bigger number because you're effectively always servicing something or have something down waiting for a blower assembly which needs to be literally made by a machinist with a lathe because that part doesn't exist anymore but that's still cheaper than replacing the whole unit.

The system are also under-provisioned in the sense that if every compute capacity in the facility suddenly went from average power draw to 100% power draw you would overload the cooling capacity, you would also commonly overload things in the electrical and other paths too. Over provisioning is just the nature of the industry.

In general neither of these things poses a real problem because compute loads don't spike to 100% of capacity and when they do spike they don't spike for terribly long and nobody builds facilities on a knife-edge of cooling or power capacity.

The problem comes when you have the intersection of multiple events.

You designed your cooling system to handle 200% of average load which is great because you have lots of headroom for maintenance/outages.

Repair guy comes on Tuesday to do work on a unit and finds a bad bearing, has to get it from the next state over so he leaves the unit off overnight to not risk damaging the whole fan assembly (which would take weeks to fabricate).

The two adjacent cooling units are now working JUST A BIT harder to compensate and one of them also had a motor which was just slightly imbalanced or a fuse which was loose and warming up a bit and now with an increased duty cycle that thing which worked fine for years goes pop.

Now you're minus two units in an N+2 facility. Not really terrible, remember you designed for 200% of average load.

That 3rd unit on the other side of the first failed unit, now under way more load, also has a fault. You're now minus 3 in a N+2 facility.

Still, not catastrophic because really you designed for 200% of average load.

The thing is, it's now 4AM, the onsite ops guy can't fix these faults and needs to call the vendor who doesn't wake up till 7AM and won't be onsite till 9.

Your load starts ramping up.

Everything up above happens daily in some datacenter in the USA. It happens in every datacenter probably once a year.

What happens next is the confluence of events which puts you in the news.

One of your bigger customers decides now is a great time to start a huge batch processing job. Some fintech wants to run a huge model before market open or some oil firm wants to do some quick analysis of a new field.

They spin up 10000 new VMs.

Normally, this is fine, you have the spare capacity.

But, remember, you planned for 200% of AVERAGE cooling capacity and this is not nodes which are busy but not terribly busy, these are nodes doing intense optimized number crunching work which means they draw max power and thus expel max waste heat.

Not only has your load in terms of aggregate number of machines spiked but their waste heat impact is also greater on average.

Boom, cascading failure, your cooling is now N-4.

Server fans start ramping up faster which consumes more power.

Your cooling is now N-5.

Alarms are blaring all over the place.

Safeties on the cooling units start to trip as they exceed their load and refrigerant pressures rise.

Your cooling is now N-6.

Your cooling is now N-7.

Your cooling is now 0.

fabian2k2• 3 months ago

I'd expect someone like AWS to just throttle machines before overloading their cooling. Because they probably can do that, while e.g. a data center that just rents the space can't really throttle their customers nicely.

foota• 3 months ago

Shouldn't there be a feedback system here preventing the scheduling of loads when cooling is degraded?

PunchyHamster3• 3 months ago

The cooling units dont fail just because they get to 100% duty cycle. That's pretty much "normal operation", you just get... higher efficiency coz the cooling side is warmer

minimaltom2• 2 months ago

This is a great writeup! thank you!!

Reminds when i did noogler training back in the day and one of the talks described a cascading failure at a datacenter, starting with a cat which was too curious near a power conditioner, and briefly conducted

wombatpm• 2 months ago

I would have thought with all the data centers being built the parts for cooling systems would be standardized with replacements available from Grainger immediately.

dtjohnnymonkey• 2 months ago

I could totally get into “Ops Thriller” genre of novels like this.

lukeify• 2 months ago

This is written beautifully. It's like a much more inconsequential variant of Chernobyl.

Andys• 2 months ago

I worked in a DC that had multiple redundant chillers on the roof, and multiple redundant coolers on each floor, but the whole building's cooling failed at once when the water lines failed somehow.

They didn't say how, but apparently the pipes between each floor and the roof were not redundant. It took almost 24 hours to fix.

el_benhameen• 2 months ago

Good listen on similar topics here: https://signalsandthreads.com/the-thermodynamics-of-trading/

Havoc• 3 months ago

Could someone explain to me why they don't build these things near oceans? Like nuclear plants that need plenty cooling capacity too

Two loop cycle with heat exchanger to get rid of the heat

sheept• 3 months ago

This is just a guess, but land near oceans is more expensive/populated, and water is comparatively cheap

kinow• 3 months ago

I had a class in my masters about data centers (HPC Infrastructures). The professor was using some data centers somewhere in the middle of USA, in an area with hot weather as example. He compared that with ideal scenario (weather, power source, etc.).

In one of the slides, there were factors that influence the decision of where to build a data center, and several of the items involved finding a place with enough space and skilled people to work at this data center. He also commented sometimes there is politics involved on choosing the place for a next data center.

ikr678• 3 months ago

Off the top of my head: Ocean levels of salt in a water system are much more expensive to maintain (even the secondary loop).

Coastal land much more expensive. If you go to a remote coastal site, you probably won't have as good access to power.

Coastal sites usually exposed to more severe weather events.

Other fun unpredicatble things eg-Diablo Canyon nuclear facility has had issues with debris and jellyfish migration blocking their saltwater cooling intake.

https://www.nbcnews.com/news/world/diablo-canyon-nuclear-pla...

idiotsecant2• 2 months ago

And oysters / mussels / clams / every other creature that starts small and turns calcium into brick finds your cooling system to be a delightful place to raise a family, especially in delicate heat exchangers with small easily blockable passages.

mandevil• 3 months ago

So Ashburn VA is a datacenter hub because the very first non-government Internet Exchange Point (IXP) anywhere in the world was there (https://en.wikipedia.org/wiki/MAE-East). Back in the 1990's something like half of all internet traffic all over the world hit MAE-East. That in turn made AWS put their first region there (us-east-1 preceded eu-west-1 by 2 years and us-west-1 by 3 years). Then because there were lots of people who knew how to build DC's- and lots of vendors who knew how to supply them- the Dulles Corridor became a major hub for lots of companies datacenters. For AWS, because us-east-1 was the first, it's by far the most gnarly and weird- and a lot of control planes for other AWS services end up relying on it. Which is why it goes down more often than other regions, and when it does go down it makes national news, unlike, say, eu-south-2 in Spain.

But NoVA is basically the same sort of economic cluster that Paul Krugman won his Nobel Prize in Economics for studying, just for datacenters, not factories.

everfrustrated2• 2 months ago

The underlying reason is more that by being in us east coast you have about equal latency for customers in us west coast and Europe. That's a very large population covered from a single site.

If you're building a single datacenter site this is where you start building first.

ckozlowski• 2 months ago

Well said. I'll also add, that with these networks, the sooner you can get traffic off your network the better. There's strong incentive to have your datacenter near these peering points. And since MAE-East was the first, it's been the largest as it's been snowballing the oldest. AOL's HQ was here, Equinix built their peering point soon after MAE-East, etc.

There's a great read about the whole area here: https://www.amazon.com/Internet-Alley-Technology-1945-2005-I...

As for AWS, I often see it repeated that the DCs are the oldest and therefor in disrepair. That's not true; many of the first ones have since been replaced. But there are services that are located here and only here.

But I'll also add, a lot of customers default to using US-East-1 without considering others, and too many deploy in only one AZ. Part of this is AWS's fault as their new services often launch in US-East-1 and West-2 first, so customers go to East-1 to get the new features first.

Speaking as one who was with AWS for 10 years as a TAM and Well-Architected contributor, I saw a lot of customers who didn't design with too much resiliency in mind, and so they get adversely affected when east-1 has an issue (either regional or AZ). The other regions have their fair bit of issues as well. It's not so much that east-1 necessarily fails more than the others, it's that it has so many AZs and so many workloads that people notice it more.

jjmarr• 3 months ago

Oceans have salt. Saltwater is bad for electronics beyond normal water. You also need a sufficient level of water depth otherwise it'll warm to surface temperature. It also needs to be price-competitive with traditional evaporative cooling.

Toronto is the textbook example of this working. It's on a freshwater lake that is deep relatively close to the shore, and the downtown has expensive real estate blocking traditional methods.

https://en.wikipedia.org/wiki/Deep_Lake_Water_Cooling_System

dpe82• 3 months ago

In a proper 2-loop cooling system, the primary loop (with direct electronics contact) and secondary loop (with seawater/external cooling source) are hydraulically isolated by a heat exchanger. The salt water or whatever never gets anywhere near the electronics.

arjie• 3 months ago

Amusingly I've been part of two critical downtime heating incidents at two different datacenters: one was when Hosting.com's SOMA datacenter got so hot that they were using hoses on the roof to cool it down; and the second one was when Alibaba's Chai Wan datacenter got so hot everything running there went down, including the control plane. So I imagine the proximity to the ocean does not yield any additional advantage in terms of emergency heat sinking. You have x capacity to pump heat out and it doesn't matter if you're next to the sea or in the middle of Nebraska because your entire system needs to be built to be rated for some performance.

PunchyHamster3• 3 months ago

yeah but capacity is easier/cheaper to build/overbuild if you can access cold-ish water at all times

tempaccount5050• 3 months ago

Lots of proposals to build them near Lake Michigan recently but the residents of Wisconsin only want auto parts stores and paper mills. They've been completely demonized. Cities and counties are passing no data center laws even though it's the perfect place for it.

Leonard_of_Q2• 2 months ago

Paper mills need a lot of heat energy to run the processes. Data centres produce a lot of heat. Sounds like a good combination?

Cold water -> data centre cooling loop - > warm water -> paper mill with heat pumps to transform low-grade heat into the required temperatures -> profit

quantumet• 2 months ago

They are, sometimes. Google built this one in Finland in 2011 at the site of an old paper mill, which was already set up to draw water from the Baltic Sea (which isn't as salty as the Atlantic is, but still not fresh water):

https://datacenters.google/locations/hamina-finland/

Using a cooling system with seawater from the Bay of Finland and a new offsite heat recovery facility, our Hamina data centre is at the forefront of progressing our sustainability and energy-efficiency efforts.

dopa42365• 2 months ago

Humidity and corrosion, it's a trade-off (pick your poison).

tailscaler2026• 3 months ago

us-east-1 is down? shocking! stop putting SPOF services there. this location has had frequent issues for the past 15 years.

unethical_ban• 2 months ago

This is correct... unless there is a specific requirement to be in that location for some kind of IXP or ultra low latency, I can't imagine putting mission-critical things in only that region.

cmiles82• 2 months ago

AWS’s US-East 1 continues to be the Achilles heel of the Internet.

And while yes building across multiple regions and AZs is a thing, AWS has had a string of issues where US-East 1 has broader impacts, which makes things far less redundant and resilient than AWS implies.

keeganpoppen• 2 months ago

anecdotally (well, more "second-hand-ly i heard that..." it sounds like there were some carry-on effects on us-east-2 as a result of people migrating over from us-east-1, so, yeah... kinda hilarious how the multiple region / AZ thing is just so plainly a façade, but yet we all seem to just collectively believe in it as an article of faith in the Cloud Religion... or whatever...

qaq• 2 months ago

It's no magic given the size of us-east-1 there is no spare capacity to absorb all the workloads

cherioo• 2 months ago

Is it really failing more, or we just don’t hear about failure happening elsewhere?

Last i heard azure outage it wasn’t even on HN frontpage

stingraycharles• 2 months ago

It really is failing more, and it’s well known amongst industry experts. It’s the oldest, largest, and most utilized region of AWS.

I’ve heard people say that the underlying physical infrastructure is older, but I think that’s a bit of speculation, although reasonable. The current outage is attributed to a “thermal event”, which does indeed suggest underlying physical hardware.

It’s also the most complex region for AWS themselves, as it’s the “control pad” for many of their global services.

9999000009993• 2 months ago

Too many people are using it.

In fantasy magic dream land loads are distributed evenly across different cloud providers.

A single point of failure doesn't exist.

It worked out with my first girlfriend. The twins are fluent in English and Korean. They know when deploying a large scale service to not only depends on AWS.

Healthcare in the US is affordable.

All types of magical stuff exist here.

But no. It's another day. AWS US-East 1 can take town most of the internet.

afro88• 2 months ago

Core AWS services use it too. Even if you are hosted in another region, you can still be affected by a US-East 1 outage

echelon_musk• 2 months ago

It worked out with my first girlfriend. The twins are fluent in English and Korean.

You were dating twins as a form of redundancy?!

Eridrus3• 2 months ago

People say this, but this this was just a single AZ, and in the last 3 years of running my startup mostly out of use-1, and we've only had one regional outage, and even that was partial, with most instances uneffected.

And honestly, everybody else's stuff is in use-1, so at least your failures are correlated with your customers lol.

linsomniac• 2 months ago

And honestly, everybody else's stuff is in use-1

Yeah, but why put your eggs in that basket? I moved all our services from east to west/oregon a decade ago and haven't looked back.

grogenaut4• 2 months ago

none of my stuff is in us-east-1. I chose that specifically 15 years ago. Been a great decision.

nilamo• 2 months ago

And honestly, everybody else's stuff is in use-1, so at least your failures are correlated with your customers lol.

Is it not a selling point to be able to say "we're still up while out competitors are down"?

skywhopper2• 2 months ago

It wasn’t even all of a single AZ. None of my resources in use1-az4 had any issues. The most annoying thing was the 20 notifications we got saying “it’s not all fixed yet” every hour.

dlenski9• 2 months ago

The idea that AWS's services are fully regionalized or isolated has always been a myth.

All the identity and access services for the public cloud outside of China (aka "IAM for the aws partition" to employees) are centralized in us-east-1. This centralization is essentially necessary in order to have a cohesive view of an account, its billing, and its permissions.

And IAM is not a wholly independent software stack: they rely on DynamoDB and a few other services, which in turn have a circular dependency on IAM.

During us-east-1 outages it's sometimes possible to continue using existing auth tokens or sessions in other regions, while not possible to grant new ones. When I worked there, I remember at least one case where my team's on-calls were advised not to close ssh sessions or AWS console browser tabs, for fear that we'd be locked out until the outage was over.

sidewndr462• 2 months ago

Isn't this kind of circular dependency what lead to extended downtime a while back?

stephenr• 2 months ago

And IAM is not a wholly independent software stack: they rely on DynamoDB and a few other services, which in turn have a circular dependency on IAM.

When you dogfood your own Rube Goldberg machine.

zaphirplane3• 2 months ago

Services outside of us-east-1 don’t call us-east-1 for IAM data plane thou right ?

Roark662• 2 months ago

Anyone who thinks one cloud provider will provide them full resilience is fooling themselves. You need multicloud for true high availability.

But then you want to use the same stack across providers and all the proprietary technologies (even hidden from you with things like terraform) are suddenly loosing their luster.

myroon5• 2 months ago

outside of China

[Nitpick] There are a few more AWS partitions like GovCloud:

https://jasonbutz.info/2023/07/aws-partitions/

jmsgwd• 2 months ago

The idea that AWS's services are fully regionalized or isolated has always been a myth.

This is highly misleading. It's true that there's a handful of global AWS services - but only their control planes operate from a single region (e.g. us-east-1). Their data planes are regionally isolated or globally distributed.[1]

The only time you'd normally use a service control plane is to deploy changes, e.g. when you create, read, update or delete service resources or update configuration during a change window.

Workloads should be designed for "static stability", as recommended by AWS.[2] A statically stable workload only depends upon the data planes of the services it uses at runtime. Statically stable workloads are designed to continue operating as normal even if there's a service event impairing one or more control planes (including for global services).

During us-east-1 outages it's sometimes possible to continue using existing auth tokens or sessions in other regions, while not possible to grant new ones.

This is just plain wrong! The IAM Security Token Service (STS), which grants IAM tokens, is a data plane-only service and runs independently in each region [3]. The IAM data plane, which enforces access control, is also regional.

If the IAM control plane is impaired, you might not be able to create new IAM roles (a control plane operation) - but you can continue generating and using temporary credentials for existing IAM roles (data plane operations) within the region your workload is running in. This allows statically stable workloads to continue using IAM without interruption.

[1] https://docs.aws.amazon.com/whitepapers/latest/aws-fault-iso...

"Global AWS services still follow the conventional AWS design pattern of separating the control plane and data plane in order to achieve static stability. The significant difference for most global services is that their control plane is hosted in a single AWS Region, while their data plane is globally distributed."

[2] https://docs.aws.amazon.com/whitepapers/latest/aws-fault-iso...

"...eliminating dependencies on control planes (the APIs that implement changes to resources) in your recovery path helps produce more resilient workloads."

[3] https://docs.aws.amazon.com/whitepapers/latest/aws-fault-iso...

"STS is a data plane-only service that is separate from IAM, and does not depend on the IAM control plane."

master_crab• 2 months ago

IAM isn’t even really the most painful dependency. Route53 is. The control plane only runs out of use1.

Better make sure the only DNS operations you run during an outage are data plane queries and health check failovers.

ohnei• 2 months ago

I've always been impressed by Amazon's ability to present the shittiest experience possible and imply the blame is with things like isolation that they don't really provide.

y3ahd0g• 2 months ago

No. This is nonsense.

Some SaaS apps had issues.

The Internet was fine.

This is physical reality. The internet was designed to route around this.

Just because some app devs do a lazy job doesn't mean the entire infrastructure as designed is garbage.

Just because some app devs are over reliant on a single cloud service doesn't mean the Internet is broken.

dehrmann• 2 months ago

building across multiple regions and AZs is a thing

If you do this for resiliency, be prepared to pay the capacity tax (2 regions means 2x capacity, 3 regions means 1.5x), have the machines already running in a multi-region setup (don't expect to be able to spin up instances or even get capacity during an outage), and ready to deal with the added complexity of multi-region hosting.

coredog64• 2 months ago

There’s all kinds of fun pitfalls with multi-AZ. Like you can create RDS subnets across multiple AZs but then you can’t remove an AZ. Which really sucks when your core database covers all 5 us-east-1 AZs and randomly can’t failover because you picked an instance type that use1-az4 can’t host.

nikcub• 2 months ago

both realtime markets where multi-AZ is hard?

kikimora• 2 months ago

Order books had to run on a single server for performance reasons. Similarly a realtime multiplayer game.

aurareturn• 2 months ago

These things are dangerous. Someone who can take AWS down such as an employee can place a bet.

These bets aren’t as innocent as they seem because the bettors can often influence or change the outcome.

shimman• 2 months ago

It's a good thing big tech hires for ethical engineers and not ones that only care about money or social status.

zaphirplane3• 2 months ago

You forgot the /s

morgoths_bane• 2 months ago

Thankfully their leadership is leading the way in ethics since inception, so I am confident that no such shenanigans will ever take place. I may even bet on this.

dennis_jeeves2• 2 months ago

Leaders with a vision for all of us.

Imustaskforhelp• 2 months ago

These things are dangerous. Someone who can take AWS down such as an employee can place a bet.

Imagine if the betting website itself shuts down because AWS is down. (half joking I suppose though)

These bets aren’t as innocent as they seem because the bettors can often influence or change the outcome.

Overall I agree with your statement that these betting markets also are able to incentivize a lot of insider trading and one can say negative scenarios as this has given them an incentive to capitalize on that.

ninjalanternshk2• 2 months ago

This is my retirement plan.

Get a job where I can affect something significant, mortgage everything I own to bet on it, then break it (get fired) and take the money and run.

noosphr• 2 months ago

Jokes on you. All betting sites are based on US-East1.

ptdorf2• 2 months ago

All sites? No.

IAM? Def. But how critical is IAM, anyway?

grogenaut4• 2 months ago

Oh no won't someone please think of the prop wagerers.

BugsJustFindMe• 2 months ago

[flagged]

aussieguy1234• 2 months ago

Once known for having super reliable services, I've heard this company is scrambling to re hire some of the engineers they overconfidently "replaced" with AI.

When customers pay for cloud services, they expect them to be maintained by competent engineers.

edit: Not sure why the downvotes. If you fire the engineers that have been keeping your systems running reliably for years, what do you expect to happen?

wmf• 2 months ago

It's a cooling equipment failure. Equipment is going to fail.

corvad• 2 months ago

It's always East 1... Jokes aside I don't understand how often east-1 is taken down compared to other regions. Like it should be pretty similar to other regions architecture wise.

tom1337• 2 months ago

Isn't east one the "core" datacenter and also the oldest? I'd imagine it has more load than the other regions and also has more tech debt and architectural / engineering debt because they had less experience when they built it. Also iirc some services rely on east-1 as a single point of failure for configuration (like IAM or some S3 stuff?)

doitLP• 2 months ago

Yes it tends to have the most things running in it, including backbone and internal services that only exist in that region.

__turbobrew__2• 2 months ago

What I have seen at other companies is that the older datacenters have suboptimal designs which are impossible to fix after the fact.

JimDabell• 2 months ago

Amusingly:

AWS in 2025: The Stuff You Think You Know That’s Now Wrong
us-east-1 is no longer a merrily burning dumpster fire of sadness and regret.

— https://www.lastweekinaws.com/blog/aws-in-2025-the-stuff-you...

Otherwise a good article!

tardedmeme5• 2 months ago

Otherwise a good article!

Who is Gell-Mann and why is he so forgetful?

bandrami• 2 months ago

It's the oldest regional system and has some structural importance (e.g. the internal CA resides there I think)

yomismoaqui• 2 months ago

How many nines of are we at this year?

toast0• 2 months ago

Eight eights!

fastest9632• 2 months ago

Coinbase claimed multiple AZs were down but the AWS statement was that only a single AZ was affected. Does anyone have more details?

b40d-48b2-979e2• 2 months ago

Never trust a crypto company to be honest.

merek2• 2 months ago

I can't find an official source, but I suspect the blast radius isn't limited to the AZ.

I have systems running in us-east-1, and over the course of the incident, I noticed unexplainable intermittent connectivity issues that I've never seen before, even outside of az4.

adamg203• 2 months ago

spent the evening looking at SLI graphs waiting for the region to blow up but it never did. only a few envs across many had some degraded EBS vols in the single AZ. it was absolutely a single az (use-az4).

bombcar2• 2 months ago

East-1 going down always takes some things from other AZs, because there's always something dependent on East-1.

fastest9632• 2 months ago

Coinbase confirmed on X that the exchange only ran in one AZ for latency reasons: https://x.com/i/status/2052855725857329254

jeffbee2• 2 months ago

I don't see anything on downdetector suggesting this was particularly disruptive.

sitzkrieg2• 2 months ago

using aws since s3 came out and i’ve yet to see any major company do multi az failover in any capacity whatsoever. default region ftw

jedberg2• 2 months ago

We were doing multi-AZ and multi-region failover at Netflix all the way back in 2011:

https://netflixtechblog.com/the-netflix-simian-army-16e57fba...

sitzkrieg2• 2 months ago

fair point. credit where it is due not a user but my understanding is netflix never went down w us-east-1 :-)

matt3210• 2 months ago

Right, cooling.

whatever1• 2 months ago

2/last 365 days down. My Ubuntu nas is 0/last 365days down.

Come and give me your cash if you want resilience.

justincormack• 2 months ago

But you couldnt apply security updates because Ubuntu was doen

tornikeo2• 2 months ago

I wonder if hetzner had better uptime in EU than AWS this year.

altern8• 2 months ago

Why no love for OVH?

I find Hetzner's UI to be super-confusing, making it hard to manage things.

mimischi• 2 months ago

At the rate that people claim AWS us-east to go down, folks will argue that OVH has a tendency to go up in flames!

teitoklien• 2 months ago

ovh rocks, they are also far more customer support friendly than hetzner. Half the time hetzner feels like they are doing you a favor by letting you rent servers from them.

Ovh is way simpler, and openstack integration from them works good enough for most of my needs.

Kinda insane how atrocious docs are tho. No .md markdown format to let agents read stuff yet -_-

tornikeo2• 2 months ago

Who said anything about ui? I just grab my project write key and Codex handles it all, no UI from idea to production at all.

TiredOfLife• 2 months ago

OVH datacenters occasionally burn down.

rswail• 2 months ago

So in the comments here we have the usual about us-east-1, it's centralized, it's a SPOF for AWS, they should fix it, don't put your stuff there, etc.

This was one data centre in one zone of a multi-zone region.

Yes IAM/R53 and others are centralized there, yes, reworking those service to be decentralized and cross-region would be a Good Thing. But us-east-1 is already multi-zone (6 with a seventh marked as "coming in 2026") with multi DC within zones. From memory, when a global service like IAM is out, it's more likely to be bugs in the implementation or dependency than a "if this was cross-region it wouldn't have died" issue.

But this wasn't an outage of any AWS global service this time. The only one that seemed to have more impact was/is MSK. Which is likely to be more of an issue with Kafka than anything AWS related.

grendelt• 2 months ago

There sure are a lot of eggs in that East basket.

dnnddidiej2• 2 months ago

I remember someone said friends dont let friends use USE1 last time and I thought that as the slack message saying USE1 and all the stuff we deploy there has gone to shit.

jasonlotito• 2 months ago

In this thread: People confusing AZs, Regions, and why people would want to use single AZs.

1vuio0pswjnm7• 2 months ago

Actual CNBC title: AWS data center outage hits trading on FanDuel, Coinbase - recovery to take hours

ptdorf2• 2 months ago

Totally unrelated:

Amazon board: institutional knowledge is the real bottleneck, guys! Let's replace these entitled seniors and staff with juniors armed with kiro. Same difference, right?

AWS North Virginia data center outage – resolved

Related Stories