bgpreport

Network · data from 2026-11-12

AS30176 Priority Colo AS30176

Registry name: AS-PRIORITYCOLO - Priority Colo Inc, CA · PeeringDB

6IPv4 routes 83.3% RPKI valid · 83.3% with a route object
2IPv6 routes 50.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS30176, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS30176, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

206.130.11.0/24 No ROA Other origin only 41 6%low visibility 29
2607:f698::/31 No ROA RIR databaseARIN 634 100% 69
67.223.96.0/20 Valid RIR databaseARIN 673 100% 67
204.11.48.0/21 Valid RIR databaseARIN 673 100% 67
204.15.192.0/21 Valid RIR databaseARIN, RADB 673 100% 67
130.51.12.0/22 Valid RIR databaseARIN 671 100% 67
192.81.56.0/23 Valid RIR databaseARIN 671 100% 67
2607:f698::/32 Valid RIR databaseARIN 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS30176: AS30176. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS30176 isn't in the set, or no route object for AS30176 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS30176 in itNot covered
AS30176 A single AS number, not a set: AS30176 (this network), 9 route objects.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 5 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none206.130.11.0/24No ROA covers it. Add a ROA for AS30176, maxLength 24.41 of 673
Route object: none206.130.11.0/24Route objects for it name AS19752, AS30645. Add a route object with origin AS30176 in the RIR database for the space.41 of 673
ROA: none2607:f698::/31No ROA covers it. Add a ROA for AS30176, maxLength 31.634 of 636

Route objects not announced

Route objects with origin AS30176 whose prefix no peer sees AS30176 announce. Many are kept on purpose (backup routes, space announced only in some places).

192.231.5.0/24ARINValid
2604:bc0:4::/48ARINInvalid: origin

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.