bgpreport

Network · data from 2026-11-12

AS272875 AS272875 - COMUNICAMOS + TELECOMUNICACIONES SAS

Registry name: AS272875 - COMUNICAMOS + TELECOMUNICACIONES SAS, CO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272875, 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:4a90:8306::/48 No ROA None 1 0%low visibility 1
2803:4a90:2::/48 No ROA Other IRR onlyRADB 634 100% 68
2803:4a90:3::/48 No ROA Other IRR onlyRADB 634 100% 68
2803:4a90:4::/48 No ROA Other IRR onlyRADB 632 99% 68

AS-SET

AS272875 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 11 are in fix.csv.

  • ROA: none4
  • Route object: none1
  • Route object: RIR3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2803:4a90:8306::/48No ROA covers it. Add a ROA for AS272875, maxLength 48.1 of 636
Route object: none2803:4a90:8306::/48No route object for it. Add a route object with origin AS272875 in the RIR database for the space.1 of 636
ROA: none2803:4a90:2::/48No ROA covers it. Add a ROA for AS272875, maxLength 48.634 of 636
Route object: RIR2803:4a90:2::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2803:4a90:3::/48No ROA covers it. Add a ROA for AS272875, maxLength 48.634 of 636
Route object: RIR2803:4a90:3::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2803:4a90:4::/48No ROA covers it. Add a ROA for AS272875, maxLength 48.632 of 636
Route object: RIR2803:4a90:4::/48Route object only in RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

Route objects with origin AS272875 whose prefix no peer sees AS272875 announce. Many are kept on purpose (backup routes, space announced only in some places).

2803:4a90::/48RADBNo ROA
2803:4a90:1::/48RADBNo ROA
2803:4a90:5::/48RADBNo ROA

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.