Network connectivity, fiber network and AS20853

DataHouse network connectivity: eTOP as telecom operator since 2001, AS20853, five geographic routes, own fiber network, peering and BGPlay view.

Operator network and BGP visibility

Network connectivity, fiber network and AS20853

DataHouse services operate on the eTOP telecom and data-center background: public AS20853, own fiber routes, geographically separated paths to exchange points and operational diagnostics through BGP, Looking Glass and RIPEstat BGPlay.

eTOP operator since 2001

The eTOP history describes the 2001 move into wide-area services using fiber and wireless technologies, RIPE membership and the first Tier1 connection.

AS20853 in public BGP

AS20853 is visible in public routing databases and can be analysed with BGP tools, Looking Glass and RIPEstat BGPlay.

Five geographic paths

The data center is connected through five geographically separated routes, so network design does not depend on a single physical direction.

Own fiber network

Own fiber infrastructure helps combine data-center access, FTTB links, colocation and customer connectivity into one operational model.

Logical BGP and peering map

AS20853: data center, IXPs, transit and customer paths

AS20853eTOP / DataHouseDataHouse WarsawDE-CIX FrankfurtEPIX WarsawEPIX KatowiceEquinix WarsawGiganet IXNTransit / upstreamCustomers

The diagram is a simplified logical view. BGPlay shows public BGP paths from RIPE RIS collectors, not a physical fiber scheme.

RIPEstat BGPlay AS20853   bgp.tools AS20853   PeeringDB AS20853

What can be verified publicly

AS20853AS-ETOPLooking GlassRPKIDE-CIXEPIXEquinix WarsawTPIX / THINX

PeeringDB profile

PeeringDB identifies ETOP Sp z o.o. as AS20853, lists Datahouse.pl as an alias, shows AS-ETOP, the public Looking Glass and exchange points such as DE-CIX Frankfurt, EPIX Warsaw/Katowice, Equinix Warsaw, Giganet IXN, THINX and TPIX.

BGP and RPKI visibility

Public BGP databases show AS20853, originated prefixes, upstreams, peers and RPKI status. This is useful before colocation, IP transit, private cloud and migration projects.

BGPlay route view

RIPEstat BGPlay visualizes BGP paths and changes for an AS or prefix. It is a diagnostic view from route collectors and complements the DataHouse Looking Glass.

Why it matters for colocation

A colocated server is only as useful as its power, access and network path. AS20853, exchange points and physically separated routes help plan predictable connectivity instead of treating bandwidth as a generic add-on.

Why it matters for cloud and VPS

Cloud servers, VPS, backup and administration still depend on network quality: latency, route stability, DNS, firewall rules, DDoS response and diagnostics during incidents.

How we use diagnostics

Looking Glass, speed tests, DNS checks and public BGP views help separate an application problem from a route, DNS, SSL, firewall or external-provider issue.

When to ask for a network design

Ask for a network design when you need IP transit, BGP, separated uplinks, cross-connect, private links, hybrid cloud, backup replication or a migration with a controlled rollback path.

Frequently asked questions

What is AS20853?

AS20853 is the public autonomous system used by eTOP / DataHouse in Internet routing. It lets public BGP tools show prefixes, peers, upstreams and route paths related to the network.

What does five geographic paths mean?

It means the data center is connected through five geographically separated directions, reducing dependence on one physical route and helping plan resilient colocation, cloud and migration projects.

Can I verify routing before migration?

Yes. Use DataHouse Looking Glass, RIPEstat BGPlay, bgp.tools and DNS or speed tests to compare route visibility, latency and diagnostics before a production change.

Is the BGPlay map a physical network map?

No. BGPlay is a public BGP route-collector view. It complements, but does not replace, the physical fiber and operational network design prepared for a specific customer project.