Sections

You are here: Home > Data & Tools > Legacy Projects > Archived Projects > DBConstat > DBConstat Statistics > Inet6num Objects with Wrong Status

Quick Links

RIPE Database Inconsistency Statistics

RIPE Database Search: By pressing the "Search" button you explicitly express your agreement with the RIPE Database Terms and Conditions.

RIPE NCC Survey 2013

Service Announcements

All of our services are operating normally.

New on RIPE Labs: IPv6 Security - An Overview Jun 18, 2013; Evaluating the Effectiveness of Happy Eyeballs Jun 13, 2013; How Many RIPE Atlas Probes Believe They Have IPv6 (But Are Wrong)? Jun 11, 2013; One Year Later: Who's Doing What With IPv6? Jun 05, 2013; RIPEstat Demo Summary: RIPE 66 May 21, 2013

Inet6num Objects with Wrong Status

01 Feb 2011

Valid status fields are defined in RIPE Database Manual The valid values are one of the following:

ALLOCATED-BY-RIR
ALLOCATED-BY-LIR
ASSIGNED

Example:

Consider the following objects: inet6num: 2001:FFFF:0000:0000::/60 status: SLA . . In this case, 2001:FFFF:0000:0000::/60 has a legacy wrong status line.

Yearly