Skip to main content

AS329258

ORG-NTL5-AFRINIC

Nextgen Telcoms LTD

Registry

Authoritative registration data

AS number
329258
Name
ORG-NTL5-AFRINIC
Organisation
Nextgen Telcoms 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 AS329258
102.213.76.0/24 IPv4 /24 not checked
102.213.77.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 AS329258
Address families
IXPN Lagos 5,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 AS329258 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS329258 in AS paths

Observed upstreams
Families
AS37662 ORG-WIOC1-AFRINIC 276 381
v4
AS37271 ORG-WCL1-AFRINIC 242 316
v4
AS6939 HURRICANE 17 18
v4
AS37468 ORG-AC4-AFRINIC 3 5
v4
AS37282 ORG-MCC1-AFRINIC 1 2
v4
AS60171 AFRIX-AS 1 2
v4
AS58453 CMI-INT-HK 1 1
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS329258 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.