Repository navigation
repology.org domain appears to be on registrar hold (resolves to 127.0.0.1) #560
Description
Since about 2026-09-13 23:00 UTC, repology.org no longer resolves to the service:
- Cloudflare (1.1.1.1) and Google (8.8.8.8) return
A 127.0.0.1(still the case as of 2026-09-14) - NS (as seen earlier today):
dns9.parkpage.foundationapi.com,dns10.parkpage.foundationapi.com - SOA:
ns1.verification-hold.suspended-domain.com. admin.suspended-domain.com. - RDAP (PIR): registrar PDR Ltd., last changed
2026-09-13T23:01:26Z, expiration2027-09-13(seems to be right after the auto-renewal)
The server itself is still up: requests to 92.63.176.157 with the hostname forced get normal responses. So this looks like a registrar hold, maybe a pending registrant verification, not a service outage.
Impact: API clients such as Renovate's repology datasource get ECONNREFUSED for every lookup.
Pinned by AMDmi3
As mentioned in the issue, the host is alive at 92.63.176.157 / 2a03:6f01:1:2::f159, you can just add it to /etc/hosts in the meantime. Unfortunately, there's not much that can be done with the domain, we'll have to wait for registrar action. These addressed can be used if the domain problem recurs.
Activity
AMDmi3 commentedon Sep 14, 2026
I'm aware. My registrar is a scam, either migrating the domain from it or renewing it is a huge problem. Long downtime is to be expected.
hartwork commentedon Sep 14, 2026
@AMDmi3 my vote for pinning this issue. Many users will have the same question. Good luck with the domain! 🙏
iedame commentedon Sep 14, 2026
Oh no. Does Repology have any backup domains? @AMDmi3, let us know if donations for a backup domain would be helpful. I'm definitely missing having Repology available right now.
AMDmi3 commentedon Sep 14, 2026
As mentioned in the issue, the host is alive at
92.63.176.157/2a03:6f01:1:2::f159, you can just add it to/etc/hostsin the meantime. Unfortunately, there's not much that can be done with the domain, we'll have to wait for registrar action. These addressed can be used if the domain problem recurs.hartwork commentedon Sep 14, 2026
@AMDmi3 I think @iedame has an interesting point: Would it be hard to make the code to service say both repology.org and repology.net (that is still free) and start serving on repology.net while waiting for repology.org to come back? The key questions to me for a domain serving repology content would be: is it operated by you and are the links fully working (i.e. being relative or absolute with the same domain). What do you think?
AMDmi3 commentedon Sep 14, 2026
I'd really prefer to avoid introducing another domain. After it is introduced, some Repology consumers will switch to it, and after that, we'll either have support the domain forever, or make them switch again. In the latter case, we'll still have to support the domain forever not to lose it to squatters or spammers.
That said, this solution haven't come to my mind. Let's wait for at least a couple of days, if the problem is not solved, we can go this way.
CelestifyX commentedon Sep 14, 2026
@AMDmi3 Is it possible to use Repology without a domain? 92.63.176.15 is inactive.
solbu commentedon Sep 14, 2026
157 at the end, not 15. :-)
CelestifyX commentedon Sep 14, 2026
sorry, didn't finish writing
The webpage at https://92.63.176.157/ might be temporarily down or it may have moved permanently to a new web address.
solbu commentedon Sep 14, 2026
Being a hoster of a few site myself: Yes you need the domain. Hence why you need to edit the hosts file.
The IP address is just another site as far as Apache/Nginx is concerned.
CelestifyX commentedon Sep 14, 2026
thanks)
56 remaining items
bigbigmdm commentedon Oct 7, 2026
It might be worth displaying the IP address of the repology.org server here. We could then add it to /etc/hosts if the problem recurs.
solbu commentedon Oct 7, 2026
He did.
Its the third reply in this issue thread. :-)
AMDmi3 commentedon Oct 7, 2026
I've pinned that comment
uluzox commentedon Oct 8, 2026
I guess we can close this issue. Or do you think there are any open points @AMDmi3 ?
AMDmi3 commentedon Oct 8, 2026
I plan to close it on Friday along with repology.amdmi3.ru termination.
webapp: Remove announcement (#560)
Use temporary repology domain until the issue is resolved
AMDmi3 commentedon Oct 12, 2026
So the issue is resolved, main domain successfully renewed, temporary domain removed.
Note though that given what's currently going on, there's a nonzero probability that the next outage may be related to datacenter damage. That should be much less harmful though, as we can setup a new VPS in some European DC within hours. I'm reluctant to doing that proactively though as those are more expensive.