MAINPORT Peer-Exchange

Germany

City: Frankfurt am Main
Website: https://mainport.one/#peer-exchange

About this IXP

Data last updated April 2026

Capacity at this IXP

610 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 MAINPORT Peer-Exchange as shown in PeeringDB in April 2026

Members of this IXP

ASNs (autonomous system numbers) are listed in PeeringDB

In the last 12 months

ASNs left0
New ASNs joined13

Participates in the MANRS IXP program

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

Yes

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: April 2026

View this IXP on PeeringDB

Countries of registration

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.

Germany: 10
Switzerland: 2
United Kingdom: 1

Types of network at this IXP

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

NSP: 8
Content: 2
Educational/Research: 2
Route Server: 1

Members peering at the route server

12 / 13

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

11 / 13

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

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

Member list for MAINPORT Peer-Exchange

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

Name	AS Number	Peering policy	RPKI Enabled
FogNet - iFog GmbH Autonomous system (AS) number: 34927 Type of AS: NSP Peering policy: Open Port speed: 10 Gbps Does this member peer at the route server?: Yes Country of registration: Switzerland Total peering locations for this AS: 52	34927	Open	Yes
handily networks Autonomous system (AS) number: 47526 Type of AS: NSP Peering policy: Open Port speed: 100 Gbps Does this member peer at the route server?: Yes Country of registration: Germany Total peering locations for this AS: 10	47526	Open	Yes
level66.network Autonomous system (AS) number: 56381 Type of AS: NSP Peering policy: Open Port speed: 60 Gbps Does this member peer at the route server?: Yes Country of registration: Germany Total peering locations for this AS: 5	56381	Open	Yes
Lukas Michaels Autonomous system (AS) number: 212864 Type of AS: Educational/Research Peering policy: Open Port speed: 20 Gbps Does this member peer at the route server?: Yes Country of registration: Germany Total peering locations for this AS: 3	212864	Open	No
LWLcom Autonomous system (AS) number: 50629 Type of AS: NSP Peering policy: Selective Port speed: 100 Gbps Does this member peer at the route server?: Yes Country of registration: Germany Total peering locations for this AS: 21	50629	Selective	Yes
MAINPORT Peer-Exchange Route-Servers Autonomous system (AS) number: 50566 Type of AS: Route Server Peering policy: Open Port speed: 20 Gbps Does this member peer at the route server?: No Country of registration: Germany Total peering locations for this AS: 1	50566	Open	No
NUXOA GmbH Autonomous system (AS) number: 51202 Type of AS: NSP Peering policy: Open Port speed: 200 Gbps Does this member peer at the route server?: Yes Country of registration: Germany Total peering locations for this AS: 4	51202	Open	Yes
Openfactory GmbH Autonomous system (AS) number: 58299 Type of AS: NSP Peering policy: Open Speed: Unknown Does this member peer at the route server?: Yes Country of registration: Switzerland Total peering locations for this AS: 22	58299	Open	Yes
PathConnect Autonomous system (AS) number: 47536 Type of AS: Content Peering policy: Open Speed: Unknown Does this member peer at the route server?: Yes Country of registration: Germany Total peering locations for this AS: 6	47536	Open	Yes
ROUTE64.ORG Autonomous system (AS) number: 212895 Type of AS: NSP Peering policy: Open Speed: Unknown Does this member peer at the route server?: Yes Country of registration: Germany Total peering locations for this AS: 26	212895	Open	Yes
TELE90 Telecom GmbH Autonomous system (AS) number: 215787 Type of AS: Content Peering policy: Open Port speed: 100 Gbps Does this member peer at the route server?: Yes Country of registration: Germany Total peering locations for this AS: 6	215787	Open	Yes
Tilman Schaefers Autonomous system (AS) number: 208814 Type of AS: Educational/Research Peering policy: Open Speed: Unknown Does this member peer at the route server?: Yes Country of registration: Germany Total peering locations for this AS: 6	208814	Open	Yes
vServer.site Autonomous system (AS) number: 56382 Type of AS: NSP Peering policy: Unknown Speed: Unknown Does this member peer at the route server?: Yes Country of registration: United Kingdom Total peering locations for this AS: 12	56382	Unknown	Yes