bgpreport

Network · data from 2026-11-12

AS272655 AS272655 - TopNet Telecom

Registry name: AS272655 - TopNet Telecom, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272655, 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.
2804:869c::/40 No ROA Nonecovered by 2804:869c::/36 636 100% 67
2804:869c:200::/40 No ROA Nonecovered by 2804:869c::/36 1 0%low visibility 1
2804:869c::/32 No ROA Other IRR onlyRADB 633 100% 67
2804:869c:9000::/36 No ROA Other IRR onlyRADB 629 99% 67
2804:869c:a000::/36 No ROA Other IRR onlyRADB 629 99% 67

AS-SET

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

  • ROA: none5
  • Route object: none2
  • Route object: RIR3
  • Route object: not announced28
ChangePrefix or setDetailFull-table peers
ROA: none2804:869c::/40No ROA covers it. Add a ROA for AS272655, maxLength 40.636 of 636
Route object: none2804:869c::/40No route object for it. A route object for 2804:869c::/36 with origin AS272655 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272655 in the RIR database for the space.636 of 636
ROA: none2804:869c:200::/40No ROA covers it. Add a ROA for AS272655, maxLength 40.1 of 636
Route object: none2804:869c:200::/40No route object for it. A route object for 2804:869c::/36 with origin AS272655 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272655 in the RIR database for the space.1 of 636
ROA: none2804:869c::/32No ROA covers it. Add a ROA for AS272655, maxLength 32.633 of 636
Route object: RIR2804:869c::/32Route object only in RADB. Add it in the RIR database for the space.633 of 636
ROA: none2804:869c:9000::/36No ROA covers it. Add a ROA for AS272655, maxLength 36.629 of 636
Route object: RIR2804:869c:9000::/36Route object only in RADB. Add it in the RIR database for the space.629 of 636
ROA: none2804:869c:a000::/36No ROA covers it. Add a ROA for AS272655, maxLength 36.629 of 636
Route object: RIR2804:869c:a000::/36Route object only in RADB. Add it in the RIR database for the space.629 of 636

Route objects not announced

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

2804:869c::/33RADBNo ROA
2804:869c::/34RADBNo ROA
2804:869c::/35RADBNo ROA
2804:869c::/36RADBNo ROA
2804:869c:1000::/36RADBNo ROA
2804:869c:2000::/35RADBNo ROA
2804:869c:2000::/36RADBNo ROA
2804:869c:3000::/36RADBNo ROA
2804:869c:4000::/34RADBNo ROA
2804:869c:4000::/35RADBNo ROA
2804:869c:4000::/36RADBNo ROA
2804:869c:5000::/36RADBNo ROA
2804:869c:6000::/35RADBNo ROA
2804:869c:6000::/36RADBNo ROA
2804:869c:7000::/36RADBNo ROA
2804:869c:8000::/33RADBNo ROA
2804:869c:8000::/34RADBNo ROA
2804:869c:8000::/35RADBNo ROA
2804:869c:8000::/36RADBNo ROA
2804:869c:a000::/35RADBNo ROA
2804:869c:b000::/36RADBNo ROA
2804:869c:c000::/34RADBNo ROA
2804:869c:c000::/35RADBNo ROA
2804:869c:c000::/36RADBNo ROA
2804:869c:d000::/36RADBNo ROA
2804:869c:e000::/35RADBNo ROA
2804:869c:e000::/36RADBNo ROA
2804:869c: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.