Skip to main content

AS329792

ORG-FIL1-AFRINIC

FIT INTERNET LTD

Registry

Authoritative registration data

AS number
329792
Name
ORG-FIL1-AFRINIC
Organisation
FIT INTERNET LTD
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

4

Total announced

11

Announced prefixes

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

Prefixes announced by AS329792
102.201.152.0/22 IPv4 /22 RPKI valid
102.201.152.0/23 IPv4 /23 not checked
102.201.154.0/23 IPv4 /23 not checked
102.201.152.0/24 IPv4 /24 not checked
102.201.153.0/24 IPv4 /24 RPKI valid
102.201.154.0/24 IPv4 /24 not checked
102.201.155.0/24 IPv4 /24 RPKI valid
2c0f:1320::/32 IPv6 /32 RPKI valid
2c0f:1320:1000::/48 IPv6 /48 not checked
2c0f:1320:1100::/48 IPv6 /48 not checked
2c0f:1320:1200::/48 IPv6 /48 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 AS329792
Address families
LINX Mombasa 10,000 Mbps IPv4 · IPv6
LINX Nairobi 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 AS329792 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS329792 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 268 939
v4 v6
AS37271 ORG-WCL1-AFRINIC 202 247
v4
AS60171 AFRIX-AS 1 3
v4
AS30844 LIQUID-AS 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS329792 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 11
v4 v6
AS328977 ORG-WISP2-AFRINIC 1 7
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.