Skip to main content

AS200750

KLIKOM_NET

Klikom.net Sp.z o.o.

Registry

Authoritative registration data

AS number
200750
Name
KLIKOM_NET
Organisation
Klikom.net Sp.z o.o.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

10

IPv6 prefixes

1

Total announced

11

Announced prefixes

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

Prefixes announced by AS200750
91.227.64.0/22 IPv4 /22 not checked
194.180.108.0/23 IPv4 /23 RPKI valid
194.180.170.0/23 IPv4 /23 RPKI valid
91.227.64.0/23 IPv4 /23 not checked
91.227.66.0/23 IPv4 /23 not checked
194.180.108.0/24 IPv4 /24 not checked
194.180.109.0/24 IPv4 /24 not checked
194.180.170.0/24 IPv4 /24 not checked
194.180.171.0/24 IPv4 /24 not checked
91.227.63.0/24 IPv4 /24 RPKI valid
2a0f:4640::/29 IPv6 /29 RPKI valid

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 AS200750
Address families
EPIX.Katowice 40,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 AS200750 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS200750 in AS paths

Observed upstreams
Families
AS5617 TPNET 201 415
v4 v6
AS50607 EPIX-KTW-GlobalMix 58 225
v4
AS201054 EPIX-PolMix 41 127
v4
AS202520 SKYPASS-AS 101 117
v4
AS33891 CORE-BACKBONE 8 67
v4
AS6204 ZET-NET 1 7
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS200750 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 34
v4
AS49544 i3Dnet 1 7
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.