StatusCake

Solar Storms in 2015 Could Leave New York Without Power for Months

website downtime

A study released last week by researchers UK insurance company Lloyd’s of London and the US’s Atmospheric and Environmental Research painted an apocalyptic picture, the kind of thing of only seen in end of the world disaster movies, as it warned that large solar storms, could leave tens of millions of people in North America without electricity for months on end, if not years.

The Lloyd’s report: Solar Storm Risk to the North American Electric Grid investigated how solar storms, which give off huge blasts of plasma which once they enter the earth’s magnetic field can interfere with electrical equipment on the ground or even in the atmosphere such as satellites.

Such massive geomagnetic storms are thankfully relatively rare. Although there have been large solar storms in recent years – a storm in 1989 in Quebec left six million Canadians without power for nine hours – the massive storms that the report warns of are seen once every 150 years.

When was the last storm like this?

The last massive solar storm to hit the earth was back in 1859, and we’re now overdue another. The so called Carrington Event of 1859 is considered by many as one of the most severe storms on record, and which if it hit the US today would impact on some 20-40 million people, with blackouts last anywhere from a few weeks up until a couple of years. The report claims that the economic costs of such a storm could run into $2.6 trillion, with the knock-on effect in terms of the repercussions to the global economy far higher – leading to prolonged periods of recession and potentially civil unrest.

With solar storms recurring in cycles, researchers have predicted that the next massive storm could hit our planet in 2015. And with only a couple of years until such a possible event, governments and those companies who are most likely to be impacted, and looking at ways to manage the risk and reduce disruption should a massive storm strike.

Whilst the doomsday report primarily assesses the risk to electrical and power infrastructure, in a world driven by electronics – all of which could be rendered useless by the storm – the impact could be truly frightening. Global air travel would almost certain be grounded. Not only would the storm interfere with the control systems of the aeroplanes themselves, but the satellites that we all rely on for GPS and communications would almost certainly be knocked out.

Without electricity and communications hospitals would struggle to support patients whose lives depended on electrical equipment. Schools and offices would be unable to open.

Those areas most likely to be hit by such a solar storm include the UK, and within the US New York and Washington DC would almost certainly be affected.

Following that solar storm in 1989 the Canadian government spent £0.77bn on measures to block massive surges in electricity along its power lines – small change compared with the £8.72bn it cost to repair the system that was knocked out in just a couple of minutes. Prevention is clearly far better, and cheaper, than cure.

James Barnes, StatusCake.com

Share this

More from StatusCake

What the Namecheap Outage Revealed About DNS Recovery

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

Monzo’s Stand-In Held Up on Wednesday. Some Customers Still Had a Bad Day.

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

What Broke GitHub on August 17 and How Retries Made the Incident Worse

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

Automate StatusCake Monitoring with viaSocket

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

Website Monitoring Checklist: What to Track Beyond Uptime

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

Want to know how much website downtime costs, and the impact it can have on your business?

Find out everything you need to know in our new uptime monitoring whitepaper 2021

*By providing your email address, you agree to our privacy policy and to receive marketing communications from StatusCake.