Is goodrx.com down or not working?

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

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

goodrx.com outage reports in the last 24 hours

goodrx.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:
GoodRx - Error
Protocol:
https
Status code:
200
Page size:
183.3 KB
Response time:
0.692sec.
IP:
151.101.130.49
Response headers:
content-type: text/html
content-length: 187700
connection: close
vary: Accept-Encoding
x-amz-id-2: +8r2o7fAs7bBQ49kjSZbEAn1dIknMrafjl+M8pc1Nge9ht0YV71ZPn3d+iMf0P6FAYrIUos95cg=
x-amz-request-id: R595SD1QA25J0HMP
date: Mon, 30 Sep 2024 20:45:59 GMT
last-modified: Wed, 05 Jun 2019 20:11:55 GMT
etag: "cfe9833e9b05de6fe14f54ffa14b1816"
server: AmazonS3
x-cache: Miss from cloudfront
via: 1.1 a60a14dea4b4a9f77d34297a625f2e24.cloudfront.net (CloudFront)
x-amz-cf-pop: PRG50-C1
x-amz-cf-id: azHVySTX53wS78lsW4y7iySpsmOp0dSZywlCu7-Fngjs0YfEvgiAfA==
x-xss-protection: 1; mode=block
x-frame-options: SAMEORIGIN
referrer-policy: no-referrer
content-security-policy: default-src 'self' data:; style-src 'unsafe-inline'
x-content-type-options: nosniff
strict-transport-security: max-age=31536000; includeSubDomains; preload
DNS records:
A address151.101.66.49
ttl300
A address151.101.130.49
ttl300
A address151.101.2.49
ttl300
A address151.101.194.49
ttl300
MX exchangealt2.aspmx.l.google.com
priority30
MX exchangeaspmx.l.google.com
priority10
MX exchangealt1.aspmx.l.google.com
priority20
MX exchangeaspmx2.googlemail.com
priority40
MX exchangeaspmx3.googlemail.com
priority50
NS valuens-1404.awsdns-47.org
NS valuens-411.awsdns-51.com
NS valuens-1770.awsdns-29.co.uk
NS valuens-594.awsdns-10.net
TXT entriesv=spf1 include:m.lessonly.com include:_spf.google.com include:_spf.salesforce.com include:mail.zendesk.com include:sendgrid.net include:mailgun.org include:b998a4.workshop-spf.net include:_spf.chargedesk.com ip4:160.72.30.82 ip4:167.89.73.35 -all
TXT entries_globalsign-domain-verification=4azHJ7gL04Dr8r2VR0txu7OrWg7uZpU6v7LOHVP1b3
TXT entriesgoogle-site-verification=xhRHduR1IfH9UIlEClofM-R-ukQQ3yuJuwn_JqbWTmU
TXT entriesopenai-domain-verification=dv-9TQ9DVJypJqUQb9lug2Tu1e2
TXT entriesCD745DDA6C
TXT entriesgoogle-site-verification=Mjmo1EMQg89B931bJmnEpVyMIZlngfjuhtKTHvSMgw4
TXT entriesgoogle-site-verification=0HCfwSPj99hPK2yKZqYCLXOCYXXMrDZr3H6fFI56oZI
TXT entriesstripe-verification=3bd0217d2646323c46fb8c55b674d399499e6b97063719d744d6d6d7cc1f532c
TXT entriesdocusign=bc2f92c6-e126-439d-918f-ceccb3909d28
TXT entriesh1-domain-verification=NE5J5mTjq7vxd8oPEvFcQDCVemeexUvvMhanigzeRtYTXhxr
TXT entriesMS=BBF593DDF48464506A198736777B968B5C933992
TXT entriesfacebook-domain-verification=upfrxujlwdu8yotvu41uzim4mzqsm9
TXT entries_globalsign-domain-verification=BHpWxHhQlVmC0Qh679dy4Ss6Rgh7znn8Rq7XF2qe6V
TXT entriesF283923BA6
TXT entriesapple-domain-verification=aWJonu6lBJVo6anY
TXT entriesapple-domain-verification=Qip7T4LAJgt76ts9
TXT entriesloaderio=26b05173dbe31e0d1552a5c3dbfa7e1a
TXT entriesstripe-verification=7b539566b7b4d8fcaf55e833195b2352d378655a9f93d95a74180858ab6efc39
TXT entriesmiro-verification=2d3569e77447fd807da9602fa827b0cf82de31d2
TXT entriesgoogle-site-verification=pL6OmFqrVMwY6amd-IYSjsukCOb_vMhns4NAC_Ltu_E
TXT entries_globalsign-domain-verification=iRl7LRCkBgH6_cc6FljPk98rDj2QFqhK5SbtgchBGh
TXT entries_globalsign-domain-verification=VmtaawP5k5JRiQ4X3iyQWrLP5VRAybwdCbW8PcvrGu
TXT entriesonetrust-domain-verification=4fdc4e24d37a486f8fbf0f49528b85f6
TXT entries_globalsign-domain-verification=-lBuNJDFRxDkLkNbYOLBU03PlWjnPqAzBPAVUokhAw
TXT entriesgoogle-site-verification=hTK8ceNUKqLpYfLyI03CBFj41L1qdeYLGTHMpjhHkKM
TXT entriesatlassian-domain-verification=tny5glhS7sb0s6V0eqgbjuVB0zt6vt+iBoIk56eEto2HPIUgQdOiZvGjP2Wayst+
SOA nsnamens-411.awsdns-51.com
hostmasterawsdns-hostmaster.amazon.com
serial1
refresh7200
retry900
expire1209600
minttl86400

How to solve problems with goodrx.com

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