Skip to main content

AS207149

SNAWNET

snaw.net networks, CH

Registry

Authoritative registration data

AS number
207149
Name
SNAWNET
Organisation
snaw.net networks, CH
Country
—
RIR
RIPE
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 AS207149
44.31.107.0/24 IPv4 /24 not checked
2a0c:b641:270::/44 IPv6 /44 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 AS207149
Address families
4b42 Internet Exchange Point: Switzerland 100 Mbps IPv6
EVIX: Peering LAN 1,000 Mbps IPv6
FogIXP 1,000 Mbps IPv4 · IPv6
ixFabric - Zurich 1,000 Mbps 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 AS207149 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS207149 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS207149 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS8298 IPNG 1 1
v6
AS35708 ASN-4IXP 1 1
v6
AS58057 SECUREBIT 1 1
v6
AS58299 OPENFACTORY-AS 1 1
v6
AS60326 DEADBEEF-AS 1 1
v6
AS209823 ENKI-AS 1 1
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.