Is chromium.org down or not working?

What happened to chromium.org, why did the website go down and not work? Here you can see who else is having the same problem with chromium.org, 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, chromium.org is working fine, but single failures are possible. If chromium.org does not work for you, then report your problem and write a comment.
Add comment

What to do if the site chromium.org is not available? Try our guide.

chromium.org outage reports in the last 24 hours

chromium.org - 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.

Technical information

Protocol:
https
Status code:
200
Page size:
0.1 KB
Response time:
0.122sec.
IP:
199.36.158.100
Response headers:
connection: close
content-length: 124
cache-control: max-age=3600
content-security-policy: script-src 'sha256-1az3CiAdXAaMP3TFl5msfrDjNuSHMdg1ecAgxfZPR50=' 'unsafe-inline' 'strict-dynamic'; object-src 'none'; base-uri 'none'; report-uri https://csp.withgoogle.com/csp/chromium-website/
content-type: text/html; charset=utf-8
etag: "18634b5864b729ef21f79ed2606138a33deee417985e026a7acd91acba601331"
last-modified: Fri, 27 Sep 2024 08:21:23 GMT
strict-transport-security: max-age=31556926
accept-ranges: bytes
date: Tue, 01 Oct 2024 01:45:24 GMT
x-served-by: cache-ams2100115-AMS
x-cache: HIT
x-cache-hits: 0
x-timer: S1727747124.414523,VS0,VE1
vary: x-fh-requested-host, accept-encoding
alt-svc: h3=":443";ma=86400,h3-29=":443";ma=86400,h3-27=":443";ma=86400
DNS records:
A address199.36.158.100
ttl300
AAAA address2620:0:890::100
ttl300
MX exchangeaspmx2.googlemail.com
priority30
MX exchangealt2.aspmx.l.google.com
priority20
MX exchangeaspmx3.googlemail.com
priority30
MX exchangeaspmx.l.google.com
priority10
MX exchangeaspmx4.googlemail.com
priority30
MX exchangealt1.aspmx.l.google.com
priority20
MX exchangeaspmx5.googlemail.com
priority30
NS valuens3.google.com
NS valuens2.google.com
NS valuens1.google.com
NS valuens4.google.com
TXT entriesgoogle-site-verification=GHWufxo4fKLhMJ-7uU3j6-Q0mJB3Rf6advbw1fbGvwg
TXT entriesgoogle-site-verification=oLhUv4dhF94lh_6AJjtQqbdl6roQsWpJjEsrV_m9OQE
TXT entriesgoogle-site-verification=i-w1cugYtxowXeGc800b00b60wGG3ScxaFyIeCeYnaQ
TXT entriesgoogle-site-verification=wzG5-PgarwdLkOAS0Aq4lnKLBt4hORCbqGJadjhF8ss
TXT entriesgoogle-site-verification=h1opXSxJSUMZFGWcXMRzEdMI1KwD7bV6jsUIP3HdrjU
TXT entriesgoogle-site-verification=ESg9pU1dTKS3fnX5yab6qWe8MRdwh7FRedd8wQeyfBA
TXT entriesv=spf1 include:_spf.google.com ?all
SOA nsnamens1.google.com
hostmasterdns-admin.google.com
serial680195848
refresh900
retry900
expire1800
minttl60
CAA critical0
issuepki.goog

How to solve problems with chromium.org

Errors on the chromium.org 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 chromium.org on your own.