Skip to main content

AS42511

STATION-AS

Connect LLC

Registry

Authoritative registration data

AS number
42511
Name
STATION-AS
Organisation
Connect LLC
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

0

Total announced

9

Announced prefixes

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

Prefixes announced by AS42511
109.95.72.0/21 IPv4 /21 not checked
83.143.156.0/22 IPv4 /22 not checked
194.143.150.0/23 IPv4 /23 not checked
194.143.150.0/24 IPv4 /24 not checked
194.143.151.0/24 IPv4 /24 not checked
83.143.156.0/24 IPv4 /24 not checked
83.143.157.0/24 IPv4 /24 not checked
83.143.158.0/24 IPv4 /24 not checked
83.143.159.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 AS42511
Address families
Eurasia Peering IX: Peering LAN 10,000 Mbps IPv4
GNM-IX 20,000 Mbps IPv4
Global-IX 10,000 Mbps IPv4
MSK-IX Moscow: MSK-IX peering network 10,000 Mbps IPv4
PITER-IX Helsinki 10,000 Mbps IPv4
PITER-IX Kiev 10,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 10,000 Mbps IPv4

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 AS42511 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS42511 in AS paths

Observed upstreams
Families
AS50509 TRANSROUTE 95 238
v4
AS35598 INETCOM 110 189
v4
AS62255 BEMYLINK 29 88
v4
AS25091 IP-Max 4 33
v4
AS31500 GNM-AS 11 28
v4
AS50629 LWLCOM 4 16
v4
AS47692 NESSUS 2 12
v4
AS6204 ZET-NET 1 3
v4
AS50673 Serverius-as 1 3
v4
AS13194 BITE 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS42511 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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