bgpreport

Network · data from 2026-11-12

AS55016 Imperium

Registry name: IMPER-AS-1 - Imperium Inc., CA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55016, 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.

204.50.103.0/24 Invalid: origin RIR databaseARIN 46 7%low visibility 29
44.31.26.0/24 No ROA Other IRR onlyALTDB 668 99% 67
44.184.136.0/24 No ROA Other IRR onlyALTDB 668 99% 67
44.184.137.0/24 No ROA Other IRR onlyALTDB 668 99% 67
44.184.138.0/24 No ROA Other IRR onlyALTDB 668 99% 67
44.184.139.0/24 No ROA Other IRR onlyALTDB 668 99% 67
208.44.192.0/24 No ROA RIR databaseARIN 668 99% 67
23.167.224.0/24 Valid RIR databaseALTDB, ARIN 668 99% 67
162.208.88.0/24 Valid RIR databaseALTDB, ARIN 668 99% 67
162.208.89.0/24 Valid RIR databaseALTDB, ARIN 668 99% 67
162.208.90.0/24 Valid RIR databaseALTDB, ARIN 668 99% 67
162.208.91.0/24 Valid RIR databaseALTDB, ARIN, RADB 668 99% 67

AS-SET

PeeringDB's irr_as_set for AS55016: AS-IMPERIUM. 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 (AS55016 isn't in the set, or no route object for AS55016 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 objectsAS55016 in itNot covered
AS-IMPERIUM ALTDB 1116 Yes 0
ARIN (also) 1116 Yes 0

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 16 are in fix.csv.

  • ROA: origin1
  • ROA: none6
  • Route object: RIR5
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin204.50.103.0/24ROAs covering it name AS812, not AS55016. If AS55016 should announce it, add a ROA for AS55016.46 of 673
ROA: none44.31.26.0/24No ROA covers it. Add a ROA for AS55016, maxLength 24.668 of 673
Route object: RIR44.31.26.0/24Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
ROA: none44.184.136.0/24No ROA covers it. Add a ROA for AS55016, maxLength 24.668 of 673
Route object: RIR44.184.136.0/24Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
ROA: none44.184.137.0/24No ROA covers it. Add a ROA for AS55016, maxLength 24.668 of 673
Route object: RIR44.184.137.0/24Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
ROA: none44.184.138.0/24No ROA covers it. Add a ROA for AS55016, maxLength 24.668 of 673
Route object: RIR44.184.138.0/24Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
ROA: none44.184.139.0/24No ROA covers it. Add a ROA for AS55016, maxLength 24.668 of 673
Route object: RIR44.184.139.0/24Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
ROA: none208.44.192.0/24No ROA covers it. Add a ROA for AS55016, maxLength 24.668 of 673

Route objects not announced

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

44.184.136.0/22ALTDBNo ROA
64.132.240.0/24ALTDBNo ROA
162.208.88.0/22ALTDB, ARINNo ROA
2602:fe1a::/36ALTDB, ARINValid

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.