Skip to main content

AS328842

ORG-PAL1-AFRINIC

ProData Africa Limited

Registry

Authoritative registration data

AS number
328842
Name
ORG-PAL1-AFRINIC
Organisation
ProData Africa Limited
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

0

Total announced

1

Announced prefixes

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

Prefixes announced by AS328842
102.220.223.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 AS328842
Address families
Accra Internet Exchange LBG 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 AS328842 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS328842 in AS paths

Observed upstreams
Families
AS37468 ORG-AC4-AFRINIC 1,426 2,400
v4
AS60171 AFRIX-AS 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

5 networks seen after AS328842 in AS paths

Observed downstreams
Families
AS328530 ORG-GCUC1-AFRINIC 264 572
v4
AS327947 ORG-TUOS1-AFRINIC 240 543
v4
AS327727 ORG-CL10-AFRINIC 226 435
v4
AS328648 ORG-KTU2-AFRINIC 235 286
v4
AS328752 ORG-CSUC2-AFRINIC 234 286
v4

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS36236 NETACTUATE 1 1
v4
AS37721 ORG-VTS1-AFRINIC 1 1
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.