Enter a prefix. We compare BGP, RPKI and IRR route objects and tell you what looks good and what needs cleanup.
Old route objects stay behind and nobody removes them.
Mismatched records cause outages, rejected announcements and hijack risk.
Checking each registry yourself takes time.
One prefix at a time, with a clear answer.
One at a time, or several.
BGP origin, RPKI status, route objects and a plain verdict.
Email the maintainer to remove it, or set an alert for route changes.
Registry, origin, status and advice, with the maintainer's contact.
Every row ends with plain advice on what to do.
Get an alert when a route is added, removed or changed.
Each result shows when it was last checked.
BGP, RPKI and IRR together.
RIPEstat for BGP, IRR mirrors for route objects.
What to clean up, in words.
A ready-to-send cleanup note.
Route added, removed or changed.
Registry and maintainer contacts on each result.
A record in a routing registry that says which network may announce a prefix. Stale ones can cause problems.
A way to sign who is allowed to originate a prefix, so others can reject false announcements.
We show you what to clean up and give you the maintainer's contact, so you can request the removal.
RIPE, RADB and others read through IRR mirrors.