Skip to content

Is MDN Web Docs down? Live status and outage map

developer.mozilla.orgDeveloper toolsChecked every 5 minutes

No, MDN Web Docs is up right now.

It answered in 271 ms. If it isn't working for you, the problem is probably on your side, so see what to try below.

Checked from EU (Falkenstein) · Check from other countries

Not working for you? Tell others what's wrong. Reports are anonymous; we don't store IP addresses.

Response time
271msHTTP 200 OK
Uptime, 24 hours
100%20 checks
Uptime, 30 days
100%20 checks
SSL certificate
49daysValid until Dec 22, 2026

Notify me when MDN Web Docs is down

Leave your email and we'll write to you when our checks find MDN Web Docs down. No account needed.

We use your email only for this. Privacy

MDN Web Docs outage map

ReachableProblems or reportsUnreachable

Reached from EU (Falkenstein)

The big dot is our server in EU (Falkenstein), which decides the status above. Small dots are home and mobile connections, one per country. Countries are shaded as visitors run the connection test below or report problems.

Check from other countries

0 of 5 picked

Pick up to 5 countries and watch them on the map. One home or mobile connection in each opens developer.mozilla.org through Globalping, so you can see whether a problem is limited to some places. You can do this 3 times an hour.

Last 24 hours

UpProblemsDownNo data
24h agoNo problems detectedNow
Typical 181 msFastest 98 msSlowest 246 ms
300 ms150 ms
24h ago18h12h6hNow

Last 15 checks

Newest first
The latest checks of MDN Web Docs
TimeResultResponse
ScheduledUp271 ms
ScheduledUp204 ms
ScheduledUp149 ms
ScheduledUp198 ms
ScheduledUp322 ms
ScheduledUp92 ms
ScheduledUp86 ms
ScheduledUp173 ms
ScheduledUp110 ms
ScheduledUp122 ms
ScheduledUp88 ms
ScheduledUp83 ms
ScheduledUp105 ms
ScheduledUp137 ms
ScheduledUp190 ms

Test from your connection

Your browser tries to reach developer.mozilla.org directly, the same way it would if you opened it. We compare that with our own check to tell whether the problem is the site or your connection.

We record only whether the test worked, how long it took and your country. Ad blockers can block the test for some sites.

Problem reports

Nobody has reported a problem with MDN Web Docs in the last 7 days. If it isn't working for you, say so at the top of this page.

Comments

Plain text only. Links and email addresses can't be posted.0/500

No comments yet

Describe what isn't working with MDN Web Docs to help the next person.

MDN Web Docs outage history

Last 90 days

No outages in the last 90 days

Every scheduled check of MDN Web Docs has been answered since we started monitoring it.

If MDN Web Docs isn't working for you

  • Reload without the cache

    Press Ctrl+F5 on Windows or Cmd+Shift+R on a Mac, or open the site in a private window.

  • Try another network

    Switch between Wi-Fi and mobile data. If it works on one, the problem is your network or provider.

  • Pause extensions and VPN

    Ad blockers, VPNs and proxies are common causes of sites failing to load.

  • Restart the app or device

    For mobile apps, also check for an update.

  • Check your clock

    A wrong date or time on your device breaks secure connections.

  • Refresh your DNS

    If only MDN Web Docs fails, restart your router or switch to a public DNS resolver.

Common questions about MDN Web Docs

Is MDN Web Docs down for everyone or just for me?
Most likely just you. MDN Web Docs answered our server in EU (Falkenstein) on its last check. Use "Test from your connection" on this page to see whether your own browser can reach developer.mozilla.org.
What problems do people report with MDN Web Docs?
Nobody has reported a problem in the last 7 days. If MDN Web Docs isn't working for you, add a report at the top of this page so the next visitor knows.
How often does MDN Web Docs go down?
Over the last 30 days MDN Web Docs was reachable in 100% of our 20 scheduled checks. We have not logged an outage in the last 90 days.
How do you check whether MDN Web Docs is down?
Every 5 minutes our server in EU (Falkenstein) looks up developer.mozilla.org, connects to it and times how long the homepage takes to start answering. A failed check is repeated before it counts as an outage.