bgpreport

Network · data from 2026-11-12

AS54976 CONVO-ASH - Convo

Registry name: CONVO-ASH - Convo, US · not in PeeringDB

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

Announced routes

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

70.33.169.0/24 No ROA Other origin only 672 100% 67
2620:12:2001::/48 No ROA None 1 0%low visibility 1
8.34.145.0/24 No ROA Other IRR onlyALTDB, BBOI 672 100% 66

AS-SET

AS54976 isn't in PeeringDB, where networks name their AS-SET.

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

  • ROA: none3
  • Route object: none2
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none70.33.169.0/24No ROA covers it. Add a ROA for AS54976, maxLength 24.672 of 673
Route object: none70.33.169.0/24Route objects for it name AS33597. Add a route object with origin AS54976 in the RIR database for the space.672 of 673
ROA: none2620:12:2001::/48No ROA covers it. Add a ROA for AS54976, maxLength 48.1 of 636
Route object: none2620:12:2001::/48No route object for it. Add a route object with origin AS54976 in the RIR database for the space.1 of 636
ROA: none8.34.145.0/24No ROA covers it. Add a ROA for AS54976, maxLength 24.672 of 673
Route object: RIR8.34.145.0/24Route object only in ALTDB, BBOI. Add it in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS54976 is announced.

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.