bgpreport

Network · data from 2026-11-12

AS272058 AS272058 - VIVO TELECOMUNICACIONES S.A.S.

Registry name: AS272058 - VIVO TELECOMUNICACIONES S.A.S., CO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272058, 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:310:a::/48 No ROA Nonecovered by 2803:310::/32 633 100% 67
2803:310:1000::/36 No ROA Nonecovered by 2803:310::/32 633 100% 67
2803:310:2000::/36 No ROA Nonecovered by 2803:310::/32 633 100% 67
2803:310:5000::/36 No ROA Nonecovered by 2803:310::/32 633 100% 67
2803:310:6000::/36 No ROA Nonecovered by 2803:310::/32 633 100% 67
2803:310:4000::/36 No ROA Nonecovered by 2803:310::/32 5 1%low visibility 6
38.252.90.0/24 Valid Other IRR onlyRADB 673 100% 67
38.252.91.0/24 Valid Other IRR onlyRADB 673 100% 67
38.252.92.0/24 Valid Other IRR onlyRADB 673 100% 67
38.252.93.0/24 Valid Other IRR onlyRADB 673 100% 67
38.252.94.0/24 Valid Other IRR onlyRADB 673 100% 67
38.252.95.0/24 Valid Other IRR onlyRADB 673 100% 67
38.252.88.0/24 Valid Other IRR onlyRADB 8 1%low visibility 8

AS-SET

AS272058 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 26 are in fix.csv.

  • ROA: none6
  • Route object: none6
  • Route object: RIR7
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none2803:310:a::/48No ROA covers it. Add a ROA for AS272058, maxLength 48.633 of 636
Route object: none2803:310:a::/48No route object for it. A route object for 2803:310::/32 with origin AS272058 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272058 in the RIR database for the space.633 of 636
ROA: none2803:310:1000::/36No ROA covers it. Add a ROA for AS272058, maxLength 36.633 of 636
Route object: none2803:310:1000::/36No route object for it. A route object for 2803:310::/32 with origin AS272058 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272058 in the RIR database for the space.633 of 636
ROA: none2803:310:2000::/36No ROA covers it. Add a ROA for AS272058, maxLength 36.633 of 636
Route object: none2803:310:2000::/36No route object for it. A route object for 2803:310::/32 with origin AS272058 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272058 in the RIR database for the space.633 of 636
ROA: none2803:310:5000::/36No ROA covers it. Add a ROA for AS272058, maxLength 36.633 of 636
Route object: none2803:310:5000::/36No route object for it. A route object for 2803:310::/32 with origin AS272058 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272058 in the RIR database for the space.633 of 636
ROA: none2803:310:6000::/36No ROA covers it. Add a ROA for AS272058, maxLength 36.633 of 636
Route object: none2803:310:6000::/36No route object for it. A route object for 2803:310::/32 with origin AS272058 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272058 in the RIR database for the space.633 of 636
ROA: none2803:310:4000::/36No ROA covers it. Add a ROA for AS272058, maxLength 36.5 of 636
Route object: none2803:310:4000::/36No route object for it. A route object for 2803:310::/32 with origin AS272058 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272058 in the RIR database for the space.5 of 636
Route object: RIR38.252.90.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR38.252.91.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR38.252.92.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR38.252.93.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR38.252.94.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR38.252.95.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR38.252.88.0/24Route object only in RADB. Add it in the RIR database for the space.8 of 673

Route objects not announced

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

38.252.88.0/21ARIN, RADBValid
38.252.88.0/22RADBValid
38.252.89.0/24RADBValid
38.252.90.0/23RADBValid
38.252.92.0/22RADBValid
38.252.94.0/23RADBValid
2803:310::/32RADBNo 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.