bgpreport

Network · data from 2026-11-12

AS273672 AS273672 - Rocket Internet

Registry name: AS273672 - Rocket Internet, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273672, 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.
38.43.82.0/23 Invalid: origin None 17 3%low visibility 9
2804:8a7c::/32 No ROA Other IRR onlyRADB 634 100% 67

AS-SET

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

  • ROA: origin1
  • ROA: none1
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced30
ChangePrefix or setDetailFull-table peers
ROA: origin38.43.82.0/23An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS273672 should announce it, add a ROA for AS273672.17 of 673
Route object: none38.43.82.0/23No route object for it. Add a route object with origin AS273672 in the RIR database for the space.17 of 673
ROA: none2804:8a7c::/32No ROA covers it. Add a ROA for AS273672, maxLength 32.634 of 636
Route object: RIR2804:8a7c::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

2804:8a7c::/33RADBNo ROA
2804:8a7c::/34RADBNo ROA
2804:8a7c::/35RADBNo ROA
2804:8a7c::/36RADBNo ROA
2804:8a7c:1000::/36RADBNo ROA
2804:8a7c:2000::/35RADBNo ROA
2804:8a7c:2000::/36RADBNo ROA
2804:8a7c:3000::/36RADBNo ROA
2804:8a7c:4000::/34RADBNo ROA
2804:8a7c:4000::/35RADBNo ROA
2804:8a7c:4000::/36RADBNo ROA
2804:8a7c:5000::/36RADBNo ROA
2804:8a7c:6000::/35RADBNo ROA
2804:8a7c:6000::/36RADBNo ROA
2804:8a7c:7000::/36RADBNo ROA
2804:8a7c:8000::/33RADBNo ROA
2804:8a7c:8000::/34RADBNo ROA
2804:8a7c:8000::/35RADBNo ROA
2804:8a7c:8000::/36RADBNo ROA
2804:8a7c:9000::/36RADBNo ROA
2804:8a7c:a000::/35RADBNo ROA
2804:8a7c:a000::/36RADBNo ROA
2804:8a7c:b000::/36RADBNo ROA
2804:8a7c:c000::/34RADBNo ROA
2804:8a7c:c000::/35RADBNo ROA
2804:8a7c:c000::/36RADBNo ROA
2804:8a7c:d000::/36RADBNo ROA
2804:8a7c:e000::/35RADBNo ROA
2804:8a7c:e000::/36RADBNo ROA
2804:8a7c:f000::/36RADBNo ROA

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.