Skip to main content

AS37525

ORG-BSIL1-AFRINIC

Altron TMT (Pty) Ltd

Registry

Authoritative registration data

AS number
37525
Name
ORG-BSIL1-AFRINIC
Organisation
Altron TMT (Pty) Ltd
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

1

Total announced

7

Announced prefixes

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

Prefixes announced by AS37525
197.156.0.0/18 IPv4 /18 not checked
41.85.128.0/19 IPv4 /19 not checked
41.87.224.0/19 IPv4 /19 not checked
105.235.160.0/20 IPv4 /20 not checked
41.76.56.0/21 IPv4 /21 not checked
41.85.134.0/24 IPv4 /24 not checked
2c0f:fda0::/32 IPv6 /32 RPKI not found

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 AS37525
Address families
NAPAfrica IX Cape Town 1,000 Mbps IPv4 · IPv6
NAPAfrica IX Johannesburg: Peering 2,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 AS37525 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS37525 in AS paths

Observed upstreams
Families
AS30844 LIQUID-AS 172 1,004
v4
AS6939 HURRICANE 57 71
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS37525 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

13 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.