bgpreport

Network · data from 2026-11-12

AS37013 Satcom Networks Africa

Registry name: Satcom Networks Africa - Satcom Networks Africa, TZ · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS37013, 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.
41.223.228.0/24 No ROA Nonecovered by 41.223.228.0/23 673 100% 66
41.223.231.0/24 No ROA Nonecovered by 41.223.230.0/23 673 100% 67
41.223.230.0/24 No ROA Nonecovered by 41.223.230.0/23 672 100% 66
2c0f:fd10::/32 No ROA Other IRR onlyRADB, RIPE-NONAUTH 636 100% 67
41.223.228.0/22 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 670 100% 67

AS-SET

AS37013'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 11 are in fix.csv.

  • ROA: none5
  • Route object: none3
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none41.223.228.0/24No ROA covers it. Add a ROA for AS37013, maxLength 24.673 of 673
Route object: none41.223.228.0/24No route object for it. A route object for 41.223.228.0/23 with origin AS37013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37013 in the RIR database for the space.673 of 673
ROA: none41.223.231.0/24No ROA covers it. Add a ROA for AS37013, maxLength 24.673 of 673
Route object: none41.223.231.0/24No route object for it. A route object for 41.223.230.0/23 with origin AS37013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37013 in the RIR database for the space.673 of 673
ROA: none41.223.230.0/24No ROA covers it. Add a ROA for AS37013, maxLength 24.672 of 673
Route object: none41.223.230.0/24No route object for it. A route object for 41.223.230.0/23 with origin AS37013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37013 in the RIR database for the space.672 of 673
ROA: none2c0f:fd10::/32No ROA covers it. Add a ROA for AS37013, maxLength 32.636 of 636
Route object: RIR2c0f:fd10::/32Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.636 of 636
ROA: none41.223.228.0/22No ROA covers it. Add a ROA for AS37013, maxLength 22.670 of 673

Route objects not announced

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

41.223.228.0/23RADBNo ROA
41.223.230.0/23RADBNo 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.