bgpreport

Network · data from 2026-11-12

AS274123 AS274123 - GLOBAL INVERNET SRL

Registry name: AS274123 - GLOBAL INVERNET SRL, DO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274123, 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.147.138.0/24 No ROA None 671 100% 67
154.13.67.0/24 No ROA Other IRR onlyRADB 673 100% 67
2803:7ed0::/48 Valid Nonecovered by 2803:7ed0::/32 636 100% 67
2803:7ed0:1::/48 Valid Nonecovered by 2803:7ed0::/32 635 100% 67
2803:7ed0:2::/48 Valid Nonecovered by 2803:7ed0::/32 635 100% 67
2803:7ed0:3::/48 Valid Nonecovered by 2803:7ed0::/32 635 100% 67
38.135.85.0/24 Valid RIR databaseARIN 671 100% 67
38.147.131.0/24 Valid RIR databaseARIN 671 100% 67

AS-SET

AS274123 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 9 are in fix.csv.

  • ROA: none2
  • Route object: none5
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none38.147.138.0/24No ROA covers it. Add a ROA for AS274123, maxLength 24.671 of 673
Route object: none38.147.138.0/24No route object for it. Add a route object with origin AS274123 in the RIR database for the space.671 of 673
ROA: none154.13.67.0/24No ROA covers it. Add a ROA for AS274123, maxLength 24.673 of 673
Route object: RIR154.13.67.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: none2803:7ed0::/48No route object for it. A route object for 2803:7ed0::/32 with origin AS274123 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274123 in the RIR database for the space.636 of 636
Route object: none2803:7ed0:1::/48No route object for it. A route object for 2803:7ed0::/32 with origin AS274123 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274123 in the RIR database for the space.635 of 636
Route object: none2803:7ed0:2::/48No route object for it. A route object for 2803:7ed0::/32 with origin AS274123 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274123 in the RIR database for the space.635 of 636
Route object: none2803:7ed0:3::/48No route object for it. A route object for 2803:7ed0::/32 with origin AS274123 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274123 in the RIR database for the space.635 of 636

Route objects not announced

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

2803:7ed0::/32LACNICValid

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.