Skip to main content

AS47252

LUKSUS-AS

Grzegorz Wloch trading as LUKSUS

Registry

Authoritative registration data

AS number
47252
Name
LUKSUS-AS
Organisation
Grzegorz Wloch trading as LUKSUS
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

10

IPv6 prefixes

0

Total announced

10

Announced prefixes

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

Prefixes announced by AS47252
185.241.252.0/22 IPv4 /22 not checked
195.238.164.0/22 IPv4 /22 not checked
155.133.30.0/23 IPv4 /23 not checked
155.133.36.0/23 IPv4 /23 not checked
155.133.39.0/24 IPv4 /24 not checked
185.251.182.0/24 IPv4 /24 not checked
193.168.218.0/24 IPv4 /24 not checked
194.140.233.0/24 IPv4 /24 not checked
195.88.150.0/24 IPv4 /24 not checked
195.88.151.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 AS47252
Address families
EPIX.Katowice 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 AS47252 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS47252 in AS paths

Observed upstreams
Families
AS50607 271 3,466
v4
AS50606 VIRTUAOPERATOR-AS 21 250
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS47252 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 70
v4
AS49544 i3Dnet 1 20
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.