Outage at 22:10 UTC — 315 reports over 3h 27m. Most common: 'Servers / connection' (68%); reports from the United States, Canada, the United Kingdom and 25 more countries.
No problems reported at Dragon Ball FighterZ right now
Problem reports for Dragon Ball FighterZ are at their usual level right now.
Reports · 24 h
0
Last report
> 1 h ago
Rate now
0 / 5 min
Last incident
none on record
reports · 24 h · /15 min
1h–15m–5m–
Dragon Ball FighterZ not working for you?
no problem reports in the last 24 h
outage map · last 24 h
live pulse
- report🇨🇲Can't log in21d
- report🇯🇴Problem report - Amman87d
- report🇬🇧Problem report - Trowbridge110d
- report🇺🇸Problem report - Philadelphia163d
- report🇺🇸Problem report - Norfolk165d
- report🇺🇸Problem report - The Bronx165d
Dragon Ball FighterZ outage record
all services by year →No incidents in the past 12 months.
Since 2018, down.now has recorded 63 outage days on Dragon Ball FighterZ; the largest was Feb 1, 2018 with 420 reports, mostly from the United States.
2020
biggest outages of 2020 →
6 recorded outage days — the worst on Apr 4, 303 reports, across 30 countries.
Disruption at 19:14 UTC — 61 reports over 34m. Most common: 'Servers / connection' (74%); reports from the United States, Spain, Mexico and 17 more countries.
Disruption at 06:28 UTC — 12 reports over 5m. Most common: 'Servers / connection' (50%); most reports from the United States.
Outage at 19:06 UTC — 303 reports over 2h 3m. Most common: 'Servers / connection' (77%); reports from the United States, the United Kingdom, France and 27 more countries.
Disruption at 01:01 UTC — 82 reports over 1h 13m. Most common: 'Servers / connection' (82%); most reports from the United States.
Disruption at 03:01 UTC — 25 reports over 8m. Most common: 'Servers / connection' (96%); reports from the United States, Australia, Mexico and 4 more countries.
Disruption at 01:01 UTC — 135 reports over 2h 2m. Most common: 'Servers / connection' (94%); most reports from the United States.
2019
biggest outages of 2019 →
11 recorded outage days — the worst on Jul 17, 169 reports, across 30 countries.
Disruption at 19:12 UTC — 169 reports over 2h 1m. Most common: 'Servers / connection' (81%); reports from the United States, France, the United Kingdom and 27 more countries.
Disruption at 01:01 UTC — 47 reports over 1h 12m. Most common: 'Servers / connection' (94%); most reports from the United States.
Disruption at 01:01 UTC — 45 reports over 53m. Most common: 'Servers / connection' (96%); reports from the United States, Canada, the United Kingdom and 7 more countries.
Outage at 22:53 UTC — 50 reports over 18m. Most common: 'Servers / connection' (86%); reports from the United States, Germany, the United Kingdom and 11 more countries.
Disruption at 01:01 UTC — 74 reports over 57m. Most common: 'Servers / connection' (95%); most reports from the United States.
Outage at 01:17 UTC — 139 reports over 48m. Most common: 'Servers / connection' (65%); most reports from the United States.
Disruption at 00:57 UTC — 35 reports over 39m. Most common: 'Servers / connection' (94%); reports from the United States, Argentina, Canada and 4 more countries.
Disruption at 01:01 UTC — 55 reports over 1h 10m. Most common: 'Servers / connection' (98%); most reports from the United States.
Disruption at 01:03 UTC — 20 reports over 16m. Most common: 'Servers / connection' (100%); most reports from the United States.
Disruption at 01:01 UTC — 46 reports over 58m. Most common: 'Servers / connection' (96%); reports from the United States, Canada, Germany and 8 more countries.
2018
biggest outages of 2018 →
45 recorded outage days — the worst on Feb 1, 420 reports, mostly from the United States.
Outage at 14:58 UTC — 254 reports over 4h 52m. Most common: 'Servers / connection' (77%); reports from the United States, the United Kingdom, Germany and 24 more countries.
Outage at 01:01 UTC — 135 reports over 2h 14m. Most common: 'Servers / connection' (94%); most reports from the United States.
Outage at 01:01 UTC — 86 reports over 56m. Most common: 'Servers / connection' (89%); most reports from the United States.
Outage at 01:01 UTC — 109 reports over 1h 9m. Most common: 'Servers / connection' (94%); most reports from the United States.
Outage at 00:53 UTC — 96 reports over 1h 9m. Most common: 'Servers / connection' (90%); most reports from the United States.
Outage at 00:54 UTC — 95 reports over 1h 7m. Most common: 'Servers / connection' (84%); most reports from the United States.
Outage at 01:02 UTC — 103 reports over 1h 4m. Most common: 'Servers / connection' (63%); most reports from the United States.
Outage at 00:57 UTC — 244 reports over 1h 40m. Most reports from the United States.
Outage at 00:32 UTC — 420 reports over 2h 34m. Most reports from the United States.
Outage, starting at 16:56 UTC — 120 reports over 1h 34m. Reports from the United States, Germany, the United Kingdom and 10 more countries.
Dragon Ball FighterZ comments
anonymous · no accountcommon questions
Is Dragon Ball FighterZ down right now?
Problem reports for Dragon Ball FighterZ are at their usual level right now.
Is Dragon Ball FighterZ down for everyone or just me?
Right now down.now isn't seeing a broad Dragon Ball FighterZ outage, so the problem is most likely local to you — your connection, your device, or the app itself. Try the app on mobile data instead of Wi-Fi, then restart the router. If reports start arriving from other people, this page flips to an outage within minutes.
When did Dragon Ball FighterZ last go down?
There are no recorded Dragon Ball FighterZ outages on down.now yet. Every incident we detect is kept permanently on this page.
How can I report a problem with Dragon Ball FighterZ?
Use the report panel on this page and pick what's not working — it takes one tap and no account. Reports are anonymous, and they feed the live signal on this page immediately.
How does down.now know if Dragon Ball FighterZ is down?
Down.Now watches two crowd signals for Dragon Ball FighterZ — anonymous reports submitted here, and public social-media posts about it — and compares the live volume against what's normal for that hour of the day. A sustained spike above that baseline opens an incident, which is usually visible before an official confirmation. We measure what users report, not Dragon Ball FighterZ's servers directly.