Is outage.report down or not working?

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

What to do if the site outage.report is not available? Try our guide.

outage.report outage reports in the last 24 hours

outage.report - 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:
Outage.Report
Main page description:
See if your provider or web service is having an outage or it's just you. Post yours and see other's reports and complaints
Protocol:
https
Status code:
200
Page size:
167.6 KB
Response time:
0.946sec.
IP:
3.160.39.34
Response headers:
content-type: text/html
content-length: 171979
connection: close
date: Tue, 01 Oct 2024 16:51:05 GMT
x-amzn-requestid: 255b75a9-681f-49ae-937a-6a44bae61708
x-amzn-trace-id: Root=1-66fc2879-46aaa79a164f49c7267f70c5;Parent=413d0be0cc7fc9c4;Sampled=0;Lineage=1:a58a0bba:0
vary: Accept-Encoding
x-cache: Miss from cloudfront
via: 1.1 bb72e3b71c64099edd81bafe5ceefcf2.cloudfront.net (CloudFront)
x-amz-cf-pop: TXL50-P6
x-amz-cf-id: O0ZKoBz9Y0Lk3b9NhkD3AImVGlLEJNaBOEk88hYqAj5os8ft7zFPQA==
DNS records:
A address18.239.83.107
ttl60
A address18.239.83.98
ttl60
A address18.239.83.116
ttl60
A address18.239.83.120
ttl60
MX exchangealt2.aspmx.l.google.com
priority5
MX exchangealt4.aspmx.l.google.com
priority10
MX exchangeaspmx.l.google.com
priority1
MX exchangealt3.aspmx.l.google.com
priority10
MX exchangealt1.aspmx.l.google.com
priority5
NS valuens-503.awsdns-62.com
NS valuens-1914.awsdns-47.co.uk
NS valuens-862.awsdns-43.net
NS valuens-1102.awsdns-09.org
TXT entriesgoogle-site-verification=sP--w5VTmGyHlRgcS_TrFUJjv3zk0UDiUCGl0eiw7n4
SOA nsnamens-503.awsdns-62.com
hostmasterawsdns-hostmaster.amazon.com
serial1
refresh7200
retry900
expire1209600
minttl86400

SEO headers

h1 Recent Incidents

How to solve problems with outage.report

Errors on the outage.report 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 outage.report on your own.