Is healthmatch.io down or not working?

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

What to do if the site healthmatch.io is not available? Try our guide.

healthmatch.io outage reports in the last 24 hours

healthmatch.io - 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:
HealthMatch - easily find the right clinical trial
Main page description:
Gain quick and easy access to clinical trials from a network of care teams around the world.
Protocol:
https
Status code:
200
Page size:
327.3 KB
Response time:
1.088sec.
IP:
54.236.67.102
Response headers:
date: Tue, 01 Oct 2024 12:55:58 GMT
content-type: text/html; charset=utf-8
content-length: 335185
connection: close
etag: W/"51d51-hHToEItI7sAM0nHLqxxEcP8+1jc"
vary: Accept-Encoding
DNS records:
A address44.217.144.154
ttl60
A address52.2.30.196
ttl60
A address54.236.67.102
ttl60
MX exchangealt2.aspmx.l.google.com
priority5
MX exchangeaspmx.l.google.com
priority1
MX exchangeaspmx3.googlemail.com
priority10
MX exchangealt1.aspmx.l.google.com
priority5
MX exchangeaspmx2.googlemail.com
priority10
NS valuens-197.awsdns-24.com
NS valuens-565.awsdns-06.net
NS valuens-1267.awsdns-30.org
NS valuens-1984.awsdns-56.co.uk
TXT entriesgoogle-site-verification=LZGHuM8FUgDb3mbVjglIQ6lZvl9vroYIe1h8Z6MXX5U
TXT entriesgoogle-site-verification=ldvNs00U0dq4SRk-iL1PDKr-AAS2cnwDI46zD3bmyK0
TXT entriestwilio-domain-verification=67f0ab69462ea8af75629975cfbbe486
TXT entriesv=spf1 include:mail.zendesk.com include:spf.mandrillapp.com include:_spf.google.com ~all
TXT entriesfacebook-domain-verification=u9rjy1it1ia3obvv8lg9ocbimu9rvj
TXT entriespinterest-site-verification=9a5a07e133bf019765fe083525f8d4a3
TXT entriesgoogle-site-verification=W3gru5fZq0bToNmHwylO0gNezJAgRlQUlR424LTRhZI
TXT entriesgoogle-site-verification=hnhFWkfA9e8gMwJbx9l4MkmyIkxA1qQEsuw7rsL1hEY
TXT entriesgoogle-site-verification=lJqdo_aluv-M7d2C7gjJha-44Gkn_HwKfwWbgphrlRA
SOA nsnamens-1984.awsdns-56.co.uk
hostmasterawsdns-hostmaster.amazon.com
serial1
refresh7200
retry900
expire1209600
minttl86400
CAA critical0
issuewildamazon.com

SEO headers

h6 Solutions
h6 Resources
h6 Clinical trials
h6 Topics
h6 Guides
h6 Solutions
h6 Resources
h1 Find clinical trials for you.

How to solve problems with healthmatch.io

Errors on the healthmatch.io 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 healthmatch.io on your own.