bgpreport

Network · data from 2026-11-12

AS264521 SLIM NET TELECOM

Registry name: AS264521 - SLIM NET TELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264521, 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.
132.255.212.0/22 No ROA Other IRR onlyALTDB, RADB, TC 671 100% 66
132.255.212.0/23 No ROA Other IRR onlyALTDB, RADB 671 100% 66
132.255.214.0/24 No ROA Other IRR onlyALTDB, RADB 668 99% 67
132.255.215.0/24 No ROA Other IRR onlyALTDB, RADB 668 99% 67
2804:20ec::/32 No ROA Other IRR onlyALTDB, RADB, TC 634 100% 67
2804:20ec::/34 No ROA Other IRR onlyRADB 634 100% 67
2804:20ec:4000::/34 No ROA Other IRR onlyRADB 634 100% 67
2804:20ec:8000::/34 No ROA Other IRR onlyRADB 634 100% 67

AS-SET

AS264521's PeeringDB record names no 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 20 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none132.255.212.0/22No ROA covers it. Add a ROA for AS264521, maxLength 22.671 of 673
Route object: RIR132.255.212.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none132.255.212.0/23No ROA covers it. Add a ROA for AS264521, maxLength 23.671 of 673
Route object: RIR132.255.212.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none132.255.214.0/24No ROA covers it. Add a ROA for AS264521, maxLength 24.668 of 673
Route object: RIR132.255.214.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.668 of 673
ROA: none132.255.215.0/24No ROA covers it. Add a ROA for AS264521, maxLength 24.668 of 673
Route object: RIR132.255.215.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.668 of 673
ROA: none2804:20ec::/32No ROA covers it. Add a ROA for AS264521, maxLength 32.634 of 636
Route object: RIR2804:20ec::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.634 of 636
ROA: none2804:20ec::/34No ROA covers it. Add a ROA for AS264521, maxLength 34.634 of 636
Route object: RIR2804:20ec::/34Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:20ec:4000::/34No ROA covers it. Add a ROA for AS264521, maxLength 34.634 of 636
Route object: RIR2804:20ec:4000::/34Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:20ec:8000::/34No ROA covers it. Add a ROA for AS264521, maxLength 34.634 of 636
Route object: RIR2804:20ec:8000::/34Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

132.255.212.0/24RADBNo ROA
132.255.213.0/24RADBNo ROA
132.255.214.0/23ALTDB, RADBNo ROA
2804:20ec:c000::/34RADBNo 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.