Skip to main content

AS203937

Cyfrotel

MAREK BZDZIUCH trading as CYFROTEL Sp. J.

Registry

Authoritative registration data

AS number
203937
Name
Cyfrotel
Organisation
MAREK BZDZIUCH trading as CYFROTEL Sp. J.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

1

Total announced

9

Announced prefixes

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

Prefixes announced by AS203937
185.119.120.0/22 IPv4 /22 not checked
185.131.240.0/23 IPv4 /23 not checked
194.42.118.0/23 IPv4 /23 not checked
185.125.4.0/24 IPv4 /24 not checked
185.131.242.0/24 IPv4 /24 not checked
185.131.243.0/24 IPv4 /24 not checked
185.216.172.0/24 IPv4 /24 not checked
185.253.233.0/24 IPv4 /24 not checked
2a06:dec0::/32 IPv6 /32 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 AS203937
Address families
EPIX.Katowice 10,000 Mbps IPv4
EPIX.Warszawa 10,000 Mbps IPv4
TPIX PL 20,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 AS203937 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS203937 in AS paths

Observed upstreams
Families
AS29535 234 2,496
v4
AS5617 44 440
v4
AS50607 176 231
v4 v6
AS6204 5 56
v4
AS201054 22 49
v4 v6
AS62081 6 47
v4
AS24482 SGGS-AS-AP 3 18
v4 v6

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS203937 in AS paths

Observed downstreams
Families
AS197294 4 4
v4

No rows match “”.

Showing of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 16
v4
AS28917 1 8
v4
AS36236 NETACTUATE 1 8
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.