Is roti.com down or not working?

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

What to do if the site roti.com is not available? Try our guide.

roti.com outage reports in the last 24 hours

roti.com - 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:
31.1 KB
Response time:
0.622sec.
IP:
18.172.88.15
Response headers:
content-type: text/html
content-length: 31824
connection: close
date: Wed, 02 Oct 2024 19:51:06 GMT
server: AmazonS3
accept-ranges: bytes
etag: "f3997150abcf0afa18ba06168945cc71"
last-modified: Sat, 20 Apr 2024 18:12:54 GMT
cache-control: public, max-age=0, s-maxage=2
vary: Accept-Encoding
x-cache: Miss from cloudfront
via: 1.1 bb390afd921c223e0fe4921fbc23bbe8.cloudfront.net (CloudFront)
x-amz-cf-pop: PRG50-C1
alt-svc: h3=":443"; ma=86400
x-amz-cf-id: PnBj5PnhfWUNUPsOnsagYeQq_3OgyuJ-EAgFcN3v56fiNMMxqstLIw==
DNS records:
A address13.227.219.129
ttl60
A address13.227.219.107
ttl60
A address13.227.219.30
ttl60
A address13.227.219.2
ttl60
MX exchangeaspmx.l.google.com
priority1
MX exchangealt1.aspmx.l.google.com
priority5
MX exchangealt3.aspmx.l.google.com
priority10
MX exchangealt4.aspmx.l.google.com
priority10
MX exchangealt2.aspmx.l.google.com
priority5
NS valuens-915.awsdns-50.net
NS valuens-1998.awsdns-57.co.uk
NS valuens-17.awsdns-02.com
NS valuens-1111.awsdns-10.org
TXT entriesgoogle-site-verification=6eEXeOOH8_tJLnl4LfQrvw4H8vGbQtzU_59ZhbaWKIw
TXT entriesfacebook-domain-verification=jitr51hvrgzekyzy6p8o6dz3krw5ek
TXT entriesgoogle-site-verification=4l_27mmsjd5bcEWlRIJqU5XluxUhts1uMt1QE0vkrzY
TXT entriesv=spf1 include:spf.mandrillapp.com include:_spf.google.com include:spf.protection.outlook.com ~all
TXT entriesatlassian-domain-verification=1lxO2ysD0Eksmh9kxZ1icMmeNHXw11RseLzEq8DyTmGSreWr7iKqdqkOP3/UA2tA
SOA nsnamens-915.awsdns-50.net
hostmasterawsdns-hostmaster.amazon.com
serial1
refresh7200
retry900
expire1209600
minttl86400

How to solve problems with roti.com

Errors on the roti.com 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 roti.com on your own.