IX Liverpool - Baltic Bubble Data Centre

United Kingdom of Great Britain and Northern Ireland

Ville
Liverpool

About this IXP

Data last updated Novembre 2025

Capacity at this IXP

42 Gbps

Cumulative port speeds of all IXP members. This shows the potential maximum traffic that can be exchanged at this IXP at one time.

Membership and capacity

The size and strength of an IXP is determined by a combination of how many members it has, and the total capacity. Larger networks tend to bring more capacity, which can benefit all members.

Data for IX Liverpool - Baltic Bubble Data Centre as shown in PeeringDB in Novembre 2025

2021202220232024202542 42 42 43 43 43 3 3 3 4 4 4
CapacityMembersCapacity (Gbps)Members

Members of this IXP

3

ASNs (autonomous system numbers) are listed in PeeringDB

In the last 12 months

  • ASNs left0
  • New ASNs joined0

Participates in the MANRS IXP program

No

IXPs that join this voluntary program apply a framework of enhanced routing security in peering. It signals an extra commitment to responsible Internet stewardship.

Source: MANRS

RIPE Atlas anchor

No

Organizations that run IXPs can host anchors to measure Internet connectivity and traffic. An anchor is a large capacity probe often used by IXPs.

Source: RIPEStat

Member information

Last sync from PeeringDB: Novembre 2025

View this IXP on PeeringDB

Pays d’enregistrement

A summary of member registrations by country. An IXP with a mixture of international and near-neighbor members can indicate that an IXP is influential, or acts as a hub within its region or sub-region.

  • Royaume-Uni: 3

Types of network at this IXP

The mix of members is an indication of a strength or focus of an IXP.

  • Cable/DSL/ISP: 2
  • Enterprise: 1

Members peering at the route server

3 / 3

The route server is a central hub that makes it easier for all networks to peer without having to create individual agreements with other members.

Members using RPKI

2 / 3

members at this IXP use Resource Public Key Infrastructure (RPKI), a security measure that helps ensure traffic is routed correctly. A member is counted as using RPKI if they have at least one valid ROA.

Peering policies of IXP members

UnknownNoOpenRestrictiveSelective

Members of an IXP can choose how they peer with others. The Internet Society encourages open policies where possible.

Member list for IX Liverpool - Baltic Bubble Data Centre

This list uses the data available in PeeringDB, which is based on self-reported data, and was last updated in Pulse Novembre 2025

Nom AS Number Peering policy RPKI Enabled
Baltic Broadband
  • Autonomous system (AS) number: 203421
  • Type of AS: Cable/DSL/ISP
  • Peering policy: Unknown
  • Port speed: 40 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: Royaume-Uni
  • Total peering locations for this AS: 6
203421 Unknown Yes
Internet of Things Limited
  • Autonomous system (AS) number: 202488
  • Type of AS: Enterprise
  • Peering policy: Unknown
  • Port speed: 1 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: Royaume-Uni
  • Total peering locations for this AS: 2
202488 Unknown No
Zycomm Electronics Limited
  • Autonomous system (AS) number: 39875
  • Type of AS: Cable/DSL/ISP
  • Peering policy: Unknown
  • Port speed: 1 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: Royaume-Uni
  • Total peering locations for this AS: 6
39875 Unknown Yes