bgpreport

Network · data from 2026-11-12

AS36983 Osiris Trading (PTY) LTD - Osiris Trading (PTY) LTD

Registry name: Osiris Trading (PTY) LTD - Osiris Trading (PTY) LTD, ZA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS36983, 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.169.115.0/24 No ROA None 1 0%low visibility 1
193.169.206.0/23 No ROA RIR databaseRIPE 673 100% 67
193.169.206.0/24 No ROA RIR databaseBELL, RIPE 673 100% 66
193.169.207.0/24 No ROA RIR databaseBELL, RIPE 673 100% 66
41.222.108.0/22 Valid None 673 100% 67
41.222.108.0/24 Valid Other IRR onlyBELL, RIPE-NONAUTH 673 100% 66
41.222.110.0/24 Valid Other IRR onlyRIPE-NONAUTH 673 100% 66
41.222.104.0/23 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
41.222.104.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
41.222.106.0/24 Valid RIR databaseAFRINIC 673 100% 66
41.222.107.0/24 Valid RIR databaseAFRINIC 670 100% 68

AS-SET

AS36983 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 17 are in fix.csv.

  • ROA: none4
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none41.169.115.0/24No ROA covers it. Add a ROA for AS36983, maxLength 24.1 of 673
Route object: none41.169.115.0/24No route object for it. Add a route object with origin AS36983 in the RIR database for the space.1 of 673
ROA: none193.169.206.0/23No ROA covers it. Add a ROA for AS36983, maxLength 23.673 of 673
ROA: none193.169.206.0/24No ROA covers it. Add a ROA for AS36983, maxLength 24.673 of 673
ROA: none193.169.207.0/24No ROA covers it. Add a ROA for AS36983, maxLength 24.673 of 673
Route object: none41.222.108.0/22No route object for it. Add a route object with origin AS36983 in the RIR database for the space.673 of 673
Route object: RIR41.222.108.0/24Route object only in BELL, RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673
Route object: RIR41.222.110.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

41.222.104.0/22RIPE-NONAUTHValid
41.222.105.0/24AFRINICValid
41.222.109.0/24BELL, RIPE-NONAUTHValid
41.222.111.0/24AFRINICInvalid: maxLength
185.31.220.0/23RIPENo ROA
185.68.84.0/24RIPENo ROA
196.43.204.0/24NTTCOM, RADBNo ROA
196.43.208.0/24RADBNo ROA
196.44.224.0/20RIPE-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.