Skip to main content

AS42905

LIMANET

LTD LIMANET

Registry

Authoritative registration data

AS number
42905
Name
LIMANET
Organisation
LTD LIMANET
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

16

IPv6 prefixes

1

Total announced

17

Announced prefixes

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

Prefixes announced by AS42905
81.163.216.0/21 IPv4 /21 not checked
141.105.132.0/22 IPv4 /22 not checked
195.62.36.0/23 IPv4 /23 not checked
141.105.128.0/24 IPv4 /24 not checked
141.105.132.0/24 IPv4 /24 not checked
141.105.133.0/24 IPv4 /24 not checked
141.105.134.0/24 IPv4 /24 not checked
141.105.135.0/24 IPv4 /24 not checked
193.200.151.0/24 IPv4 /24 not checked
193.39.118.0/24 IPv4 /24 not checked
195.62.36.0/24 IPv4 /24 not checked
195.62.37.0/24 IPv4 /24 not checked
81.163.220.0/24 IPv4 /24 not checked
81.163.223.0/24 IPv4 /24 not checked
91.193.194.0/24 IPv4 /24 not checked
91.199.245.0/24 IPv4 /24 not checked
2a02:680:9100::/40 IPv6 /40 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 AS42905
Address families
1-IX EU 80,000 Mbps IPv4 · IPv6
1-IX UA 200,000 Mbps IPv4 · IPv6
DTEL-IX: PUBLIC 160,000 Mbps IPv4 · IPv6
Giganet IXN Frankfurt 80,000 Mbps IPv4 · IPv6
Giganet IXN Odesa: Odessa local exchange 80,000 Mbps IPv4 · IPv6
Giganet IXN Warsaw: Warsaw local exchange 80,000 Mbps IPv4 · IPv6
Giganet IXN: Global exchange 120,000 Mbps IPv4 · IPv6
UA-IX 50,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 AS42905 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

21 networks seen before AS42905 in AS paths

Observed upstreams
Families
AS50263 535 1,711
v4 v6
AS9002 RETN-AS 618 1,663
v4 v6
AS35320 235 712
v4 v6
AS6939 HURRICANE 135 583
v4 v6
AS24482 SGGS-AS-AP 5 226
v4 v6
AS3303 SWISSCOM 32 201
v4
AS8218 NEO-ASN 19 152
v4 v6
AS14840 ASN14840 10 80
v4 v6
AS50629 LWLCOM 15 40
v4 v6
AS49434 10 31
v4 v6
AS42295 TBISS-AS 10 30
v4
AS6663 5 30
v4
AS1257 SWIPNET 6 18
v4 v6
AS6204 5 15
v4
AS62000 5 15
v4
AS263444 5 15
v4
AS15958 1 2
v4
AS21215 1 2
v4
AS39120 1 2
v4
AS30886 1 1
v6
AS60812 1 1
v4

No rows match “”.

Showing of

Observed downstreams

6 networks seen after AS42905 in AS paths

Observed downstreams
Families
AS44800 283 700
v4
AS52128 328 666
v4
AS202483 281 350
v4
AS56401 260 320
v4
AS43384 5 5
v4
AS21497 1 1
v4

No rows match “”.

Showing of

Uncertain adjacencies

10 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 5 48
v4 v6
AS212483 level86 5 32
v4 v6
AS59514 6 23
v4
AS48919 4 23
v4 v6
AS209823 4 23
v4 v6
AS34927 iFog-GmbH 5 17
v4
AS198150 SIACOM-AS 5 16
v4 v6
AS29049 5 15
v4
AS44901 1 8
v4
AS13004 1 2
v4

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.