Skip to main content

AS328562

ORG-SC5-AFRINIC

Swift Connect Private Company

Registry

Authoritative registration data

AS number
328562
Name
ORG-SC5-AFRINIC
Organisation
Swift Connect Private Company
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

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

Prefixes announced by AS328562
102.23.144.0/20 IPv4 /20 not checked
102.23.144.0/21 IPv4 /21 not checked
102.23.152.0/21 IPv4 /21 not checked
2c0f:71c0::/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 AS328562
Address families
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 AS328562 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS328562 in AS paths

Observed upstreams
Families
AS37100 ORG-SL75-AFRINIC 655 1,573
v4 v6
AS6939 HURRICANE 92 404
v4
AS37468 ORG-AC4-AFRINIC 12 39
v4
AS39120 CONVERGENZE-AS 2 6
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS328562 in AS paths

Observed downstreams
Families
AS328704 ORG-WTC1-AFRINIC 305 1,332
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.