Skip to main content

AS199947

Nexusway

Nexusway srl

Registry

Authoritative registration data

AS number
199947
Name
Nexusway
Organisation
Nexusway srl
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS199947
185.41.32.0/22 IPv4 /22 not checked
45.140.84.0/22 IPv4 /22 not checked
2a01:5420::/32 IPv6 /32 RPKI valid

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 AS199947
Address families
MIX Bologna 10,000 Mbps IPv4 · IPv6
MIX-IT 10,000 Mbps IPv4 · IPv6
VSIX: Primary 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 AS199947 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS199947 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 267 861
v4 v6
AS9002 RETN-AS 105 176
v4 v6
AS8218 NEO-ASN 2 16
v4
AS2593 ASN-VSIX 1 3
v4 v6
AS6204 ZET-NET 1 2
v4
AS60171 AFRIX-AS 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS199947 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

17 adjacencies that may be an artefact of collector peering

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.