Skip to main content

AS328125

ORG-FA2-AFRINIC

Forbtech

Registry

Authoritative registration data

AS number
328125
Name
ORG-FA2-AFRINIC
Organisation
Forbtech
Country
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS328125
196.250.224.0/21 IPv4 /21 not checked
2c0f:f0f0::/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 AS328125
Address families
NAPAfrica IX Johannesburg: Peering 1,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 AS328125 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS328125 in AS paths

Observed upstreams
Families
AS327983 384 557
v4 v6
AS327782 ORG-MN2-AFRINIC 93 122
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS328125 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

11 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS917 MISAKA 1 1
v4
AS24482 SGGS-AS-AP 1 1
v4
AS32653 1 1
v4
AS36236 NETACTUATE 1 1
v4
AS37239 1 1
v4
AS37697 1 1
v4
AS37721 ORG-VTS1-AFRINIC 1 1
v4
AS327804 1 1
v4
AS327960 1 1
v4
AS328137 1 1
v4
AS328320 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.