bgpreport

Network · data from 2026-11-12

AS57324 GCCIT

Registry name: GCCIT Al Lawn Al Akhdar International Company for Communications and Information Technology Ltd., IQ · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS57324, 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.
202.164.196.0/24 No ROA RIR databaseRIPE 671 100% 67
2a03:c341::/32 No ROA RIR databaseRIPE 635 100% 69
2a03:c343::/32 No ROA RIR databaseRIPE 635 100% 67
93.187.32.0/24 Valid Other origin only 672 100% 67
93.187.33.0/24 Valid Other origin only 672 100% 67
93.187.36.0/24 Valid Other origin only 672 100% 68
122.102.117.0/24 Valid None 672 100% 67
93.187.35.0/24 Valid Other origin only 670 100% 67
93.187.37.0/24 Valid Other origin only 670 100% 67
93.187.39.0/24 Valid Other origin only 670 100% 68
185.52.118.0/24 Valid Other origin only 665 99% 67
93.187.34.0/24 Valid Other origin only 2 0%low visibility 2
93.187.38.0/24 Valid Other origin only 2 0%low visibility 2
185.52.119.0/24 Valid RIR databaseRIPE 673 100% 67
202.164.194.0/24 Valid RIR databaseRIPE 673 100% 68
202.164.195.0/24 Valid RIR databaseRIPE 673 100% 68
202.164.202.0/24 Valid RIR databaseRIPE 673 100% 66
79.132.197.0/24 Valid RIR databaseRIPE 672 100% 66
86.111.144.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
86.111.146.0/24 Valid RIR databaseRIPE 672 100% 66
109.230.114.0/24 Valid RIR databaseRIPE 672 100% 66
109.230.115.0/24 Valid RIR databaseRIPE 672 100% 66
202.164.192.0/24 Valid RIR databaseRIPE 672 100% 67
202.164.193.0/24 Valid RIR databaseRIPE 672 100% 66
202.164.199.0/24 Valid RIR databaseRIPE 672 100% 66
202.164.203.0/24 Valid RIR databaseRIPE 672 100% 66
202.164.205.0/24 Valid RIR databaseRIPE 672 100% 66
79.132.199.0/24 Valid RIR databaseRIPE 671 100% 67
109.230.120.0/24 Valid RIR databaseRIPE 671 100% 68
185.113.105.0/24 Valid RIR databaseRIPE 671 100% 67
202.164.197.0/24 Valid RIR databaseRIPE 671 100% 67
202.164.198.0/24 Valid RIR databaseRIPE 671 100% 67
202.164.201.0/24 Valid RIR databaseRIPE 670 100% 67
79.132.196.0/24 Valid RIR databaseRIPE 669 99% 67
109.230.126.0/24 Valid RIR databaseRIPE 3 0%low visibility 3
202.164.200.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
2a03:c340::/32 Valid RIR databaseRIPE 0 0%low visibility 1

AS-SET

AS57324'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 21 are in fix.csv.

  • ROA: none3
  • Route object: none10
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none202.164.196.0/24No ROA covers it. Add a ROA for AS57324, maxLength 24.671 of 673
ROA: none2a03:c341::/32No ROA covers it. Add a ROA for AS57324, maxLength 32.635 of 636
ROA: none2a03:c343::/32No ROA covers it. Add a ROA for AS57324, maxLength 32.635 of 636
Route object: none93.187.32.0/24Route objects for it name AS56484. Add a route object with origin AS57324 in the RIR database for the space.672 of 673
Route object: none93.187.33.0/24Route objects for it name AS56484. Add a route object with origin AS57324 in the RIR database for the space.672 of 673
Route object: none93.187.36.0/24Route objects for it name AS56484. Add a route object with origin AS57324 in the RIR database for the space.672 of 673
Route object: none122.102.117.0/24No route object for it. Add a route object with origin AS57324 in the RIR database for the space.672 of 673
Route object: none93.187.35.0/24Route objects for it name AS56484. Add a route object with origin AS57324 in the RIR database for the space.670 of 673
Route object: none93.187.37.0/24Route objects for it name AS56484. Add a route object with origin AS57324 in the RIR database for the space.670 of 673
Route object: none93.187.39.0/24Route objects for it name AS56484. Add a route object with origin AS57324 in the RIR database for the space.670 of 673
Route object: none185.52.118.0/24Route objects for it name AS56484. Add a route object with origin AS57324 in the RIR database for the space.665 of 673
Route object: none93.187.34.0/24Route objects for it name AS56484. Add a route object with origin AS57324 in the RIR database for the space.2 of 673
Route object: none93.187.38.0/24Route objects for it name AS56484. Add a route object with origin AS57324 in the RIR database for the space.2 of 673

Route objects not announced

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

86.111.145.0/24RADB, RIPEValid
86.111.147.0/24RADB, RIPEValid
86.111.148.0/24RADBNo ROA
86.111.149.0/24RADBNo ROA
109.230.112.0/24RIPEValid
109.230.123.0/24RIPEValid
202.164.204.0/24RIPEValid
2a03:c342::/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.