Network · BGP

Our network: AS47263

Anyone promising high availability should not depend on third parties for routing. We operate our own autonomous system with fixed IP address space, redundant upstreams, and peering in Frankfurt – the foundation of every managed cluster.

Fundamentals

What running our own autonomous system means.

AS47263 is our own autonomous system – the Cube-Hosting network that all managed clusters are connected through. We speak BGP with the world ourselves: which paths our traffic takes is decided by our routers, not by a single upstream provider.

That is more than a technical detail. It means: fixed IPv4 and IPv6 address space, announced via AS47263 – with the routing in our hands. Multiple independent upstreams, so the failure of one carrier does not cut the network off. And direct peering at internet exchanges, so traffic to major networks takes the short path instead of a detour via third parties.

Key facts

AS47263 at a glance.

  • Our own autonomous system: AS47263, operated by Cube-Hosting, RIPE region Germany.
  • Fixed IP address space: multiple IPv4 prefixes and native IPv6, announced and routed via AS47263.
  • Redundant upstreams: several independent transit carriers – the failure of one provider does not cut the network off.
  • Peering at internet exchanges: including ERA-IX Frankfurt, NL-ix, and frankonIX – short paths to major networks.
  • DE-CIX connectivity at the Frankfurt site, directly at Europe's most important internet exchange.
  • DDoS protection at the network layer, before attacks reach your cluster.
  • Public looking glass: live routing visible at lg.cube-hosting.net.
  • Transparency: prefixes and peerings publicly documented, e.g. on bgp.tools.

Architecture

Redundantly connected, redundantly built.

Diagram: connectivity via AS47263. Multiple independent upstreams and IX peering converge on redundant core routers; behind them sits your cluster.

Inside the network, the same rigor applies as in the cluster: redundant core routers, bonding on every node uplink, and separate networks for management, storage, and public traffic – the details are covered in the network architecture on the home page and in the design phase.

FAQ

Common questions about the network.

Why is your own AS relevant for me as a customer?

Because routing decisions are in our hands: if a carrier fails, BGP automatically reroutes via the remaining upstreams – without us waiting on an upstream provider's support. And your cluster IPs are routed within our network – control over them lies with us, not with a third party.

Does my cluster get fixed IP addresses?

Yes. Your cluster receives fixed IPv4 addresses and, on request, dedicated IPv6 subnets from our address space – including clean reverse DNS.

Can we bring our own IP ranges?

If you own provider-independent address space (PI space), we can announce it via AS47263 after verification. We clarify this in the design phase.

How does the DDoS protection work?

Attacks are detected and filtered at the network layer before they reach your cluster – complemented by firewalling at the cluster level. For particularly exposed applications we define additional protective measures in the concept.

Can I inspect the routing myself?

Yes – our looking glass at lg.cube-hosting.net is public. There you can see live how AS47263 routes; independent views are available from services such as bgp.tools.

Contact

A cluster is only as good as its network.

Briefly describe your project. You will receive an initial assessment within one business day, free of charge and without obligation.

Request a project