Is wttr.in down or not working?

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

What to do if the site wttr.in is not available? Try our guide.

wttr.in outage reports in the last 24 hours

wttr.in - 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:
Weather report: not found
Protocol:
https
Status code:
200
Page size:
26.3 KB
Response time:
0.416sec.
IP:
5.9.243.187
Response headers:
access-control-allow-origin: *
content-length: 29575
content-type: text/html; charset=utf-8
date: Mon, 07 Oct 2024 22:04:12 GMT
connection: close
DNS records:
A address5.9.243.187
ttl3600
MX exchangechub.in
priority10
NS valuensc2.srv53.com
NS valuensd4.srv53.com
NS valuensd4.srv53.org
NS valuensb3.srv53.org
NS valuensb4.srv53.com
NS valuensa1.srv53.com
NS valuensa3.srv53.org
NS valuensb1.srv53.net
NS valuensd2.srv53.net
NS valuensc2.srv53.net
NS valuensc3.srv53.org
NS valuensa3.srv53.net
SOA nsnamensa3.srv53.net
hostmastersupport.dnshosting.org
serial1726333019
refresh1800
retry600
expire2419200
minttl1800

How to solve problems with wttr.in

Errors on the wttr.in 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 wttr.in on your own.