1. Home
  2. Outages
  3. Elite: Dangerous
  4. 30 Oct 2026

OutageFriday 30 October 2026Ended 31 Oct, 00:54

Elite: Dangerous outage on 30 October 2026

Problem reports about Elite: Dangerous rose to outage level at 22:30 Central European time on Friday 30 October 2026 and stayed there for 2 h 24 min.

They peaked at 160 reports in 15 minutes at 23:08, at a time of day when there are usually almost none, and 437 reports came in while the outage lasted.

Reports reached outage level in 4 countries, the US, the UK, Germany, France.

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

Is Elite: Dangerous down right now? 5 outages of Elite: Dangerous

Started
22:30
Fri 30 Oct, Central European time
At outage level
2 h 24 min
Ended 00:54 on 31 Oct
Busiest 15 minutes
160
reports, at 23:08
Reports during the outage
437
Counted in 15-minute windows
Timeline

Reports from Fri 16:30 to Sat 07:00

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 Elite: Dangerous rose to outage level at 22:30 Central European time on Friday 30 October 2026 and stayed there for 2 h 24 min. They peaked at 160 reports in 15 minutes at 23:08, at a time of day when there are usually almost none, and 437 reports came in while the outage lasted. Reports reached outage level in 4 countries, the US, the UK, Germany, France. 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 30 October, 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 USOutage438
The UKOutage236
GermanyOutage125
FranceOutage58
CanadaNormal49
AustraliaNormal30
PolandNormal27
The NetherlandsNormal26
ItalyNormal16
Same time

Other services with an outage at the same time

Their reports also reached outage level while Elite: Dangerous'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

Elite: Dangerous: live status and other outages

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

Earlier: 28 Oct 2026 Later: 1 Nov 2026 October 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.

Elite: Dangerous outage on 30 October 2026: problem reports over time

<iframe src="https://isitdownrightnow.app/embed/elite-dangerous/2026-10-30/" title="Elite: Dangerous outage on 30 October 2026" width="100%" height="230" style="border:0;max-width:560px" loading="lazy"></iframe> <p><a href="https://isitdownrightnow.app/services/elite-dangerous/outages/2026-10-30/">Elite: Dangerous outage on 30 October 2026</a> from IsItDownRightNow.app</p>Frame: the chart and numbers, as a small card
<a href="https://isitdownrightnow.app/services/elite-dangerous/outages/2026-10-30/"><img src="https://isitdownrightnow.app/share/elite-dangerous/2026-10-30.png" alt="Elite: Dangerous outage on 30 October 2026: problem reports over time" width="600" height="315" loading="lazy"></a>Image: the same card as a picture
[![Elite: Dangerous outage on 30 October 2026](https://isitdownrightnow.app/share/elite-dangerous/2026-10-30.png)](https://isitdownrightnow.app/services/elite-dangerous/outages/2026-10-30/)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.