Skip to main content

AS50550

K3

K3 Telecom Sp. z o.o.

Registry

Authoritative registration data

AS number
50550
Name
K3
Organisation
K3 Telecom Sp. z o.o.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

0

Total announced

6

Announced prefixes

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

Prefixes announced by AS50550
109.207.100.0/24 IPv4 /24 not checked
109.207.102.0/24 IPv4 /24 not checked
109.207.96.0/24 IPv4 /24 not checked
109.207.97.0/24 IPv4 /24 not checked
109.207.98.0/24 IPv4 /24 not checked
109.207.99.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 AS50550
Address families
EPIX.Katowice 10,000 Mbps IPv4
EPIX.Warszawa 20,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 AS50550 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS50550 in AS paths

Observed upstreams
Families
AS62081 649 1,717
v4
AS50607 158 368
v4
AS201054 EPIX-PolMix 42 123
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS50550 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 50
v4
AS49544 i3Dnet 1 12
v4
AS36236 NETACTUATE 2 6
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.