bgpreport

Network · data from 2026-11-12

AS208080 ge-te Tbilisi Energy LLC

Registry name: ge-te Tbilisi Energy LLC, GE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS208080, 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.

193.29.190.0/24 No ROA Other origin onlycovered by 193.29.190.0/23 673 100% 67
193.29.184.0/23 No ROA RIR databaseRIPE 673 100% 67
193.29.184.0/24 No ROA RIR databaseRIPE 673 100% 67
193.29.185.0/24 No ROA RIR databaseRIPE 673 100% 67
193.29.190.0/23 No ROA RIR databaseRIPE 673 100% 67
193.29.191.0/24 No ROA RIR databaseRIPE 673 100% 67

AS-SET

AS208080 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: none6
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none193.29.190.0/24No ROA covers it. Add a ROA for AS208080, maxLength 24.673 of 673
Route object: none193.29.190.0/24Route objects for it name AS11908. A route object for 193.29.190.0/23 with origin AS208080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208080 in the RIR database for the space.673 of 673
ROA: none193.29.184.0/23No ROA covers it. Add a ROA for AS208080, maxLength 23.673 of 673
ROA: none193.29.184.0/24No ROA covers it. Add a ROA for AS208080, maxLength 24.673 of 673
ROA: none193.29.185.0/24No ROA covers it. Add a ROA for AS208080, maxLength 24.673 of 673
ROA: none193.29.190.0/23No ROA covers it. Add a ROA for AS208080, maxLength 23.673 of 673
ROA: none193.29.191.0/24No ROA covers it. Add a ROA for AS208080, maxLength 24.673 of 673

Route objects not announced

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

193.29.185.0/32RIPENo ROA
193.29.190.0/32RIPENo 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.