bgpreport

Network · data from 2026-11-12

AS271936 SERVICIOS DE TELECOMUNICACIONES ATVCABLE

Registry name: AS271936 - SERVICIOS DE TELECOMUNICACIONES ATVCABLE CIA. LTDA., EC · PeeringDB

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

Announced routes

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

2803:fa10:e000::/48 Valid Nonecovered by 2803:fa10::/32 633 100% 67
157.100.204.0/24 Valid Other IRR onlyRADB 670 100% 67
45.225.91.0/24 Valid Other IRR onlyRADB 665 99% 67
181.188.237.0/24 Valid RIR databaseLACNIC, RADB 672 100% 67
66.231.68.0/24 Valid RIR databaseLACNIC, RADB 668 99% 67
2803:fa10::/32 Valid RIR databaseLACNIC 635 100% 67

AS-SET

AS271936'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 3 are in fix.csv.

  • Route object: none1
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none2803:fa10:e000::/48No route object for it. A route object for 2803:fa10::/32 with origin AS271936 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271936 in the RIR database for the space.633 of 636
Route object: RIR157.100.204.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR45.225.91.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673

Route objects not announced

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