bgpreport

Network · data from 2026-11-12

AS271580 AS271580 - R.P.A Telecom

Registry name: AS271580 - R.P.A Telecom, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271580, 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.
179.63.60.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
2804:7dc0::/32 Valid Other IRR onlyRADB, TC 633 100% 68
2804:7dc0::/33 Valid Other IRR onlyTC 633 100% 67
2804:7dc0::/34 Valid Other IRR onlyTC 633 100% 67
2804:7dc0:4000::/34 Valid Other IRR onlyTC 633 100% 67
2804:7dc0:8000::/33 Valid Other IRR onlyTC 633 100% 67
2804:7dc0:8000::/34 Valid Other IRR onlyTC 633 100% 67
2804:7dc0:c000::/34 Valid Other IRR onlyTC 633 100% 67
179.63.60.0/24 Valid Other IRR onlyRADB, TC 327 49% 63
179.63.61.0/24 Valid Other IRR onlyRADB, TC 327 49% 63
179.63.62.0/24 Valid Other IRR onlyRADB, TC 327 49% 63
179.63.63.0/24 Valid Other IRR onlyRADB, TC 327 49% 63
179.63.60.0/23 Valid Other IRR onlyRADB, TC 33 5%low visibility 12
179.63.62.0/23 Valid Other IRR onlyRADB, TC 33 5%low visibility 12

AS-SET

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

  • Route object: RIR14
ChangePrefix or setDetailFull-table peers
Route object: RIR179.63.60.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:7dc0::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:7dc0::/33Route object only in TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:7dc0::/34Route object only in TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:7dc0:4000::/34Route object only in TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:7dc0:8000::/33Route object only in TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:7dc0:8000::/34Route object only in TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:7dc0:c000::/34Route object only in TC. Add it in the RIR database for the space.633 of 636
Route object: RIR179.63.60.0/24Route object only in RADB, TC. Add it in the RIR database for the space.327 of 673
Route object: RIR179.63.61.0/24Route object only in RADB, TC. Add it in the RIR database for the space.327 of 673
Route object: RIR179.63.62.0/24Route object only in RADB, TC. Add it in the RIR database for the space.327 of 673
Route object: RIR179.63.63.0/24Route object only in RADB, TC. Add it in the RIR database for the space.327 of 673
Route object: RIR179.63.60.0/23Route object only in RADB, TC. Add it in the RIR database for the space.33 of 673
Route object: RIR179.63.62.0/23Route object only in RADB, TC. Add it in the RIR database for the space.33 of 673

Route objects not announced

Every route object with origin AS271580 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.