Is x.company down or not working?

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

What to do if the site x.company is not available? Try our guide.

x.company outage reports in the last 24 hours

x.company - 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

Main page title:
X, the moonshot factory
Main page description:
X, the moonshot factory develops radical new technologies to help solve the world's hardest problems. Learn more about X.
Protocol:
https
Status code:
200
Page size:
216.3 KB
Response time:
0.773sec.
IP:
216.239.32.21
Response headers:
content-type: text/html
vary: Accept-Encoding, Accept-Encoding
cache-control: public, max-age=0036
expires: Tue, 01 Oct 2024 11:37:56 GMT
last-modified: Fri, 07 Jun 2024 00:28:22 GMT
etag: "323fc32d9d413851d78b75b0940ea1ba"
accept-ranges: bytes
access-control-allow-origin: *
access-control-expose-headers: Origin, Accept, X-Requested-With, Authorization, Content-Type, Content-Length, Accept-Encoding, X-CSRF-Token
alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000, h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
x-fileset-blob: 38aa7d22e733356eff42f8330eaeee28a139ab7b
x-fileset-ref: f2072b7bd03d254dd1955dd4ab94ca6685a2e043
x-fileset-site: default
x-cloud-trace-context: 43d0be0d0048c8349c833c243cbc4c8f
date: Tue, 01 Oct 2024 10:37:56 GMT
server: Google Frontend
content-length: 221702
connection: close
DNS records:
A address216.239.34.21
ttl300
A address216.239.32.21
ttl300
A address216.239.36.21
ttl300
A address216.239.38.21
ttl300
AAAA address2001:4860:4802:36::15
ttl300
AAAA address2001:4860:4802:32::15
ttl300
AAAA address2001:4860:4802:38::15
ttl300
AAAA address2001:4860:4802:34::15
ttl300
NS valuens-cloud-c1.googledomains.com
NS valuens-cloud-c4.googledomains.com
NS valuens-cloud-c2.googledomains.com
NS valuens-cloud-c3.googledomains.com
TXT entriesv=spf1 -all
TXT entriesgoogle-site-verification=QPTBYJ46kd3VMsmIirA48bItUhbvIRG3EnC6cFX1iQw
SOA nsnamens-cloud-c1.googledomains.com
hostmastercloud-dns-hostmaster.google.com
serial1
refresh21600
retry3600
expire259200
minttl300

How to solve problems with x.company

Errors on the x.company 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 x.company on your own.