Skip to main content

AS206492

NEXPHONE

Nexphone AG

Registry

Authoritative registration data

AS number
206492
Name
NEXPHONE
Organisation
Nexphone AG
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

1

Total announced

9

Announced prefixes

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

Prefixes announced by AS206492
185.185.32.0/22 IPv4 /22 not checked
194.148.52.0/22 IPv4 /22 not checked
194.191.112.0/22 IPv4 /22 not checked
45.150.248.0/22 IPv4 /22 not checked
185.185.32.0/24 IPv4 /24 not checked
5.154.170.0/24 IPv4 /24 not checked
62.65.137.0/24 IPv4 /24 not checked
212.25.7.64/28 IPv4 /28 not checked
2a0b:4d80::/29 IPv6 /29 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 AS206492
Address families
SwissIX: Peering 2,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 AS206492 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

18 networks seen before AS206492 in AS paths

Observed upstreams
Families
AS212865 NETCONNECT 180 878
v4
AS8758 IWAY 105 677
v4
AS1836 GREEN 181 467
v4 v6
AS6939 HURRICANE 79 225
v4 v6
AS8218 NEO-ASN 2 57
v4 v6
AS34019 HIVANE 4 48
v4 v6
AS5405 INTERDOTLINK 9 45
v4 v6
AS47147 AS-ANX 2 36
v4 v6
AS48362 TKSWF-AS 2 32
v4 v6
AS1764 NEXTLAYER-AS 2 22
v4 v6
AS33891 CORE-BACKBONE 8 18
v4
AS24961 MYLOC-AS 2 16
v4 v6
AS39351 ESAB-AS 2 16
v4 v6
AS9002 RETN-AS 11 15
v6
AS25091 IP-Max 2 8
v4
AS9009 M247 1 2
v4
AS4601 DNET 1 1
v6
AS21215 UGNI 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS206492 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

32 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.