Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

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

    Spectrum - Service Disruption

    Resolved
    Critical Outage
    Lasted 1d 1h
    StartedSeptember 5, 20261:26 PM
    ResolvedSeptember 6, 20262:50 PM

    Uptimus incident intelligence

    Spectrum Service Disruption Reports

    As of September 5, 2026, there is an elevated volume of user-submitted reports regarding Spectrum internet and TV services, with 141 reports indicating issues ranging from complete service loss to slow performance. Charter Communications has not issued an official confirmation of a widespread network outage.

    Observed user impact

    Community reports suggest users may be experiencing complete service outages or slow performance, though it is unclear if these are centralized or localized incidents.

    Likely cause

    No reliable public cause has been confirmed yet.

    Based on community signalsConfidence 60%

    Public sources

    • statusgator.com
    • outage.report
    • designtaxi.com
    • spectrum.net
    • spectrum.net
    • spectrum.net

    Social signals and community reports

    • [email protected]Martin mi 49070. Of the last 17 hrs Internet has only been online for less than 45 minutes.2 days ago
    • King Astral3 days!? COULD TAKE 3 DAYS TO FIX IT SPECTRUM!? WHY!? WHY BRO...?2 days ago
    • JacobBeen down no internet since 12:30 Mentor ohio2 days ago
    • Cday6104Any word2 days ago
    • Cday6104Down in Fredericktown2 days ago
    • King AstralStill down in China Grove NC. Seriously Spectrum? -_-2 days ago
    • [email protected]Is down more than connected for the last month. Unfortunately this is becoming a very noticeable pattern with spectrum.2 days ago
    • Rocky MontalvoDon’t worry guys services will be back up at 2 in the morning. THROW SPECTRUM ROUTER AND MODEM AWAY FOR BEST SERVICE !2 days ago
    • Arthur ArenaSpectrum in Saugerties ny sucks. I wish I had verizon fios back.3 days ago

    Incident Details

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

    Incident Timeline

    Status changes during this incident

    1. Incident detected

      Sep 5, 2026, 1:26 PM UTC

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

      78 reports · 1 affected countries

    2. Recovery being verified

      Sep 5, 2026, 1:40 PM UTC

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

    3. Recovery interrupted

      Sep 5, 2026, 2:04 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    4. Recovery being verified

      Sep 5, 2026, 2:20 PM UTC

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

    5. Recovery interrupted

      Sep 5, 2026, 2:44 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    6. Recovery being verified

      Sep 5, 2026, 3:00 PM UTC

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

    7. Recovery interrupted

      Sep 5, 2026, 3:21 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    8. Recovery being verified

      Sep 5, 2026, 3:35 PM UTC

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

    9. Recovery confirmed

      Sep 5, 2026, 4:10 PM UTC

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

    10. Incident reopened

      Sep 5, 2026, 4:35 PM UTC

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

      55 reports · 1 affected countries

    11. Recovery being verified

      Sep 5, 2026, 4:50 PM UTC

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

    12. Recovery interrupted

      Sep 5, 2026, 5:13 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    13. Recovery being verified

      Sep 5, 2026, 5:30 PM UTC

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

    14. Recovery interrupted

      Sep 5, 2026, 5:52 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    15. Recovery being verified

      Sep 5, 2026, 6:10 PM UTC

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

    16. Recovery interrupted

      Sep 5, 2026, 6:32 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    17. Recovery being verified

      Sep 5, 2026, 6:45 PM UTC

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

    18. Recovery confirmed

      Sep 5, 2026, 7:20 PM UTC

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

    19. Incident reopened

      Sep 5, 2026, 7:53 PM UTC

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

      50 reports · 1 affected countries

    20. Recovery being verified

      Sep 5, 2026, 8:10 PM UTC

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

    21. Recovery confirmed

      Sep 5, 2026, 8:45 PM UTC

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

    22. Incident reopened

      Sep 5, 2026, 9:04 PM UTC

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

      25 reports · 1 affected countries

    23. Recovery being verified

      Sep 5, 2026, 9:30 PM UTC

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

    24. Recovery interrupted

      Sep 5, 2026, 9:58 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    25. Recovery being verified

      Sep 5, 2026, 10:10 PM UTC

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

    26. Recovery interrupted

      Sep 5, 2026, 10:26 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    27. Recovery being verified

      Sep 5, 2026, 10:40 PM UTC

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

    28. Recovery interrupted

      Sep 5, 2026, 11:03 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    29. Recovery being verified

      Sep 5, 2026, 11:20 PM UTC

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

    30. Recovery interrupted

      Sep 5, 2026, 11:42 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    31. Recovery being verified

      Sep 6, 2026, 12:00 AM UTC

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

    32. Recovery interrupted

      Sep 6, 2026, 12:21 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    33. Recovery being verified

      Sep 6, 2026, 12:35 AM UTC

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

    34. Recovery interrupted

      Sep 6, 2026, 12:59 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    35. Recovery being verified

      Sep 6, 2026, 1:15 AM UTC

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

    36. Recovery interrupted

      Sep 6, 2026, 1:37 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    37. Recovery being verified

      Sep 6, 2026, 1:55 AM UTC

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

    38. Recovery confirmed

      Sep 6, 2026, 2:30 AM UTC

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

    39. Incident reopened

      Sep 6, 2026, 2:58 AM UTC

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

      83 reports · 1 affected countries

    40. Recovery being verified

      Sep 6, 2026, 3:15 AM UTC

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

    41. Recovery interrupted

      Sep 6, 2026, 3:37 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    42. Recovery being verified

      Sep 6, 2026, 3:55 AM UTC

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

    43. Recovery interrupted

      Sep 6, 2026, 4:16 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    44. Recovery being verified

      Sep 6, 2026, 4:35 AM UTC

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

    45. Recovery interrupted

      Sep 6, 2026, 4:56 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    46. Recovery being verified

      Sep 6, 2026, 5:10 AM UTC

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

    47. Recovery interrupted

      Sep 6, 2026, 5:34 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    48. Recovery being verified

      Sep 6, 2026, 5:50 AM UTC

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

    49. Recovery interrupted

      Sep 6, 2026, 6:13 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    50. Recovery being verified

      Sep 6, 2026, 6:40 AM UTC

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

    51. Recovery confirmed

      Sep 6, 2026, 7:15 AM UTC

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

    52. Incident reopened

      Sep 6, 2026, 7:47 AM UTC

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

      74 reports · 1 affected countries

    53. Recovery being verified

      Sep 6, 2026, 8:05 AM UTC

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

    54. Recovery interrupted

      Sep 6, 2026, 8:27 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    55. Recovery being verified

      Sep 6, 2026, 8:45 AM UTC

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

    56. Recovery confirmed

      Sep 6, 2026, 9:20 AM UTC

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

    57. Incident reopened

      Sep 6, 2026, 10:11 AM UTC

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

      31 reports · 1 affected countries

    58. Recovery being verified

      Sep 6, 2026, 10:25 AM UTC

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

    59. Recovery interrupted

      Sep 6, 2026, 10:59 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    60. Recovery being verified

      Sep 6, 2026, 11:15 AM UTC

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

    61. Recovery interrupted

      Sep 6, 2026, 11:47 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    62. Recovery being verified

      Sep 6, 2026, 12:00 PM UTC

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

    63. Recovery interrupted

      Sep 6, 2026, 12:23 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    64. Recovery being verified

      Sep 6, 2026, 12:40 PM UTC

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

    65. Recovery interrupted

      Sep 6, 2026, 12:55 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    66. Recovery being verified

      Sep 6, 2026, 1:10 PM UTC

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

    67. Recovery interrupted

      Sep 6, 2026, 1:34 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    68. Recovery being verified

      Sep 6, 2026, 1:50 PM UTC

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

    69. Recovery interrupted

      Sep 6, 2026, 2:00 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    70. Recovery being verified

      Sep 6, 2026, 2:15 PM UTC

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

    71. Recovery confirmed

      Sep 6, 2026, 2:50 PM UTC

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

    Impact Summary

    Reports
    78
    Countries
    1
    Top Issues
    Issue DistributionCompletely Down: 34 reports (70.8%)Slow Performance: 14 reports (29.2%)
    Completely Down
    34(71%)
    Slow Performance
    14(29%)

    Quick Links

    View Current Status