Anchored Registry · corrections
If your organisation is on a page here
Write to oleg@anchoredregistry.com and a named person answers within one working day. Anything wrong is fixed. What follows is what counts as wrong, and the one thing this page does not offer.
First, which kind of wrong
| The situation | What happens |
|---|---|
| The page disagrees with the RIPE database | Our defect, fixed here. Send the URL — the page is corrected and the importer fixed so the same class of error does not return. |
| The page matches the RIPE database, and the database is wrong | Fixed in the registry, by whoever maintains the object. Every page here is rebuilt from RIPE’s published dumps, so correcting it at the source corrects this site and every other derived view at once. Tell us and we will confirm it landed. |
| Everything is accurate and you would rather not be listed | The entry stays. The reason is below, and it is not a brush-off. |
Why accurate entries stay
Because a directory with holes in it is worse than no directory. The organisations most likely to ask to be removed are the ones sponsoring hundreds of resources, and those are precisely the entries a person comparing sponsors needs to see. Take them out and the page still looks complete: the counts still add up, the ranking still reads as a ranking, and a visitor has no way to tell that the largest sponsors are missing. That is not neutrality, it is a page that misinforms while appearing not to.
Every fact here is one the RIPE NCC publishes about a resource, in a database that exists so the internet can tell who holds what. This site rearranges it and cites the file each fact came from. Rearranging public registry data is not the same as disclosing something, and a preference not to appear in someone else’s index is not the same as an error.
The exception, which is narrow
If an entry names a natural person rather than a company — a sole trader whose own name is the registered org-name — write and say so. That is a legal position rather than a preference, and it is treated as one. It is close to empty by construction: this directory reads no contact attribute and no person: object at all, which /data sets out in full.
What to send, and how it is checked
- Your organisation handle — ORG-XXXX-RIPE. Company names repeat across countries; the handle does not.
- The URL, and what the right value is.
- Requests are checked against the contact published on your own organisation object in the RIPE database. That is the one time a contact field is read at all, it is not stored, and it is used for nothing else. Writing from an address that is not on the record is sorted out by asking, not by refusing.
- A correction is applied where the data enters the site, so it holds through the daily rebuild rather than depending on anybody remembering it.
What this page is not
It is not a route to change the registry: only the maintainer of an object can do that, and it is not us — what this site holds is a read-only copy of what RIPE publishes. It is also not a sales channel. Writing here puts you on no list, because there is no list to be on and no contact data is kept from the dumps at all.
Tropynin Oleg · ORG-TO334-RIPE · AS41800