Flush your DNS cache: ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS.
Publisher status · statuspage
Epic Games / Fortnite status
Live incidents and maintenance pulled from the publisher's official status page.
OPERATIONAL
Checked 1s ago
single-source feed
every 5 min · publisher feed
direct probe, not crowd-reported
Publisher status
- Indicator
- none
- Description
- All Systems Operational
- Source
- https://status.epicgames.com
- Adapter
- statuspage
What this means
Epic Games / Fortnite reports no active incidents on its official status page.
This is the publisher's own classification. If you still can't connect, the issue may be network-local or specific to your region — publisher feeds don't always flag every user-visible problem.
What to try next
Check your DNS
Try another network
Switch between Wi-Fi and mobile data, or disable your VPN. If it works there, the issue is on your primary network.
Browser reset
Try an incognito window or a different browser — a bad extension or cached error page can masquerade as downtime.
Cross-check
Compare with Epic Games / Fortnite's official status page.
Official status page
status.epicgames.com Epic Games / Fortnite's official status pageFAQ
Why does this page show Epic Games / Fortnite as up while my game won't connect?
Publisher status pages show the publisher's view, not yours. Epic Games / Fortnite aggregates many internal signals; user-visible problems (matchmaker queues, regional CDN issues, account auth) sometimes don't trip the public indicator. Check the active incidents list below for narrower scope.
How is this different from a direct probe?
Websites and game servers get hit with a live network request. Publishers don't expose a single check endpoint, so we poll their official status feed (Statuspage, Riot, etc.) every 5 minutes and surface their classification verbatim.
Where does the data come from?
Directly from Epic Games / Fortnite's own status feed — see https://status.epicgames.com. We don't aggregate Twitter or DownDetector signals.
Related
Methodology
- Probe
- We poll the publisher's official status page endpoint (Statuspage.io JSON, Riot's status API, etc.) and read their own incident feed.
- Counts as DOWN
- The publisher reports a major or critical indicator, or the adapter returns a protocol error.
- Counts as DEGRADED
- The publisher reports minor issues or maintenance. Active incidents are listed even when the overall indicator is green.
- Detail
- Publisher checks differ from direct probing: we inherit the publisher's own classification. If Atlassian says "all systems operational" while users can't connect, our check will show up — the signal is theirs, not ours.
- Cadence
- Every 5 minutes, in parallel across 4 monitoring regions (US East Virginia, US West Oregon, Europe London, Asia Singapore).
- Rate-limited targets
- If a host returns 429 or consistently drops connections from our IPs, we cap retries at 3 and report the last observed status — we do not flood the target to confirm the outage.
- Data source
- Direct probes from our monitoring infrastructure. We do not aggregate crowd reports, Twitter mentions, or DownDetector signals — every result on this page is a live network request.