Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    1. Home
    2. Mobile Games
    3. Fortnite
    4. Incident
    Fortnite logo

    Fortnite - Service Disruption

    Resolved
    Critical Outage
    Lasted 10h 15m
    StartedSeptember 4, 202611:55 PM
    ResolvedSeptember 5, 202610:10 AM

    Social signals and community reports

    • FyreZoruaI can name 1000 big reasons why the game's down4 days ago
    • Sydny Wernerthis โ˜๐Ÿผโ˜๐Ÿผโ˜๐Ÿผ4 days ago

    Incident Details

    Widespread service disruption detected. 73 reports received from 2 countries.

    Incident Timeline

    Status changes during this incident

    1. Incident detected

      Sep 4, 2026, 11:55 PM UTC

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

      73 reports ยท 2 affected countries

    2. Recovery being verified

      Sep 5, 2026, 12:07 AM UTC

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

    3. Recovery interrupted

      Sep 5, 2026, 12:34 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    4. Recovery being verified

      Sep 5, 2026, 12:45 AM UTC

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

    5. Recovery interrupted

      Sep 5, 2026, 1:03 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    6. Recovery being verified

      Sep 5, 2026, 1:16 AM UTC

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

    7. Recovery interrupted

      Sep 5, 2026, 1:20 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    8. Recovery being verified

      Sep 5, 2026, 1:25 AM UTC

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

    9. Recovery interrupted

      Sep 5, 2026, 1:36 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    10. Recovery being verified

      Sep 5, 2026, 2:00 AM UTC

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

    11. Recovery interrupted

      Sep 5, 2026, 2:24 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    12. Recovery being verified

      Sep 5, 2026, 2:37 AM UTC

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

    13. Recovery interrupted

      Sep 5, 2026, 2:53 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    14. Recovery being verified

      Sep 5, 2026, 3:15 AM UTC

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

    15. Recovery interrupted

      Sep 5, 2026, 3:28 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    16. Recovery being verified

      Sep 5, 2026, 3:35 AM UTC

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

    17. Recovery interrupted

      Sep 5, 2026, 3:55 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    18. Recovery being verified

      Sep 5, 2026, 4:15 AM UTC

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

    19. Recovery interrupted

      Sep 5, 2026, 4:38 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    20. Recovery being verified

      Sep 5, 2026, 5:00 AM UTC

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

    21. Recovery interrupted

      Sep 5, 2026, 5:03 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    22. Recovery being verified

      Sep 5, 2026, 5:24 AM UTC

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

    23. Recovery interrupted

      Sep 5, 2026, 5:44 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    24. Recovery being verified

      Sep 5, 2026, 6:08 AM UTC

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

    25. Recovery interrupted

      Sep 5, 2026, 6:25 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    26. Recovery being verified

      Sep 5, 2026, 6:45 AM UTC

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

    27. Recovery confirmed

      Sep 5, 2026, 7:20 AM UTC

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

    28. Incident reopened

      Sep 5, 2026, 7:59 AM UTC

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

      47 reports ยท 2 affected countries

    29. Recovery being verified

      Sep 5, 2026, 8:15 AM UTC

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

    30. Recovery interrupted

      Sep 5, 2026, 8:16 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    31. Recovery being verified

      Sep 5, 2026, 8:45 AM UTC

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

    32. Recovery interrupted

      Sep 5, 2026, 8:57 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    33. Recovery being verified

      Sep 5, 2026, 9:35 AM UTC

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

    34. Recovery confirmed

      Sep 5, 2026, 10:10 AM UTC

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

    Impact Summary

    Reports
    73
    Countries
    2
    Top Issues
    Issue DistributionLag / High Ping: 18 reports (85.7%)Completely Down: 3 reports (14.3%)
    Lag / High Ping
    18(86%)
    Completely Down
    3(14%)

    Quick Links

    View Current Status