bgpreport

Network · data from 2026-11-12

AS274048 VARGAS JAMPOL TELECOMUNICACIONES SRL

Registry name: AS274048 - VARGAS JAMPOL TELECOMUNICACIONES SRL, DO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274048, 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.
38.246.144.0/23 No ROA Nonecovered by 38.246.144.0/22 673 100% 67
38.246.146.0/23 No ROA Nonecovered by 38.246.144.0/22 668 99% 67
38.246.144.0/22 No ROA Other IRR onlyRADB 670 100% 67
2803:22d0::/34 Valid Nonecovered by 2803:22d0::/32 633 100% 67
2803:22d0:4000::/34 Valid Nonecovered by 2803:22d0::/32 633 100% 67
45.196.56.0/22 Valid RIR databaseAFRINIC, RADB 672 100% 67
45.196.56.0/21 Valid RIR databaseAFRINIC, RADB 669 99% 67
45.196.60.0/22 Valid RIR databaseAFRINIC, RADB 667 99% 67
2803:22d0::/32 Valid RIR databaseLACNIC 633 100% 67

AS-SET

AS274048'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 16 are in fix.csv.

  • ROA: none3
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none38.246.144.0/23No ROA covers it. Add a ROA for AS274048, maxLength 23.673 of 673
Route object: none38.246.144.0/23No route object for it. A route object for 38.246.144.0/22 with origin AS274048 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274048 in the RIR database for the space.673 of 673
ROA: none38.246.146.0/23No ROA covers it. Add a ROA for AS274048, maxLength 23.668 of 673
Route object: none38.246.146.0/23No route object for it. A route object for 38.246.144.0/22 with origin AS274048 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274048 in the RIR database for the space.668 of 673
ROA: none38.246.144.0/22No ROA covers it. Add a ROA for AS274048, maxLength 22.670 of 673
Route object: RIR38.246.144.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: none2803:22d0::/34No route object for it. A route object for 2803:22d0::/32 with origin AS274048 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274048 in the RIR database for the space.633 of 636
Route object: none2803:22d0:4000::/34No route object for it. A route object for 2803:22d0::/32 with origin AS274048 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274048 in the RIR database for the space.633 of 636

Route objects not announced

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

45.196.56.0/24AFRINIC, RADBValid
45.196.57.0/24AFRINIC, RADBValid
45.196.58.0/24AFRINIC, RADBValid
45.196.59.0/24AFRINIC, RADBValid
45.196.60.0/24AFRINIC, RADBValid
45.196.61.0/24AFRINIC, RADBValid
45.196.62.0/24AFRINIC, RADBValid
45.196.63.0/24AFRINIC, RADBValid

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.