Skip to main content

AS37398

ORG-JsL1-AFRINIC

Juniper solutions Limited

Registry

Authoritative registration data

AS number
37398
Name
ORG-JsL1-AFRINIC
Organisation
Juniper solutions Limited
Country
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

0

Total announced

5

Announced prefixes

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

Prefixes announced by AS37398
41.77.168.0/22 IPv4 /22 not checked
41.77.172.0/22 IPv4 /22 not checked
41.77.172.0/23 IPv4 /23 not checked
41.77.174.0/24 IPv4 /24 not checked
41.77.175.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 AS37398
Address families
AMS-IX Lagos: Main 1,000 Mbps IPv4 · IPv6
IXPN Lagos 100 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 AS37398 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS37398 in AS paths

Observed upstreams
Families
AS37282 ORG-MCC1-AFRINIC 285 1,677
v4
AS37468 ORG-AC4-AFRINIC 2 6
v4
AS60171 AFRIX-AS 1 3
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS37398 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 3
v4
AS37721 ORG-VTS1-AFRINIC 1 3
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.