Skip to main content

AS50247

ITCOMP

ITCOMP sp. z o.o

Registry

Authoritative registration data

AS number
50247
Name
ITCOMP
Organisation
ITCOMP sp. z o.o
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 AS50247
109.196.80.0/20 IPv4 /20 not checked
109.95.88.0/21 IPv4 /21 not checked
185.178.236.0/22 IPv4 /22 not checked
109.197.36.0/23 IPv4 /23 not checked
185.129.124.0/23 IPv4 /23 not checked
185.129.126.0/23 IPv4 /23 not checked
45.85.184.0/23 IPv4 /23 not checked
91.224.142.0/23 IPv4 /23 not checked
109.207.103.0/24 IPv4 /24 not checked
185.191.144.0/24 IPv4 /24 not checked
185.191.145.0/24 IPv4 /24 not checked
193.106.238.0/24 IPv4 /24 not checked
194.1.252.0/24 IPv4 /24 not checked
45.131.33.0/24 IPv4 /24 not checked
45.131.34.0/24 IPv4 /24 not checked
91.218.240.0/24 IPv4 /24 not checked
2a0a:7080::/29 IPv6 /29 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 AS50247
Address families
EPIX.Katowice 80,000 Mbps IPv4 · IPv6
EPIX.Warszawa 40,000 Mbps IPv4 · IPv6
TPIX PL 100,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 AS50247 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS50247 in AS paths

Observed upstreams
Families
AS62081 162 3,003
v4
AS5617 230 2,356
v4
AS201054 EPIX-PolMix 23 326
v4
AS6939 HURRICANE 40 90
v4
AS28917 2 18
v4
AS6204 1 16
v4
AS1820 1 1
v6
AS20473 1 1
v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS50247 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 159
v4 v6
AS49544 i3Dnet 1 34
v4 v6
AS36236 NETACTUATE 1 17
v4 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.