Routy's tracking service did not answer on your custom domain
Routy checks your custom tracking domain from the public internet every few minutes. This issue means the domain and its secure connection work, but Routy's own tracking service did not answer correctly on it.
What it means
Our check asked Routy's tracking service, through your domain, for a simple health response and got something else: an error status (such as HTTP 403 or 404), an unexpected reply, or no reply in time. The issue message names the domain and the response.
The service that failed to answer is Routy's, not your website or your hosting. The notification you receive is titled Domain Down.
Why it happens
Most common first:
- A routing problem on our side, so requests for your domain did not reach the tracking service. Routy tries to repair this automatically before it raises the issue.
- A proxy or firewall you run in front of the domain answered our check with an error instead of passing it to Routy.
- A short outage of the tracking service.
What we're doing
This is almost always on our side. When the check fails, Routy re-creates the routing for your domain automatically and alerts our team if it keeps failing. You do not need to change anything.
One thing to check yourself: if you put your own proxy or CDN in front of the domain, make sure the DNS record points directly at the target Routy gave you during setup (Cloaked links), without the proxy turned on.
Contact support if the issue stays open for more than a few hours, or if your links are failing for real visitors.
When it clears
Automatically. As soon as a check gets the right answer from the tracking service, the issue closes and you get a Domain recovered notification. The check runs every few minutes. A domain that has been failing for more than a week is only checked about once a day, so it can then take up to a day to clear.
If nothing detects the problem again for 30 minutes, the issue also closes on its own. If the domain is still broken, it opens again at the next check.