bgpreport

Network · data from 2026-11-12

AS34666 GLB1-AS JSC "Global Erty"

Registry name: GLB1-AS JSC "Global Erty", GE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS34666, 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.
81.16.240.0/20 No ROA RIR databaseRIPE 673 100% 67
38.188.57.0/24 Valid Nonecovered by 38.188.56.0/23 671 100% 67
38.188.56.0/24 Valid Nonecovered by 38.188.56.0/23 2 0%low visibility 2
38.188.56.0/23 Valid RIR databaseARIN 672 100% 67
81.16.240.0/24 Valid RIR databaseRIPE 672 100% 67
81.16.248.0/24 Valid RIR databaseRIPE 672 100% 66
81.16.253.0/24 Valid RIR databaseRIPE 672 100% 67
81.16.241.0/24 Valid RIR databaseRIPE 671 100% 66
81.16.242.0/24 Valid RIR databaseRIPE 671 100% 66
81.16.243.0/24 Valid RIR databaseRIPE 671 100% 66
81.16.244.0/24 Valid RIR databaseRIPE 671 100% 67
81.16.245.0/24 Valid RIR databaseRIPE 671 100% 67
81.16.246.0/24 Valid RIR databaseRIPE 671 100% 66
81.16.247.0/24 Valid RIR databaseRIPE 671 100% 66
81.16.249.0/24 Valid RIR databaseRIPE 671 100% 67
81.16.250.0/24 Valid RIR databaseRIPE 671 100% 67
81.16.251.0/24 Valid RIR databaseRIPE 671 100% 67
81.16.252.0/24 Valid RIR databaseRIPE 671 100% 67
81.16.254.0/24 Valid RIR databaseRIPE 671 100% 67
81.16.255.0/24 Valid RIR databaseRIPE 671 100% 66

AS-SET

AS34666 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 3 are in fix.csv.

  • ROA: none1
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: none81.16.240.0/20No ROA covers it. Add a ROA for AS34666, maxLength 20.673 of 673
Route object: none38.188.57.0/24No route object for it. A route object for 38.188.56.0/23 with origin AS34666 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34666 in the RIR database for the space.671 of 673
Route object: none38.188.56.0/24No route object for it. A route object for 38.188.56.0/23 with origin AS34666 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34666 in the RIR database for the space.2 of 673

Route objects not announced

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