Skip to main content

AS201966

OPTIKABELPL

OptiKabel Telecom Sp. z o.o.

Registry

Authoritative registration data

AS number
201966
Name
OPTIKABELPL
Organisation
OptiKabel Telecom Sp. z o.o.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

2

Total announced

8

Announced prefixes

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

Prefixes announced by AS201966
94.229.84.0/23 IPv4 /23 RPKI valid
185.92.216.0/24 IPv4 /24 not checked
185.92.217.0/24 IPv4 /24 RPKI valid
185.92.218.0/24 IPv4 /24 not checked
185.92.219.0/24 IPv4 /24 not checked
91.219.119.0/24 IPv4 /24 not checked
2a14:8900::/32 IPv6 /32 RPKI valid
2a05:2c7:c000::/34 IPv6 /34 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 AS201966
Address families
EPIX.Katowice 50,000 Mbps IPv4 · IPv6
EPIX.Warszawa 10,000 Mbps IPv4 · IPv6
THINX Warsaw 10,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 AS201966 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS201966 in AS paths

Observed upstreams
Families
AS3356 LEVEL3 133 878
v4 v6
AS174 COGENT-174 129 810
v4 v6
AS6939 HURRICANE 268 486
v4 v6
AS62178 Master_IT_Technologies 22 185
v4
AS201054 EPIX-PolMix 19 101
v4 v6
AS24748 THINX_Poland 3 74
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS201966 in AS paths

Observed downstreams
Families
AS62178 Master_IT_Technologies 18 120
v4
AS199810 UMBB-INET 48 66
v4

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

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