Monitoring
Status Pages
Pricing
The Battle Royale game Fortnite has become a sensation amongst online gamers in no time at all. To explain it in simple terms, 100 players are simultaneously dropped into a battleground measuring several (in-game) square kilometers, and must proceed alone or as part of a team towards a random central point on the map whilst avoiding or confronting the other players. The last man or team standing takes the top spot and wins the game. It all adds up to an intense and at times hilarious experience that can last around 1-20 minutes.
The growth in popularity of the game has been epic from a 60,000 players on launch last July to 3,200,000 players in under nine months, and suddenly keeping the game up-and-running was going to require some pretty serious infrastructure.
From day one Epic, the publisher behind Fortnite, has like so many other large businesses such as Airbnb, Unilver, and Netflix relied on Amazon Web Services (AWS) to keep it online.
AWS gives Epic the ability to cope when player numbers spike; the difference in infrastructure workload might be up to ten times difference between the peaks and troughs.
Epic also takes advantage of AWS’s “availability zones”. These 55 zones are designed to ensure web services don’t lag in any one zone. Where one zone fails another simply takes up the baton. Fortnite currently runs across 24 of these zones.
This isn’t to say that AWS and the use of availability zones are infallible. In February of this year Fortnite experienced multiple outages which even AWS’s availability zoning couldn’t prevent.
It’s also worth remembering that whilst many companies such as Epic rely on AWS for its reliability and stability it’s worth remembering that Amazon itself can still have problems.
Just last month on Amazon’s Prime Day the rush for bargains not only brought Amazon down but impacted AWS. Whilst the AWS service itself continued to operate normally, AWS customers were unable to login to their accounts.
More serious however was the four hour outage in AWS’ US-East-1 region in February this year which saw over half of the top 100 internet retailers impacted. Many websites saw the performance of their sites impacted severely (Disney’s store took over 1000% longer to load than normal), many other sites went down completely; the same availability zone having similar issues again in May.
All of this highlights that even if you’re using cloud service providers such as AWS or Google Cloud that monitoring your website is as important as ever.
Share this
4 min read On 13th August 2026, a storm knocked out cooling at RadiusDC’s Phoenix data centre, which hosted essential Namecheap operations. To protect hardware from thermal damage, Namecheap took services offline while temporary chillers were brought in. The incident and recovery ran for roughly 30 hours, with Namecheap’s own site unreachable for about 11 hours 42 minutes
3 min read On Wednesday 19 August, Monzo had an outage. DownDetector logged more than 3,000 reports by midday. Monzo’s own statement was direct about what it did next: it activated Monzo Stand-in, its fully independent backup bank, while it investigated an issue affecting customers. By the end of the day, Monzo said the issue was resolved and
3 min read GitHub’s incident on 17 August 2026 ran from 13:28 to 21:15 UTC, seven hours and forty-seven minutes. At peak, web and API traffic saw error rates of around 20%, while archive and raw-content downloads reached roughly 50%. SAML and OIDC authentication, SCIM and Team Sync were affected alongside Git operations, Actions, Pages, Issues, Pull Requests
3 min read Adding a new website, launching a customer portal, or handing a service to a new team should be straightforward. Setting up monitoring is part of that job, but it is easy for a manual step to be missed when information is spread across several systems. StatusCake now integrates with viaSocket, giving teams a way to connect
7 min read A website may be standing and still be in trouble. It may answer a request, return a cheerful 200 OK, and yet load slowly enough that visitors begin to lose patience. Its certificate may be nearing expiry. Its domain records may have changed. A server may be filling its disk in the background, patient and
6 min read StatusCake tells you that something might be broken. Hermes can check whether it really looks broken, decide who should hear about it, send the email, and keep the record for tomorrow morning’s summary.
Find out everything you need to know in our new uptime monitoring whitepaper 2021
