Our network.Perfectly connected.
AS215828 connects Europe, North America, and Asia. Explore our locations, upstreams, and open peering.
Links a network engineer will actually check.
These are public systems of record and operational tools, not marketing badges. Use them to verify routing, peering, facilities, contact roles, and service health.

- Autonomous System
- AS215828
- AS-SET
- AS-TMW
- RIR
- RIPE NCC
- Protocol support
- IPv4 + IPv6 unicast
- public facility metros
- 6
- listed IX ports
- 17
Links a network engineer will actually check.
These are public systems of record and operational tools, not marketing badges. Use them to verify routing, peering, facilities, contact roles, and service health.
Where we connect.
Our public locations for transit, DDoS protection, and peering.
Route validation
Prefixes require IRR route objects, ROAs where possible, max-prefix limits, and LOA checks before production announcement.
Where we connect.
Our public locations for transit, DDoS protection, and peering.
Frankfurt
Primary EU edge and scrubbing metro
- Digital Realty FRA1-27
- Equinix FR7
- firstcolo FRA4
- maincubes FRA01
AmsterdamNew
EU peering and exchange aggregation
- Qupra DC
- NIKHEF
Zurich
DACH backup edge and CHIX presence
- CHIX-CH
RoubaixNew
France edge metro
- OVHcloud RBX
North Kansas City
US central edge and emergency onboarding
- 1530 SWIFT - NOCIX
Singapore
APAC edge and remote protection handoff
- Racks Central
Upstream connectivity
Publicly observed upstreams for AS215828. IPv4 and IPv6 supported.
Open peering
Exchange traffic with AS215828. Our policy and peering contacts are public.
- Policy
- Open
- Multiple locations
- Preferred
- Traffic ratio
- No requirement
- Contract
- Not required for public peering
- Route server
- Accepted where supported
- Address families
- IPv4 and IPv6
Route validation
Prefixes require IRR route objects, ROAs where possible, max-prefix limits, and LOA checks before production announcement.Operational visibility
Looking Glass, status page, BGP community controls, and customer dashboards expose the same state the NOC uses.Abuse and NOC contacts
Abuse, NOC, maintenance, and peering roles are published for escalation and interconnection coordination.
Public exchange ports.
| Exchange | Metro | Port | IPv4 / IPv6 |
|---|---|---|---|
| FogIXP Frankfurt | Frankfurt | 20G | 185.0.30.572001:7f8:11c:1:0:21:5828:1 |
| NL-ix | Amsterdam | 10G | 193.239.119.1192001:7f8:13::a521:5828:2 |
| PITER-IX Frankfurt | Frankfurt | 10G | 31.44.186.1572001:7f8:109::3:4b14:1 |
| Speed-IX | Amsterdam | 10G | 185.1.222.202001:7f8:b7::a521:5828:1 |
| INTERIX | Amsterdam | 10G | 185.1.184.2142001:7f8:134::d5 |
| Kawaii IX AMS | Amsterdam | 10G | 195.60.92.882602:f93b:1a35:1311::88 |
| Frys-IX | Amsterdam | 10G | 185.1.160.1172001:7f8:10f::3:4b14:117 |
| nine | Amsterdam | 10G | 185.1.14.1912001:7f8:12e::21:5828:1 |
| frankonIX | Nuremberg | 1G | 193.34.203.2032001:7f8:15b:1::c122:cbcb |
| CHIX-CH | Zurich | 1G | 185.1.59.2022001:7f8:cc:333::202 |
| FogIXP | Remote | 20G | 185.1.147.1962001:7f8:ca:1:0:21:5828:1 |
| TMW-iX | Frankfurt | 10G | -2a0e:b107:2888:0:1:21:5828:1 |
| BGP.Exchange - Auckland | Auckland | 1G | -2a0e:8f01:1000:20::102 |
| EVIX | Remote | 1G | 206.81.104.602602:fed2:fff:ffff::60 |
| HN Internet Exchange (Main) | Kansas City | 1G | -2a0f:85c1:363:1:21:5828:0:1 |
| BGP.Exchange - Singapore | Singapore | 1G | -2a0e:8f01:1000:7::164 |
| F4IX MCI | Kansas City | 100M | 149.112.75.372602:fa3d:f4:1::37 |
Book a session or routing review.
Send ASN, peering LAN addresses, max-prefix requirements, and intended route set. The NOC can validate policy before turn-up.