bgpreport

Network · data from 2026-11-12

AS208800 G42 Cloud Technology

Registry name: eoscloud G42 CLOUD TECHNOLOGY L.L.C., AE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS208800, 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.
77.242.252.0/24 Invalid: origin Other origin only 2 0%low visibility 2
77.242.254.0/23 Invalid: origin Other origin only 2 0%low visibility 2
91.201.4.0/22 Valid RIR databaseNTTCOM, RADB, RIPE 673 100% 66
91.201.4.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 673 100% 70
91.201.5.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 673 100% 70
91.201.6.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 673 100% 70
91.201.7.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 673 100% 70
77.242.241.0/24 Valid RIR databaseRIPE 671 100% 66
77.242.242.0/24 Valid RIR databaseRIPE 671 100% 66
77.242.243.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
77.242.247.0/24 Valid RIR databaseRIPE 671 100% 66
77.242.248.0/24 Valid RIR databaseRIPE 671 100% 66
77.242.249.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
77.242.250.0/24 Valid RIR databaseRIPE 671 100% 66
77.242.251.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
188.116.28.0/22 Valid RIR databaseNTTCOM, RADB, RIPE 671 100% 66
77.242.240.0/24 Valid RIR databaseRIPE 670 100% 66
2a0e:6e80::/44 Valid RIR databaseRADB, RIPE 635 100% 68

AS-SET

AS208800'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 12 are in fix.csv.

  • ROA: origin2
  • Route object: none2
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: origin77.242.252.0/24ROAs covering it name AS218669, not AS208800. If AS208800 should announce it, add a ROA for AS208800.2 of 673
Route object: none77.242.252.0/24Route objects for it name AS218669. Add a route object with origin AS208800 in the RIR database for the space.2 of 673
ROA: origin77.242.254.0/23ROAs covering it name AS218669, not AS208800. If AS208800 should announce it, add a ROA for AS208800.2 of 673
Route object: none77.242.254.0/23Route objects for it name AS218669. Add a route object with origin AS208800 in the RIR database for the space.2 of 673

Route objects not announced

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

77.242.240.0/21RADBNo ROA
77.242.240.0/22RIPEValid
77.242.240.0/23RIPEValid
188.116.28.0/24RADB, RIPEValid
188.116.29.0/24RADB, RIPEValid
188.116.30.0/24RIPEValid
188.116.31.0/24RIPEValid
2a0e:6e80::/29RIPENo 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.