Skip to main content

AS329740

ORG-TSL15-AFRINIC

TRYANNET SOLUTIONS LIMITED

Registry

Authoritative registration data

AS number
329740
Name
ORG-TSL15-AFRINIC
Organisation
TRYANNET SOLUTIONS LIMITED
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 AS329740
102.202.152.0/23 IPv4 /23 not checked
2c0f:ba0::/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 AS329740
Address families
AF-CIX 10,000 Mbps IPv4 · IPv6
IXPN Lagos 1,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 AS329740 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS329740 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 244 350
v4 v6
AS37271 ORG-WCL1-AFRINIC 243 347
v4 v6
AS60171 AFRIX-AS 1 2
v4 v6
AS37282 ORG-MCC1-AFRINIC 1 1
v4
AS58453 CMI-INT-HK 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS329740 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
AS37721 ORG-VTS1-AFRINIC 1 3
v4 v6
AS36236 NETACTUATE 1 2
v4 v6

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.