Summary

  • RIPE NCC has added a resource tree and automated checks to My Resources, bringing registrations and routing observations into one view.
  • RIPE's own designers warn that unexamined children must not look healthy and a missing exact route-object match can reflect an intended routing configuration.

The registry now has a dashboard with opinions. In its October member update, RIPE NCC announced a tree view and resource checks in My Resources. An allocation opens into its more-specific pieces; a side panel gathers registration, utilisation, database objects and routing details. The flat list has been replaced by a map of how one resource sits inside another.

The checks can be useful. RIPE's design account names announced IPv6 allocations with no registered usage, ASNs absent from the observed BGP table, and address space in use that may require assignment registration. These are reasons to investigate. Put them in one place and a member has less excuse to miss an awkward entry buried three levels down.

The hard part begins when the screen appears to know more than it has checked. Large resource trees can require many API calls, RIPE says, so some child branches may not yet have been examined. A green-looking parent beside an unexamined child would tell a comforting story the system has not earned. RIPE's designers explicitly raise this problem. The honest color for “we have not looked” is its own state, not borrowed reassurance.

They found a second trap in route objects. A route object may cover a prefix, sit beneath it, or use another legitimate arrangement. A missing exact match therefore makes a poor automatic accusation. RIPE describes replacing a blunt issue label with neutral information such as “No exact match found”, while showing related objects in a hierarchy. Orange marks something to review; green conveys a positive check; neutral information asks for interpretation. Those distinctions are part of the tool's governance, because an operator may treat a colored badge as a direction to change a registration.

For a member, the right response is to open the branch, read the check's evidence and status, then compare it with the actual allocation and routing plan. For RIPE, the next test is whether people can tell “needs review” from “not examined” when the tree grows large. A quiet dashboard can be more accurate than a loud one. The registry's job here is to point to the questionable line and let its owner explain it.