bgpreport

Network · data from 2026-11-12

AS27950 AS27950 - Cooperativa Telefonica Benavidez Ltda

Registry name: AS27950 - Cooperativa Telefonica Benavidez Ltda, AR · not in PeeringDB

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

Announced routes

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

200.49.116.0/24 Valid Nonecovered by 200.49.112.0/21 672 100% 67
200.49.117.0/24 Valid Nonecovered by 200.49.112.0/21 672 100% 67
200.49.118.0/24 Valid Nonecovered by 200.49.112.0/21 672 100% 67
200.49.119.0/24 Valid Nonecovered by 200.49.112.0/21 672 100% 67
200.49.112.0/24 Valid Other IRR onlyRADB 672 100% 67
200.49.113.0/24 Valid Other IRR onlyRADB 672 100% 67
200.49.114.0/24 Valid Other IRR onlyRADB 672 100% 67
200.49.115.0/24 Valid Other IRR onlyRADB 672 100% 67
200.49.112.0/21 Valid RIR databaseLACNIC, RADB 100 15% 37

AS-SET

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

  • Route object: none4
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
Route object: none200.49.116.0/24No route object for it. A route object for 200.49.112.0/21 with origin AS27950 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27950 in the RIR database for the space.672 of 673
Route object: none200.49.117.0/24No route object for it. A route object for 200.49.112.0/21 with origin AS27950 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27950 in the RIR database for the space.672 of 673
Route object: none200.49.118.0/24No route object for it. A route object for 200.49.112.0/21 with origin AS27950 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27950 in the RIR database for the space.672 of 673
Route object: none200.49.119.0/24No route object for it. A route object for 200.49.112.0/21 with origin AS27950 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27950 in the RIR database for the space.672 of 673
Route object: RIR200.49.112.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR200.49.113.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR200.49.114.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR200.49.115.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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