Skip to main content

AS37673

ORG-TA32-AFRINIC

Telemasters

Registry

Authoritative registration data

AS number
37673
Name
ORG-TA32-AFRINIC
Organisation
Telemasters
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

0

Total announced

8

Announced prefixes

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

Prefixes announced by AS37673
196.223.56.0/22 IPv4 /22 not checked
196.223.60.0/22 IPv4 /22 not checked
41.77.24.0/22 IPv4 /22 not checked
41.77.28.0/22 IPv4 /22 not checked
196.223.56.0/23 IPv4 /23 not checked
196.223.62.0/23 IPv4 /23 not checked
196.223.62.0/24 IPv4 /24 not checked
41.77.27.0/24 IPv4 /24 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 AS37673
Address families
NAPAfrica IX Cape Town 1,000 Mbps IPv4
NAPAfrica IX Durban 1,000 Mbps IPv4
NAPAfrica IX Johannesburg: Peering 10,000 Mbps IPv4

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 AS37673 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS37673 in AS paths

Observed upstreams
Families
AS22355 ORG-FN1-AFRINIC 580 1,491
v4
AS3741 ORG-DD1-AFRINIC 3 11
v4

No rows match “”.

Showing – of

Observed downstreams

4 networks seen after AS37673 in AS paths

Observed downstreams
Families
AS328872 ORG-STL9-AFRINIC 156 187
v4
AS328371 ORG-PCL3-AFRINIC 152 174
v4
AS328912 ORG-MCL7-AFRINIC 144 166
v4
AS329266 ORG-IITL1-AFRINIC 5 5
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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