bgpreport

Network · data from 2026-11-12

AS25364 Egypt Cyber Center aka ECC Solutions - Egypt Cyber Center aka ECC Solutions

Registry name: Egypt Cyber Center aka ECC Solutions - Egypt Cyber Center aka ECC Solutions, EG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS25364, 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.29.96.0/24 No ROA Other IRR onlyRIPE-NONAUTH 672 100% 67
81.29.98.0/24 No ROA Other IRR onlyRIPE-NONAUTH 672 100% 67
81.29.100.0/24 No ROA Other IRR onlyRIPE-NONAUTH 672 100% 67
81.29.101.0/24 No ROA Other IRR onlyRIPE-NONAUTH 672 100% 67
81.29.102.0/24 No ROA Other IRR onlyRIPE-NONAUTH 672 100% 67
81.29.103.0/24 No ROA Other IRR onlyRIPE-NONAUTH 672 100% 67
81.29.104.0/24 No ROA Other IRR onlyRIPE-NONAUTH 672 100% 67
81.29.108.0/24 No ROA Other IRR onlyRIPE-NONAUTH 672 100% 67
81.29.109.0/24 No ROA Other IRR onlyRIPE-NONAUTH 672 100% 67
81.29.111.0/24 No ROA Other IRR onlyRIPE-NONAUTH 672 100% 67

AS-SET

AS25364 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 35 are in fix.csv.

  • ROA: none10
  • Route object: RIR10
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none81.29.96.0/24No ROA covers it. Add a ROA for AS25364, maxLength 24.672 of 673
Route object: RIR81.29.96.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.672 of 673
ROA: none81.29.98.0/24No ROA covers it. Add a ROA for AS25364, maxLength 24.672 of 673
Route object: RIR81.29.98.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.672 of 673
ROA: none81.29.100.0/24No ROA covers it. Add a ROA for AS25364, maxLength 24.672 of 673
Route object: RIR81.29.100.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.672 of 673
ROA: none81.29.101.0/24No ROA covers it. Add a ROA for AS25364, maxLength 24.672 of 673
Route object: RIR81.29.101.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.672 of 673
ROA: none81.29.102.0/24No ROA covers it. Add a ROA for AS25364, maxLength 24.672 of 673
Route object: RIR81.29.102.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.672 of 673
ROA: none81.29.103.0/24No ROA covers it. Add a ROA for AS25364, maxLength 24.672 of 673
Route object: RIR81.29.103.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.672 of 673
ROA: none81.29.104.0/24No ROA covers it. Add a ROA for AS25364, maxLength 24.672 of 673
Route object: RIR81.29.104.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.672 of 673
ROA: none81.29.108.0/24No ROA covers it. Add a ROA for AS25364, maxLength 24.672 of 673
Route object: RIR81.29.108.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.672 of 673
ROA: none81.29.109.0/24No ROA covers it. Add a ROA for AS25364, maxLength 24.672 of 673
Route object: RIR81.29.109.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.672 of 673
ROA: none81.29.111.0/24No ROA covers it. Add a ROA for AS25364, maxLength 24.672 of 673
Route object: RIR81.29.111.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

81.29.96.0/20RIPE-NONAUTHNo ROA
81.29.96.0/22RIPE-NONAUTHNo ROA
81.29.96.0/23RIPE-NONAUTHNo ROA
81.29.97.0/24RIPE-NONAUTHNo ROA
81.29.98.0/23RIPE-NONAUTHNo ROA
81.29.99.0/24RIPE-NONAUTHNo ROA
81.29.100.0/22RIPE-NONAUTHNo ROA
81.29.100.0/23RIPE-NONAUTHNo ROA
81.29.102.0/23RIPE-NONAUTHNo ROA
81.29.104.0/22RIPE-NONAUTHNo ROA
81.29.105.0/24RIPE-NONAUTHNo ROA
81.29.106.0/24RIPE-NONAUTHNo ROA
81.29.107.0/24RIPE-NONAUTHNo ROA
81.29.108.0/22RIPE-NONAUTHNo ROA
81.29.110.0/24RIPE-NONAUTHNo 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.