Is xarelto-us.com down or not working?

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

What to do if the site xarelto-us.com is not available? Try our guide.

xarelto-us.com outage reports in the last 24 hours

xarelto-us.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

Main page title:
XARELTO® (rivaroxaban) | Official Patient Website
Main page description:
XARELTO® (rivaroxaban) Official Patient Website. See full Prescribing & Safety Info, including Boxed Warnings.
Protocol:
https
Status code:
200
Page size:
4.2 KB
Response time:
0.422sec.
IP:
172.64.146.37
Response headers:
date: Thu, 03 Oct 2024 03:34:49 GMT
content-type: text/html
transfer-encoding: chunked
connection: close
cf-ray: 8cc9e0ef5a281c8e-AMS
cf-cache-status: DYNAMIC
age: 86177
cache-control: public, max-age=7889400
etag: W/"fdbb46247b6bfe84303143dca6edc684"
last-modified: Wed, 25 Sep 2024 10:51:10 GMT
strict-transport-security: max-age=63072000; includeSubDomains; preload
vary: Accept-Encoding
via: 1.1 054609fe51831eb8825d39133f1a4c84.cloudfront.net (CloudFront)
content-security-policy: default-src *; script-src * 'unsafe-eval' 'self' 'unsafe-inline' https:; style-src * 'unsafe-inline'; object-src 'self' *.youtube.com youtube.com; img-src * data:; frame-src * blob:; font-src * data:; connect-src *; media-src * blob:; worker-src 'self' blob:; frame-ancestors 'self' *.eq5trck.com *.pulsepoint.com;
origin-trial: AgFQuf4mDUoYbYbxfDSPtNUX0lUTx60vacf2yr4HOagA+Ise+042sca3k8dhtI0xmVqBj8piIhXoLT3Ip+Qq3QYAAABpeyJvcmlnaW4iOiJodHRwczovL3hhcmVsdG8tdXMuY29tOjQ0MyIsImZlYXR1cmUiOiJNdXRhdGlvbkV2ZW50cyIsImV4cGlyeSI6MTc0NzE4MDc5OSwiaXNTdWJkb21haW4iOnRydWV9, AgFQuf4mDUoYbYbxfDSPtNUX0lUTx60vacf2yr4HOagA+Ise+042sca3k8dhtI0xmVqBj8piIhXoLT3Ip+Qq3QYAAABpeyJvcmlnaW4iOiJodHRwczovL3hhcmVsdG8tdXMuY29tOjQ0MyIsImZlYXR1cmUiOiJNdXRhdGlvbkV2ZW50cyIsImV4cGlyeSI6MTc0NzE4MDc5OSwiaXNTdWJkb21haW4iOnRydWV9
referrer-policy: strict-origin-when-cross-origin
x-amz-cf-id: RPMfOrmctMiF-g4-QLiUuL5AHDow5nBJiDQLr6Ul70JFd59xvUKGdQ==
x-amz-cf-pop: AMS1-P3
x-amz-server-side-encryption: AES256
x-cache: Hit from cloudfront
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-robots-tag: index, follow
x-xss-protection: 1; mode=block
server: cloudflare
DNS records:
MX exchangemx1.jnj-sd.iphmx.com
priority5
MX exchangemx2.jnj-sd.iphmx.com
priority5
NS valuens5.jnj.com
NS valuens3.jnj.com
NS valuens1.jnj.com
TXT entriesv=spf1 include:%{d}.ce.spf-protect.dmp.cisco.com exists:%{i}._i.%{d}._d.espf.dmp.cisco.com -all
TXT entriesMS=ms77341500
SOA nsnamens1.jnj.com
hostmasterextdnsreqs.its.jnj.com
serial2016091642
refresh7200
retry1800
expire2592000
minttl1800

How to solve problems with xarelto-us.com

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