Skip to main content

AS42765

LINER

------------------ Uplinks (localpref=100) ------------------

Registry

Authoritative registration data

AS number
42765
Name
LINER
Organisation
------------------ Uplinks (localpref=100) ------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

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

Prefixes announced by AS42765
213.108.208.0/21 IPv4 /21 not checked
171.25.164.0/22 IPv4 /22 not checked
91.204.148.0/22 IPv4 /22 not checked
91.233.168.0/22 IPv4 /22 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 AS42765
Address families
GNM-IX 100,000 Mbps IPv4
Global-IX 100,000 Mbps IPv4
PITER-IX Frankfurt 100,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 100,000 Mbps IPv4
PITER-IX Riga: RIX_PEERING_VLAN 100,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 100,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 AS42765 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

20 networks seen before AS42765 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS42765 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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