bgpreport

Network · data from 2026-11-12

AS27877 Cooperativa Telefónica de Capitán Bermúdez

Registry name: AS27877 - Coop. Telefonica de Capitan Bermudez, AR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS27877, 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.
190.123.96.0/21 Valid Nonecovered by 190.123.96.0/20 669 99% 67
190.123.104.0/21 Valid Nonecovered by 190.123.96.0/20 669 99% 67
190.123.112.0/21 Valid RIR databaseLACNIC 671 100% 67
200.110.160.0/21 Valid RIR databaseLACNIC 671 100% 66
190.123.96.0/20 Valid RIR databaseLACNIC 668 99% 67
2803:5000::/32 Valid RIR databaseLACNIC 321 50% 64

AS-SET

AS27877'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 2 are in fix.csv.

  • Route object: none2
ChangePrefix or setDetailFull-table peers
Route object: none190.123.96.0/21No route object for it. A route object for 190.123.96.0/20 with origin AS27877 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27877 in the RIR database for the space.669 of 673
Route object: none190.123.104.0/21No route object for it. A route object for 190.123.96.0/20 with origin AS27877 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27877 in the RIR database for the space.669 of 673

Route objects not announced

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