Skip to main content

AS36868

ORG-EISL3-AFRINIC

Rogers Capital Technology Services Ltd

Registry

Authoritative registration data

AS number
36868
Name
ORG-EISL3-AFRINIC
Organisation
Rogers Capital Technology Services Ltd
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

46

IPv6 prefixes

1

Total announced

47

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS36868
196.46.32.0/21 IPv4 /21 not checked
196.46.40.0/21 IPv4 /21 not checked
196.46.48.0/21 IPv4 /21 not checked
41.207.144.0/21 IPv4 /21 not checked
41.207.152.0/21 IPv4 /21 not checked
41.211.80.0/21 IPv4 /21 not checked
41.211.88.0/21 IPv4 /21 not checked
196.22.144.0/22 IPv4 /22 not checked
196.22.152.0/22 IPv4 /22 not checked
196.22.156.0/22 IPv4 /22 not checked
196.46.60.0/22 IPv4 /22 not checked
196.22.148.0/24 IPv4 /24 not checked
196.22.149.0/24 IPv4 /24 not checked
196.22.150.0/24 IPv4 /24 not checked
196.22.151.0/24 IPv4 /24 not checked
196.22.154.0/24 IPv4 /24 not checked
196.22.156.0/24 IPv4 /24 not checked
196.46.32.0/24 IPv4 /24 not checked
196.46.36.0/24 IPv4 /24 not checked
196.46.43.0/24 IPv4 /24 not checked
196.46.44.0/24 IPv4 /24 not checked
196.46.47.0/24 IPv4 /24 not checked
196.46.56.0/24 IPv4 /24 not checked
196.46.57.0/24 IPv4 /24 not checked
196.46.59.0/24 IPv4 /24 not checked
196.46.60.0/24 IPv4 /24 not checked
196.46.61.0/24 IPv4 /24 not checked
196.46.62.0/24 IPv4 /24 not checked
196.46.63.0/24 IPv4 /24 not checked
41.207.128.0/24 IPv4 /24 not checked
41.207.129.0/24 IPv4 /24 not checked
41.207.130.0/24 IPv4 /24 not checked
41.207.131.0/24 IPv4 /24 not checked
41.207.132.0/24 IPv4 /24 not checked
41.207.133.0/24 IPv4 /24 not checked
41.207.134.0/24 IPv4 /24 not checked
41.207.135.0/24 IPv4 /24 not checked
41.207.138.0/24 IPv4 /24 not checked
41.207.144.0/24 IPv4 /24 not checked
41.211.64.0/24 IPv4 /24 not checked
41.211.67.0/24 IPv4 /24 not checked
41.211.72.0/24 IPv4 /24 not checked
41.211.73.0/24 IPv4 /24 not checked
41.211.74.0/24 IPv4 /24 not checked
41.211.94.0/24 IPv4 /24 not checked
41.211.95.0/24 IPv4 /24 not checked
2c0f:fe68::/32 IPv6 /32 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS36868
Address families
CINX: CINX Peering 1,000 Mbps IPv4 · IPv6
JINX: JINX Peering 10,000 Mbps IPv4 · IPv6
LINX LON1: Main 1,000 Mbps IPv4 · IPv6
MIXP: Peering 10,000 Mbps IPv4 · IPv6
NAPAfrica IX Cape Town 10,000 Mbps IPv4 · IPv6
NAPAfrica IX Johannesburg: Peering 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS36868 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS36868 in AS paths

Observed upstreams
Families
AS37100 ORG-SL75-AFRINIC 1,130 7,223
v4 v6
AS6939 HURRICANE 968 4,790
v4 v6
AS1299 TWELVE99 448 2,398
v4
AS30844 LIQUID-AS 245 328
v4
AS23889 ORG-mA21-AFRINIC 29 36
v4
AS3741 ORG-DD1-AFRINIC 3 33
v4
AS9583 SIFY-AS-IN 16 18
v4
AS37468 ORG-AC4-AFRINIC 2 2
v4 v6
AS39120 CONVERGENZE-AS 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

5 networks seen after AS36868 in AS paths

Observed downstreams
Families
AS37708 ORG-AFNC1-AFRINIC 121 405
v4 v6
AS37722 ORG-KL3-AFRINIC 160 383
v4
AS327821 ORG-MIXP1-AFRINIC 250 319
v4
AS25818 ORG-cA1-AFRINIC 215 263
v4
AS64518 5 7
v4

No rows match “”.

Showing – of

Uncertain adjacencies

21 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.