Disruption at 02:30 UTC — 104 reports over 2h 12m. Most common: 'Not working' (17%); most reports from the United States.
No problems reported at Sprint right now
Problem reports for Sprint 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–
Sprint not working for you?
no problem reports in the last 24 h
outage map · last 24 h
live pulse
- report🇺🇸Not working - Costa Mesa67d
- report🇺🇸Problem report - Atlanta101d
- reportProblem report173d
- reportProblem report229d
- reportProblem report252d
- reportProblem report253d
Sprint outage record
all services by year →No incidents in the past 12 months (last major on record: 2018-11-01).
Since 2016, down.now has recorded 29 outage days on Sprint, 3 of them major; the largest was Nov 1, 2018 with 1,816 reports, mostly from the United States.
2021
biggest outages of 2021 →
1 recorded outage day — 243 reports on Nov 30, mostly from the United States.
Disruption at 18:50 UTC — 243 reports over 5h 38m. Most common: 'Not working' (2%); most reports from the United States.
2019
biggest outages of 2019 →
6 recorded outage days — the worst on Jan 22, 479 reports, mostly from Texas, United States.
Disruption at 17:25 UTC — 63 reports over 1h 23m. Most common: 'Not working' (6%); most reports from the United States.
Disruption at 18:38 UTC — 193 reports over 3h 8m. Most common: 'Not working' (7%); most reports from the United States.
Outage at 00:29 UTC — 184 reports over 1h 34m. Most common: 'Not working' (2%); most reports from the United States.
Outage at 22:04 UTC — 216 reports over 1h 30m. Most common: 'Not working' (7%); most reports from the United States.
Disruption at 11:33 UTC — 50 reports over 1h 16m. Most common: 'Not working' (27%); most reports from the United States.
Outage at 23:37 UTC — 479 reports over 3h 25m. Most common: 'Not working' (29%); most reports from Texas, United States.
2018
biggest outages of 2018 →
9 recorded outage days, 2 major — the worst on Nov 1, 1816 reports, mostly from the United States.
Outage at 23:04 UTC — 105 reports over 59m. Most common: 'Not working' (14%); most reports from Texas, United States.
Major outage — problem reports peaked at 10/min around 00:35 UTC; 1,816 reports over 5h 13m. Most reports from the United States.
- reports
- 1,816
- duration
- 5h 13m
- top problem
- Not working 3%
story · 3 beats
- 20:41 Problem reports started climbing at 20:41 UTC.
- 00:35 Peak at 00:35 UTC: 10/min.
- 01:54 Problem reports faded around 01:54 UTC.
reports · 2018-11-01 · no recorded series
incident timeline
- 20:41Problem reports started climbing.
- 00:35Peak: 10/min.
- 01:54Problem reports faded.
outage map
Disruption at 20:56 UTC — 122 reports over 2h 6m. Most common: 'Not working' (5%); most reports from the United States.
Major outage — problem reports peaked at 5/min around 22:30 UTC; 766 reports over 7h 4m. Most reports from New Jersey, United States.
- reports
- 766
- duration
- 7h 4m
- top problem
- Not working 38%
story · 3 beats
- 20:34 Problem reports started climbing at 20:34 UTC.
- 22:30 Peak at 22:30 UTC: 5/min.
- 03:38 Problem reports faded around 03:38 UTC.
Disruption at 16:12 UTC — 94 reports over 2h 22m. Most common: 'Not working' (27%); most reports from the United States.
Outage at 04:41 UTC — 197 reports over 1h 51m. Most common: 'Not working' (20%); most reports from the United States.
Disruption at 16:44 UTC — 46 reports over 43m. Most common: 'Not working' (13%); most reports from the United States.
Disruption at 04:22 UTC — 11 reports over 1m. Most reports from the United States.
Disruption at 05:40 UTC — 75 reports over 1h 5m. Most reports from Texas, United States.
2017
biggest outages of 2017 →
10 recorded outage days, 1 major — the worst on Oct 17, 760 reports, mostly from the United States.
Outage at 23:00 UTC — 15 reports over 1m. Most reports from the United States.
Major outage — problem reports peaked at 14/min around 10:30 UTC; 760 reports over 1h 56m. Most reports from the United States.
- reports
- 760
- duration
- 1h 56m
story · 3 beats
- 09:08 Problem reports started climbing at 09:08 UTC.
- 10:30 Peak at 10:30 UTC: 14/min.
- 11:04 Problem reports faded around 11:04 UTC.
Disruption at 17:00 UTC — 10 reports over 5m. Most reports from the United States.
Outage at 21:19 UTC — 304 reports over 2h 40m. Most reports from the United States.
Outage at 17:37 UTC — 73 reports over 38m. Most reports from the United States.
Outage at 12:20 UTC — 428 reports over 3h 49m. Most reports from Pennsylvania, United States.
Disruption at 03:00 UTC — 10 reports over 0m. Most reports from the United States.
Outage at 17:01 UTC — 163 reports over 1h 16m. Most reports from the United States.
Outage at 20:25 UTC — 96 reports over 1h 1m. Most reports from Illinois, United States.
Disruption at 02:11 UTC — 233 reports over 3h 59m. Most reports from the United States.
2016
biggest outages of 2016 →
2 recorded outage days — the worst on Dec 14, 728 reports, mostly from Nebraska, United States.
Outage at 14:44 UTC — 728 reports over 10h 19m. Most reports from Nebraska, United States.
Outage at 13:04 UTC — 329 reports over 3h 25m. Most reports from the United States.
Sprint comments
anonymous · no accountcommon questions
Is Sprint down right now?
Problem reports for Sprint are at their usual level right now.
Is Sprint down for everyone or just me?
Right now down.now isn't seeing a broad Sprint 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 Sprint last go down?
There are no recorded Sprint outages on down.now yet. Every incident we detect is kept permanently on this page.
How can I report a problem with Sprint?
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 Sprint is down?
Down.Now watches two crowd signals for Sprint — 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 Sprint's servers directly.