Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    1. Home
    2. Websites
    3. Spectrum
    4. Incident
    Spectrum logo

    Spectrum - Service Disruption

    Resolved
    Major Outage
    Lasted 22h 31m
    StartedAugust 31, 20265:48 PM
    ResolvedSeptember 1, 20264:20 PM

    Social signals and community reports

    • Paula Sarkar1453 16th street oceano 93445 calif- spectrum wifi down7 days ago
    • Laura Ivanovich-BakerWhen s company does not correctly wire their own business equipment and wiring, we get the mess. TRANSMISSIONS AND ROUTING TABLES IN YOUR LOCAL AREA! Get an App Firewall that runs tracer routes!7 days ago
    • MysterriSpectrum Been down in 33881 for about 7 hours now7 days ago
    • SnowSpectrum internet down in White Settlement, TX. It's been spotty all day and finally went down and never came back up.7 days ago
    • ChrisSpectrum internet is down again in Commerce, Tx it's been acting up all day, and my fiance needs the internet for her emergency alert button.7 days ago
    • BKInternet down again in Wahiawa. I like get free service for the month since multiple times been out. No internet no TV 🤬7 days ago
    • Lisa Marie ParkerSame in Florence County SC, been down since 9am and still down at this time, almost 3:30pm. Spectrum said it should be back up by 4:30, but who even knows at this point.7 days ago
    • Lisa Marie ParkerSpectrum Internet has been down since 9am this morning and it’s almost 3:30pm, Florence County, South Carolina.7 days ago
    • Jane Lanikakron ohio Spectrum Internet acting up again7 days ago

    Incident Details

    Widespread service disruption detected. 25 reports received from 1 country.

    Incident Timeline

    Status changes during this incident

    1. Incident detected

      Aug 31, 2026, 5:48 PM UTC

      Incident opened after 25 recent community reports crossed the outage threshold.

      25 reports · 1 affected countries

    2. Recovery being verified

      Aug 31, 2026, 6:00 PM UTC

      Reports returned to normal. Uptimus is verifying stability for 35 minutes before resolving the incident.

    3. Recovery confirmed

      Aug 31, 2026, 6:35 PM UTC

      Service remained healthy for 35 minutes. The incident is resolved.

    4. Incident reopened

      Aug 31, 2026, 7:28 PM UTC

      Reports returned shortly after recovery, so the same incident was reopened.

      50 reports · 1 affected countries

    5. Recovery being verified

      Aug 31, 2026, 7:45 PM UTC

      Reports returned to normal. Uptimus is verifying stability for 35 minutes before resolving the incident.

    6. Recovery interrupted

      Aug 31, 2026, 8:11 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    7. Recovery being verified

      Aug 31, 2026, 8:25 PM UTC

      Reports returned to normal. Uptimus is verifying stability for 35 minutes before resolving the incident.

    8. Recovery interrupted

      Aug 31, 2026, 8:52 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    9. Recovery being verified

      Aug 31, 2026, 9:04 PM UTC

      Reports returned to normal. Uptimus is verifying stability for 35 minutes before resolving the incident.

    10. Recovery interrupted

      Aug 31, 2026, 9:04 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    11. Recovery being verified

      Aug 31, 2026, 9:20 PM UTC

      Reports returned to normal. Uptimus is verifying stability for 35 minutes before resolving the incident.

    12. Recovery interrupted

      Aug 31, 2026, 9:46 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    13. Recovery being verified

      Aug 31, 2026, 10:00 PM UTC

      Reports returned to normal. Uptimus is verifying stability for 35 minutes before resolving the incident.

    14. Recovery interrupted

      Aug 31, 2026, 10:29 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    15. Recovery being verified

      Aug 31, 2026, 10:45 PM UTC

      Reports returned to normal. Uptimus is verifying stability for 35 minutes before resolving the incident.

    16. Recovery interrupted

      Aug 31, 2026, 11:09 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    17. Recovery being verified

      Aug 31, 2026, 11:25 PM UTC

      Reports returned to normal. Uptimus is verifying stability for 35 minutes before resolving the incident.

    18. Recovery confirmed

      Sep 1, 2026, 12:00 AM UTC

      Service remained healthy for 35 minutes. The incident is resolved.

    19. Incident reopened

      Sep 1, 2026, 1:25 AM UTC

      Reports returned shortly after recovery, so the same incident was reopened.

      25 reports · 1 affected countries

    20. Recovery being verified

      Sep 1, 2026, 1:40 AM UTC

      Reports returned to normal. Uptimus is verifying stability for 35 minutes before resolving the incident.

    21. Recovery confirmed

      Sep 1, 2026, 2:15 AM UTC

      Service remained healthy for 35 minutes. The incident is resolved.

    22. Incident reopened

      Sep 1, 2026, 2:27 AM UTC

      Reports returned shortly after recovery, so the same incident was reopened.

      25 reports · 1 affected countries

    23. Recovery being verified

      Sep 1, 2026, 2:40 AM UTC

      Reports returned to normal. Uptimus is verifying stability for 35 minutes before resolving the incident.

    24. Recovery interrupted

      Sep 1, 2026, 3:07 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    25. Recovery being verified

      Sep 1, 2026, 3:20 AM UTC

      Reports returned to normal. Uptimus is verifying stability for 35 minutes before resolving the incident.

    26. Recovery interrupted

      Sep 1, 2026, 3:48 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    27. Recovery being verified

      Sep 1, 2026, 4:00 AM UTC

      Reports returned to normal. Uptimus is verifying stability for 35 minutes before resolving the incident.

    28. Recovery interrupted

      Sep 1, 2026, 4:27 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    29. Recovery being verified

      Sep 1, 2026, 4:40 AM UTC

      Reports returned to normal. Uptimus is verifying stability for 35 minutes before resolving the incident.

    30. Recovery interrupted

      Sep 1, 2026, 5:07 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    31. Recovery being verified

      Sep 1, 2026, 5:20 AM UTC

      Reports returned to normal. Uptimus is verifying stability for 35 minutes before resolving the incident.

    32. Recovery interrupted

      Sep 1, 2026, 5:50 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    33. Recovery being verified

      Sep 1, 2026, 6:00 AM UTC

      Reports returned to normal. Uptimus is verifying stability for 35 minutes before resolving the incident.

    34. Recovery confirmed

      Sep 1, 2026, 6:35 AM UTC

      Service remained healthy for 35 minutes. The incident is resolved.

    35. Incident reopened

      Sep 1, 2026, 9:25 AM UTC

      Reports returned shortly after recovery, so the same incident was reopened.

      16 reports · 1 affected countries

    36. Recovery being verified

      Sep 1, 2026, 9:40 AM UTC

      Reports returned to normal. Uptimus is verifying stability for 35 minutes before resolving the incident.

    37. Recovery confirmed

      Sep 1, 2026, 10:15 AM UTC

      Service remained healthy for 35 minutes. The incident is resolved.

    38. Incident reopened

      Sep 1, 2026, 10:22 AM UTC

      Reports returned shortly after recovery, so the same incident was reopened.

      16 reports · 1 affected countries

    39. Recovery being verified

      Sep 1, 2026, 10:40 AM UTC

      Reports returned to normal. Uptimus is verifying stability for 35 minutes before resolving the incident.

    40. Recovery interrupted

      Sep 1, 2026, 11:06 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    41. Recovery being verified

      Sep 1, 2026, 11:20 AM UTC

      Reports returned to normal. Uptimus is verifying stability for 35 minutes before resolving the incident.

    42. Recovery interrupted

      Sep 1, 2026, 11:48 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    43. Recovery being verified

      Sep 1, 2026, 12:00 PM UTC

      Reports returned to normal. Uptimus is verifying stability for 35 minutes before resolving the incident.

    44. Recovery interrupted

      Sep 1, 2026, 12:14 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    45. Recovery being verified

      Sep 1, 2026, 12:30 PM UTC

      Reports returned to normal. Uptimus is verifying stability for 35 minutes before resolving the incident.

    46. Recovery interrupted

      Sep 1, 2026, 1:00 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    47. Recovery being verified

      Sep 1, 2026, 1:15 PM UTC

      Reports returned to normal. Uptimus is verifying stability for 35 minutes before resolving the incident.

    48. Recovery confirmed

      Sep 1, 2026, 1:50 PM UTC

      Service remained healthy for 35 minutes. The incident is resolved.

    49. Incident reopened

      Sep 1, 2026, 2:49 PM UTC

      Reports returned shortly after recovery, so the same incident was reopened.

      14 reports · 1 affected countries

    50. Recovery being verified

      Sep 1, 2026, 3:05 PM UTC

      Reports returned to normal. Uptimus is verifying stability for 35 minutes before resolving the incident.

    51. Recovery interrupted

      Sep 1, 2026, 3:32 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    52. Recovery being verified

      Sep 1, 2026, 3:45 PM UTC

      Reports returned to normal. Uptimus is verifying stability for 35 minutes before resolving the incident.

    53. Recovery confirmed

      Sep 1, 2026, 4:20 PM UTC

      Service remained healthy for 35 minutes. The incident is resolved.

    Impact Summary

    Reports
    25
    Countries
    1
    Top Issues
    Issue DistributionCompletely Down: 15 reports (68.2%)Slow Performance: 7 reports (31.8%)
    Completely Down
    15(68%)
    Slow Performance
    7(32%)

    Quick Links

    View Current Status