Skip to main content

AS13000

LEON-AS

Leon Sp. z o.o.

Registry

Authoritative registration data

AS number
13000
Name
LEON-AS
Organisation
Leon Sp. z o.o.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

39

IPv6 prefixes

3

Total announced

42

Announced prefixes

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

Prefixes announced by AS13000
188.137.0.0/17 IPv4 /17 not checked
188.137.80.0/20 IPv4 /20 not checked
87.101.64.0/20 IPv4 /20 not checked
188.137.56.0/21 IPv4 /21 not checked
188.137.64.0/21 IPv4 /21 not checked
188.137.72.0/21 IPv4 /21 not checked
62.182.224.0/21 IPv4 /21 not checked
87.239.192.0/21 IPv4 /21 not checked
89.200.224.0/21 IPv4 /21 not checked
188.137.100.0/22 IPv4 /22 not checked
188.137.28.0/22 IPv4 /22 not checked
188.137.32.0/22 IPv4 /22 not checked
188.137.36.0/22 IPv4 /22 not checked
188.137.40.0/22 IPv4 /22 not checked
188.137.44.0/22 IPv4 /22 not checked
188.137.48.0/22 IPv4 /22 not checked
188.137.52.0/22 IPv4 /22 not checked
193.34.112.0/22 IPv4 /22 not checked
193.93.92.0/22 IPv4 /22 not checked
195.3.200.0/22 IPv4 /22 not checked
87.101.64.0/22 IPv4 /22 not checked
87.101.68.0/22 IPv4 /22 not checked
87.101.72.0/22 IPv4 /22 not checked
87.101.76.0/22 IPv4 /22 not checked
89.200.224.0/22 IPv4 /22 not checked
89.200.228.0/22 IPv4 /22 not checked
91.200.24.0/22 IPv4 /22 not checked
91.214.24.0/22 IPv4 /22 not checked
188.137.96.0/23 IPv4 /23 not checked
193.150.36.0/23 IPv4 /23 not checked
91.195.134.0/23 IPv4 /23 not checked
91.195.158.0/23 IPv4 /23 not checked
91.195.190.0/23 IPv4 /23 not checked
91.207.64.0/23 IPv4 /23 not checked
185.191.246.0/24 IPv4 /24 not checked
188.137.2.0/24 IPv4 /24 not checked
195.3.203.0/24 IPv4 /24 not checked
195.66.73.0/24 IPv4 /24 not checked
91.208.247.0/24 IPv4 /24 not checked
2a02:c40::/32 IPv6 /32 not checked
2a02:c40:2::/48 IPv6 /48 not checked
2a02:c40:8100::/48 IPv6 /48 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 AS13000
Address families
AMS-IX 10,000 Mbps IPv4 · IPv6
DE-CIX Frankfurt: DE-CIX Frankfurt Peering LAN 30,000 Mbps IPv4 · IPv6
EPIX.Katowice 80,000 Mbps IPv4 · IPv6
THINX Warsaw 40,000 Mbps IPv4 · IPv6
TPIX PL 80,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 AS13000 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

29 networks seen before AS13000 in AS paths

Observed upstreams
Families
AS15744 1,132 5,231
v4 v6
AS174 COGENT-174 689 3,958
v4
AS6939 HURRICANE 284 2,105
v4 v6
AS5617 336 449
v4
AS5405 31 388
v4 v6
AS33891 CORE-BACKBONE 19 220
v4
AS3257 GTT-BACKBONE 131 162
v4
AS24748 10 118
v4 v6
AS12552 7 112
v4
AS6204 9 88
v4
AS28917 9 51
v4
AS34019 HIVANE 2 12
v6
AS48362 TKSWF-AS 2 12
v6
AS9002 RETN-AS 3 7
v6
AS6057 6057 2 6
v6
AS34927 iFog-GmbH 2 6
v6
AS35280 F5 2 6
v6
AS35625 EUROFIBER-FRANCE 2 6
v6
AS39351 ESAB-AS 2 6
v6
AS8758 IWAY 1 6
v6
AS12859 2 5
v6
AS1764 NEXTLAYER-AS 1 3
v6
AS7195 7195 1 3
v6
AS60171 1 3
v6
AS201054 EPIX-PolMix 1 3
v6
AS212024 RISSON 1 3
v6
AS50673 2 2
v6
AS205103 1 2
v6
AS24889 MONZOON-AS 1 1
v6

No rows match “”.

Showing of

Observed downstreams

7 networks seen after AS13000 in AS paths

Observed downstreams
Families
AS49001 301 1,382
v4
AS12642 270 692
v4
AS39255 185 355
v4
AS39412 270 346
v4
AS47129 270 346
v4
AS202037 269 346
v4
AS198469 139 189
v4

No rows match “”.

Showing of

Uncertain adjacencies

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