Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

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

    Fortnite - Service Disruption

    Resolved
    Major Outage
    Lasted 12h 33m
    StartedSeptember 5, 20262:13 PM
    ResolvedSeptember 6, 20262:46 AM

    Social signals and community reports

    • Tkfive years later the server are still trash3 days ago
    • boxiershelf1460This guy keeps saying they are the reason whatever is down is down.3 days ago
    • SegaSaturndude what does that even have to do with fortnite's servers being down for unknown reasons smh3 days ago
    • BlackDragonBardBurndCloudFEpic shouldn’t steal… 😈3 days ago
    • SegaSaturnWDYM "YOU HAD TROUBLE TALKING TO THE MATCHMAKER" BRO COME ON MAN WHAT THE HECK🤦3 days ago
    • SegaSaturnand what would these reasons be? (i know this was 18 hours ago but this game is STILL saying its down)3 days ago
    • SegaSaturnepic games fix your game plz I just want to play fortnite bro🙄3 days ago
    • SegaSaturnOh my god bruh why is it telling me that we can't join any matches right now I'm just trying to play fortnite and this is what i get?!3 days ago
    • FyreZoruaARE WE SERIOUS3 days ago
    • ArcanistAttempting to matchmake gives error after ready3 days ago
    • mohm'd eltahtawyI cant sprint while in build mode how do i fix it i tried many things but it doesn’t work3 days ago
    • wd gasterim wd gaster from fortnite im gonna 360 noscope myself3 days ago

    Incident Details

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

    Incident Timeline

    Status changes during this incident

    1. Incident detected

      Sep 5, 2026, 2:13 PM UTC

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

      49 reports · 2 affected countries

    2. 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.

    3. Recovery confirmed

      Sep 5, 2026, 3:35 PM UTC

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

    4. Incident reopened

      Sep 5, 2026, 4:43 PM UTC

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

      50 reports · 1 affected countries

    5. Recovery being verified

      Sep 5, 2026, 5:32 PM UTC

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

    6. Recovery interrupted

      Sep 5, 2026, 5:40 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    7. Recovery being verified

      Sep 5, 2026, 6:39 PM UTC

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

    8. Recovery interrupted

      Sep 5, 2026, 6:53 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    9. Recovery being verified

      Sep 5, 2026, 7:20 PM UTC

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

    10. Recovery interrupted

      Sep 5, 2026, 7:28 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    11. Recovery being verified

      Sep 5, 2026, 7:45 PM UTC

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

    12. Recovery interrupted

      Sep 5, 2026, 8:01 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    13. Recovery being verified

      Sep 5, 2026, 8:14 PM UTC

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

    14. Recovery interrupted

      Sep 5, 2026, 8:40 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    15. Recovery being verified

      Sep 5, 2026, 8:55 PM UTC

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

    16. Recovery interrupted

      Sep 5, 2026, 9:02 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    17. 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.

    18. Recovery interrupted

      Sep 5, 2026, 9:31 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    19. Recovery being verified

      Sep 5, 2026, 9:45 PM UTC

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

    20. Recovery interrupted

      Sep 5, 2026, 10:03 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    21. 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.

    22. Recovery interrupted

      Sep 5, 2026, 10:31 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    23. Recovery being verified

      Sep 5, 2026, 10:50 PM UTC

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

    24. Recovery interrupted

      Sep 5, 2026, 10:56 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    25. Recovery being verified

      Sep 5, 2026, 11:00 PM UTC

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

    26. Recovery interrupted

      Sep 5, 2026, 11:01 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    27. 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.

    28. Recovery interrupted

      Sep 5, 2026, 11:28 PM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    29. 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.

    30. Recovery interrupted

      Sep 6, 2026, 12:26 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    31. Recovery being verified

      Sep 6, 2026, 12:40 AM UTC

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

    32. Recovery interrupted

      Sep 6, 2026, 12:47 AM UTC

      Recovery monitoring was interrupted because elevated reports returned.

    33. Recovery being verified

      Sep 6, 2026, 1:10 AM UTC

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

    34. Recovery confirmed

      Sep 6, 2026, 1:45 AM UTC

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

    35. Incident reopened

      Sep 6, 2026, 1:58 AM UTC

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

      59 reports · 1 affected countries

    36. Recovery being verified

      Sep 6, 2026, 2:11 AM UTC

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

    37. Recovery confirmed

      Sep 6, 2026, 2:46 AM UTC

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

    Impact Summary

    Reports
    49
    Countries
    2
    Top Issues
    Issue DistributionLag / High Ping: 42 reports (71.2%)Completely Down: 17 reports (28.8%)
    Lag / High Ping
    42(71%)
    Completely Down
    17(29%)

    Quick Links

    View Current Status