Is web.dev down or not working?

What happened to web.dev, why did the website go down and not work? Here you can see who else is having the same problem with web.dev, as well as possible solutions. According to our statistics, the following most often do not work: Website, Login, Account, Mobile App.

Current status: No failures

At the moment, according to our data, web.dev is working fine, but single failures are possible. If web.dev does not work for you, then report your problem and write a comment.

Add comment

What to do if the site web.dev is not available? Try our guide.

web.dev outage reports in the last 24 hours

web.dev - error and failure reports, troubleshooting methods

Leave your comment describing the failure and share with other users how to solve the problem.

No registration required.
Messages with obscene language and insults, as well as breaking the law, are not allowed to be published.
Active links in the text of the message are not published, but displayed in plain text.
It is forbidden to post your own and other people's personal data: addresses, phone numbers, emails, accounts in instant messengers, etc.

Your name:

Message:

Technical information

Main page title:

web.dev

Main page description:

Guidance to build modern web experiences that work on any browser.

Protocol:

https

Status code:

200

Page size:

86.7 KB

Response time:

0.766sec.

IP:

216.239.32.27

Response headers:

last-modified:	Wed, 11 Sep 2024 13:46:58 GMT
content-type:	text/html; charset=utf-8
vary:	Cookie
set-cookie:	_ga_devsite=GA1.2.641123393.1727736603; Expires=Wed, 30 Sep 2026 22:50:03 GMT; Max-Age=63072000; Path=/
content-security-policy:	base-uri 'self'; object-src 'none'; script-src 'strict-dynamic' 'unsafe-inline' https: http: 'nonce-5/8Z2wIKU5dkEC6QBLVcnIUmo2YwTQ' 'unsafe-eval'; report-uri https://csp.withgoogle.com/csp/devsite/v2
strict-transport-security:	max-age=63072000; includeSubdomains; preload
x-frame-options:	SAMEORIGIN
x-xss-protection:	0
x-content-type-options:	nosniff
cache-control:	no-cache, must-revalidate
expires:	0
pragma:	no-cache
x-cloud-trace-context:	2366737f29ca9c772fac9b5e5e43ffc0
date:	Mon, 30 Sep 2024 22:50:03 GMT
server:	Google Frontend
content-length:	88958
alt-svc:	h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
connection:	close

DNS records:

A	address	216.239.32.27
A	ttl	300
AAAA	address	2001:4860:4802:32::1b
AAAA	ttl	300
NS	value	ns2.zdns.google
NS	value	ns1.zdns.google
NS	value	ns3.zdns.google
NS	value	ns4.zdns.google
TXT	entries	google-site-verification=1KUpoM0U9uMGLkzIL1CaCnZDapQByrD74Wr92wrYZdA
SOA	nsname	ns1.zdns.google
	hostmaster	cloud-dns-hostmaster.google.com
	serial	1
	refresh	21600
	retry	3600
	expire	259200
	minttl	300
CAA	critical	0
CAA	issue	pki.goog
CAA	critical	0
CAA	issue	letsencrypt.org

SEO headers

h3 Building a better web, together

h3 Thanks for tuning in to Google I/O

h3 A new way to measure interaction responsiveness

h2 What's new?

h3 Introducing Baseline

h3 New to the web platform in April.

h3 The CSS Podcast

h2 CSS and UI design

h3 Adapting typography to user preference using CSS

h3 New CSS color spaces and functions in all major engines

h3 What are source maps?

h3 CSS subgrid

h2 Core Web Vitals

h3 Interaction to Next Paint becomes a Core Web Vital on March 12

h3 How to optimize INP

h3 Our top Core Web Vitals recommendations for 2023

h3 Use the Web Vitals extension to debug Core Web Vitals issues.

h2 Progressive Web Apps

h3 Learn PWA

h3 TransformStream is now supported cross browser.

h3 New patterns for amazing apps

h3 Project Fugu API showcase

h2 Accessible for all

h3 Learn Accessibility

h3 Testing web design color contrast

h3 Building the main navigation for a website

h3 Community highlight: Melanie Sumner

h2 Payments and identity

h3 Create a passkey for passwordless logins

h3 Sign in with a passkey

h3 Web payments overview

h3 Payment and address form best practices

h2 Developer Newsletter

h3 web.dev

h3 Contribute

h3 Related Content

h3 Follow

How to solve problems with web.dev

Errors on the web.dev website can be either on the server side or on your side (client side). If there is practically nothing to be done about errors on the server side (it remains only to wait for the site to work again), then with errors on the client side it is possible to solve the problem with the availability of web.dev on your own.