1. Home
  2. Outages
  3. Fortnite
  4. 1 Nov 2026

OutageSunday 1 November 2026Ended 22:38

Fortnite outage on 1 November 2026

Problem reports about Fortnite rose to outage level at 05:26 Central European time on Sunday 1 November 2026, in 2 separate spikes over 17 h 12 min (11 h 26 min at outage level in all).

They peaked at 1,670 reports in 15 minutes at 18:56, about 167 times the usual level for that time of day, and 9,040 reports came in while the outage lasted.

Reports reached outage level in 36 countries, the US, the UK, Germany, France and more.

12 other services had an outage spike at the same time.

Is Fortnite down right now? 2 outages of Fortnite

Started
05:26
Sun 1 Nov, Central European time
At outage level
11 h 26 min
Ended 22:38
Busiest 15 minutes
1,670
reports, at 18:56
Reports during the outage
9,040
Peak about 167× the usual level
Timeline

Reports from Sat 23:15 to Mon 04:45

One bar per 15 minutes, Central European time. Red bars are the outage; the dashed line is what a usual day sees at that time.

Problem reports about Fortnite rose to outage level at 05:26 Central European time on Sunday 1 November 2026, in 2 separate spikes over 17 h 12 min (11 h 26 min at outage level in all). They peaked at 1,670 reports in 15 minutes at 18:56, about 167 times the usual level for that time of day, and 9,040 reports came in while the outage lasted. Reports reached outage level in 36 countries, the US, the UK, Germany, France and more. 12 other services had an outage spike at the same time.
Around the world

Where people reported it that day

Each country's reports on 1 November, against the usual level there. Outage means reports stayed at outage level for half an hour or more; above usual, for an hour or more.

CountryThat dayReports
The USOutage10,342
The UKOutage2,688
GermanyOutage1,576
FranceOutage1,344
The NetherlandsOutage1,293
CanadaOutage1,082
JapanOutage1,010
MexicoOutage979
AustraliaOutage969
PolandOutage685
ItalyOutage538
SpainOutage497
Same time

Other services with an outage at the same time

Their reports also reached outage level while Fortnite's did. Many services failing together can point to a shared cause, such as a network or cloud provider, but reports alone cannot show it.

More

Fortnite: live status and other outages

Check whether Fortnite is down right now: the live page shows the last 24 hours and fixes to try. This site keeps a page for each of Fortnite's 2 outages since the archive began.

Later: 3 Nov 2026 November 2026 outage report All recent outages

Embed

Put this outage in an article

Copy a frame with the chart and numbers above, or an image of the same card for places that do not allow frames, such as newsletters. Both link back to this page. More for journalists.

Fortnite outage on 1 November 2026: problem reports over time

<iframe src="https://isitdownrightnow.app/embed/fortnite/2026-11-01/" title="Fortnite outage on 1 November 2026" width="100%" height="230" style="border:0;max-width:560px" loading="lazy"></iframe> <p><a href="https://isitdownrightnow.app/services/fortnite/outages/2026-11-01/">Fortnite outage on 1 November 2026</a> from IsItDownRightNow.app</p>Frame: the chart and numbers, as a small card
<a href="https://isitdownrightnow.app/services/fortnite/outages/2026-11-01/"><img src="https://isitdownrightnow.app/share/fortnite/2026-11-01.png" alt="Fortnite outage on 1 November 2026: problem reports over time" width="600" height="315" loading="lazy"></a>Image: the same card as a picture
[![Fortnite outage on 1 November 2026](https://isitdownrightnow.app/share/fortnite/2026-11-01.png)](https://isitdownrightnow.app/services/fortnite/outages/2026-11-01/)Markdown: the image, for README files and forums

Where these numbers come from

The numbers are problem reports that users sent to a public outage-reporting service, counted in 15-minute windows and kept as this site's live page showed them. A spike counts as an outage when reports are more than twice the usual level and far above the day's average. Reports show that many people had trouble at the same time, not what caused it; the service's own status page is the place for that.