bgpreport

Network · data from 2026-11-12

AS49113 CABLOTEL Cablotel S.A.

Registry name: CABLOTEL Cablotel S.A., CH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS49113, 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.
193.111.202.0/23 No ROA RIR databaseRIPE 673 100% 67
77.234.56.0/21 Valid RIR databaseRIPE 673 100% 67
91.201.148.0/22 Valid RIR databaseRIPE 673 100% 67
185.97.136.0/22 Valid RIR databaseRIPE 673 100% 67
2a00:cd40::/32 Valid RIR databaseRIPE 636 100% 69

AS-SET

AS49113 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 1 are in fix.csv.

  • ROA: none1
ChangePrefix or setDetailFull-table peers
ROA: none193.111.202.0/23No ROA covers it. Add a ROA for AS49113, maxLength 23.673 of 673

Route objects not announced

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