Skip to main content

AS328699

ORG-DL6-AFRINIC

HOSTED LTD

Registry

Authoritative registration data

AS number
328699
Name
ORG-DL6-AFRINIC
Organisation
HOSTED LTD
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

2

Total announced

7

Announced prefixes

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

Prefixes announced by AS328699
102.222.104.0/23 IPv4 /23 not checked
102.222.106.0/23 IPv4 /23 not checked
102.222.105.0/24 IPv4 /24 not checked
102.222.106.0/24 IPv4 /24 not checked
102.222.107.0/24 IPv4 /24 not checked
2c0f:e8f8::/32 IPv6 /32 RPKI valid
2c0f:e8f8:2000::/40 IPv6 /40 RPKI valid

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 AS328699
Address families
MIXP: Peering 20,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 AS328699 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS328699 in AS paths

Observed upstreams
Families
AS37722 ORG-KL3-AFRINIC 244 799
v4 v6
AS6939 HURRICANE 128 179
v4 v6
AS328170 ORG-DL4-AFRINIC 83 143
v4
AS23889 ORG-mA21-AFRINIC 67 82
v4
AS37468 ORG-AC4-AFRINIC 2 3
v4 v6
AS36994 ORG-VA67-AFRINIC 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS328699 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.