Already Stelia Enabled
Service Uptime SLA
Site to Site capacity
No set up or fixed cost
This page contains Stelia IX’s rules and regulations which members must follow. They should be read in conjunction with the Stelia conduct guidelines which govern members’ relationship with Stelia and are available to members on request.
Stelia IX is available across every enabled Stelia facility, advocating borderless and open peering with our vibrant ecosystem of AI, HPC, Service provider and research institution members.
Consumption Only Billing
Stelia advocates an open internet and open peering. Our IX is free to connect to at any port capacity, paying only a fractional pence per GB consumed on a monthly basis, visible in our real time reporting application, Cora.
As a Stelia member, you’ll able to exchange traffic with a growing list of fellow Stelia members. This reduces the amount of traffic you’ll need to send through your upstream provider, reducing your bandwidth usage and the cost of your IP transit.
Stelia members can keep traffic local by exchanging it closer to its source or destination. This is preferable to sending traffic via upstream providers that rely on more convoluted routes, and means that the time a data packet takes to reach its destination is minimised.
Organisational Rules and Requirements
Members must publish their contact information to whom requests for peering should be sent.
Members must subscribe at least one e-mail address to the members annoucement email system for regular IX updates.
Members must not carry out any illegal activity through Stelia IX.
Members must not circulate correspondence on confidential Stelia mailing lists or any other Stelia confidential information to non-members.
- Members must have an Autonomous System number registered with RIPE or other appropriate authority.
- All networks announced at Stelia must be registered with RIPE or other appropriate authority.
- Members must not proxy-arp on any peering VLANs.
- Members must only respond to ARP requests for addresses which they have been assigned.
- Members must only present one source mac-address on any one physical connection they are connected to Stelia via. (Aggregated LAG ports are considered to be one connection.)
- Each member physical port (or LAG) must peer with the route collector on at least one of the public peering VLANs.
- Each public peering VLAN active on each member port must have a peering with the route collector.
- Members should announce the same set of routes to the collector that would be advertised to a regular peer across Stelia
- Members must ensure that their use of Stelia is not detrimental to the use made by other Members.
- Members must not install ‘sniffers’ or similar devices in an attempt to monitor traffic passing through Stelia.
- Cabling to Stelia racks will only be run by contractors approved by Stelia and always in accordance with the guidelines set by Stelia.
Port and Traffic Requirements
Stelia members must advise Stelia of devices in the path between the Stelia switch and the members Layer3 terminating device, for example media converters, or connections via third party ethernet providers (psuedowires).
All frames forwarded to a particular Stelia port from a member must have the same source mac-address. On no account should BPDUs be forwarded to a Stelia port.
Members must ensure their equipment is configured in such a way that a frame received from a Stelia port is never forwarded back to Stelia.
Member ports are configured as either single VLAN or multi VLAN ports.
Stelia has an assigned range of MAC addresses, so members can use a fixed address if they wish to override a physical interface’s MAC address. This is completely optional, but could be useful to present a consistent MAC address to the exchange e.g. to avoid it changing if a router is replaced.
Find out more about our IX locations here: