Skip to main content

AS328528

ORG-NSL5-AFRINIC

NetIT Solutions LTD

Registry

Authoritative registration data

AS number
328528
Name
ORG-NSL5-AFRINIC
Organisation
NetIT Solutions LTD
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS328528
102.220.213.0/24 IPv4 /24 not checked
102.36.160.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 AS328528
Address families
AF-CIX 1,000 Mbps IPv4 · IPv6
IXPN Lagos 1,024 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 AS328528 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS328528 in AS paths

Observed upstreams
Families
AS36873 ORG-VNL1-AFRINIC 103 248
v4
AS37613 ORG-EISL1-AFRINIC 103 236
v4
AS6939 HURRICANE 27 56
v4
AS37468 ORG-AC4-AFRINIC 5 7
v4
AS37282 ORG-MCC1-AFRINIC 1 2
v4
AS60171 AFRIX-AS 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS328528 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS36236 NETACTUATE 1 2
v4
AS37721 ORG-VTS1-AFRINIC 1 2
v4

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.