Skip to content

Is Chrome for Developers down right now?

developer.chrome.com

Checking developer.chrome.com…

Asking our locations to reach the site. This takes a few seconds.

Uptime, 24 hours
100 %
Uptime, 7 days
100 %
Uptime, 30 days
100 %

Based on 1 day of checks so far. Checks that failed because of how we test, not because of the site, are left out.

Response time, last 24 hours

2026-10-09 11:03 UTC: 354 ms2026-10-09 11:19 UTC: 434 ms2026-10-09 11:34 UTC: 388 ms2026-10-09 11:50 UTC: 449 ms2026-10-09 12:06 UTC: 621 ms2026-10-09 12:21 UTC: 542 ms
Green: response time, full height at 810 ms or more. Red: down. Amber: not confirmed.

Response time by location, last 24 hours

LocationAverage responseReached
Berlin 1, Germany479 ms6 of 6 checks
Falkenstein, Germany490 ms6 of 6 checks
Berlin 2, Germany499 ms6 of 6 checks

Each check runs from all locations at once. A location far from the site’s servers answers later; that says nothing about the site being slow.

Outage history

No confirmed outage on record. An outage is listed once Chrome for Developers could not be reached from at least two locations in two checks in a row.

Recent checks

TimeStatusLocationsResponse
2026-10-09 12:21 UTCUp3 of 3542 ms
2026-10-09 12:06 UTCUp3 of 3621 ms
2026-10-09 11:50 UTCUp3 of 3449 ms
2026-10-09 11:34 UTCUp3 of 3388 ms
2026-10-09 11:19 UTCUp3 of 3434 ms
2026-10-09 11:03 UTCUp3 of 3354 ms

Comments

0/500 · no links · do not post personal data

No comments yet. Be the first to say what you are seeing.

About Chrome for Developers

Chrome for Developers

Helping you build, grow and innovate on the web.

Visit developer.chrome.comTitle and description as published by the site.

We can reach it, but you cannot?
  • Reload the page without the cache: Ctrl + F5 on Windows, Cmd + Shift + R on a Mac.
  • Open the site in a private window. If it works there, clear the cookies and cache for developer.chrome.com.
  • Try another network, such as mobile data. If that works, the problem is with your provider or router.
  • Switch to a public DNS resolver such as 1.1.1.1 or 8.8.8.8, then flush your DNS cache.
  • Turn off VPNs, proxies and ad blockers for a moment. Some sites refuse those connections.
Embed a status badge

Show the current status of Chrome for Developers on your own page or in a README. The badge updates by itself.

Status of developer.chrome.com

Similar sites