Skip to main content

AS42656

QXL-POLAND

Allegro sp. z o.o.

Registry

Authoritative registration data

AS number
42656
Name
QXL-POLAND
Organisation
Allegro sp. z o.o.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

21

IPv6 prefixes

6

Total announced

27

Announced prefixes

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

Prefixes announced by AS42656
5.134.208.0/21 IPv4 /21 not checked
178.21.152.0/22 IPv4 /22 not checked
185.31.24.0/22 IPv4 /22 not checked
178.21.156.0/23 IPv4 /23 not checked
193.203.222.0/23 IPv4 /23 not checked
91.194.188.0/23 IPv4 /23 not checked
91.207.14.0/23 IPv4 /23 not checked
178.21.153.0/24 IPv4 /24 not checked
185.31.25.0/24 IPv4 /24 not checked
185.31.26.0/24 IPv4 /24 not checked
185.31.27.0/24 IPv4 /24 not checked
193.203.223.0/24 IPv4 /24 not checked
193.23.48.0/24 IPv4 /24 not checked
194.0.251.0/24 IPv4 /24 not checked
5.134.209.0/24 IPv4 /24 not checked
5.134.211.0/24 IPv4 /24 not checked
5.134.212.0/24 IPv4 /24 not checked
5.134.213.0/24 IPv4 /24 not checked
5.134.215.0/24 IPv4 /24 not checked
91.194.188.0/24 IPv4 /24 not checked
91.207.14.0/24 IPv4 /24 not checked
2a02:dc8::/29 IPv6 /29 not checked
2a02:dc8::/32 IPv6 /32 not checked
2a02:dcc::/32 IPv6 /32 not checked
2a02:dcd::/32 IPv6 /32 not checked
2a02:dce::/32 IPv6 /32 not checked
2a02:dcc:22::/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 AS42656
Address families
EPIX.Warszawa 100,000 Mbps IPv4 · IPv6
Equinix Warsaw 100,000 Mbps IPv4 · IPv6
NIX.CZ: Public peering VLAN 25,000 Mbps IPv4 · IPv6
POZIX 20,000 Mbps IPv4 · IPv6
Peering.cz 100,000 Mbps IPv4 · IPv6
TPIX PL 100,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 AS42656 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

24 networks seen before AS42656 in AS paths

Observed upstreams
Families
AS3356 LEVEL3 536 5,110
v4 v6
AS1299 TWELVE99 366 1,998
v4 v6
AS6939 HURRICANE 134 722
v4 v6
AS8218 NEO-ASN 15 358
v4 v6
AS6762 SEABONE-NET 138 342
v4 v6
AS24482 SGGS-AS-AP 4 342
v4 v6
AS24115 ASN-EQIX-MLPE 20 175
v4 v6
AS14840 ASN14840 6 150
v4 v6
AS1764 NEXTLAYER-AS 10 135
v4 v6
AS33891 CORE-BACKBONE 15 132
v4 v6
AS4455 BSO 5 75
v4 v6
AS5617 TPNET 6 40
v4 v6
AS20562 OPEN-PEERING-AS 7 29
v4 v6
AS22356 ASN22356 4 27
v4 v6
AS6663 TTI-NET 3 25
v4 v6
AS137409 GSLNETWORKS-AS-AP 3 25
v4 v6
AS6204 ZET-NET 2 23
v4
AS29632 NASSIST-AS 6 18
v6
AS13194 BITE 1 11
v4
AS21215 UGNI 1 11
v4
AS201054 EPIX-PolMix 2 6
v6
AS50629 LWLCOM 4 4
v6
AS9009 M247 1 1
v4
AS39120 CONVERGENZE-AS 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS42656 in AS paths

Observed downstreams
Families
AS201629 267 1,000
v4
AS210641 allegro-nr 260 340
v6
AS44424 AS44424 1 1
v4

No rows match “”.

Showing – of

Uncertain adjacencies

17 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 3 62
v4 v6
AS51184 FONIRA 3 60
v4 v6
AS212483 level86 3 60
v4 v6
AS28917 Fiord-AS 3 37
v4 v6
AS59890 Kabel-TV-Lampert 2 34
v4 v6
AS29504 LBCFREE 3 30
v4 v6
AS36236 NETACTUATE 3 30
v4 v6
AS198150 SIACOM-AS 3 30
v4 v6
AS6881 NIXCZ 3 29
v4 v6
AS40994 Alwyzon 3 29
v4 v6
AS47692 NESSUS 2 24
v4
AS3212 TELEMACH 2 17
v4 v6
AS6424 EDGOO 2 17
v4 v6
AS37721 ORG-VTS1-AFRINIC 2 17
v4 v6
AS35369 LINZAG-TELEKOM-AS 2 12
v4
AS8529 OMANTEL-AS 1 10
v6
AS41327 FIBERTELECOM-AS 1 5
v6

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.