AS215828 · Network

Our network. Directly connected.

AS215828 connects Europe, North America, and Asia. Explore our locations, upstreams, and open peering.

Open Looking GlassBGP communities
Router ports with connected fibre cables and status lights
A look at our router.
Autonomous System
AS215828
AS-SET
AS-TMW
RIR
RIPE NCC
Protocol support
IPv4 + IPv6 unicast
public facility metros
5

Where we connect.

Our public locations for transit, DDoS protection, and peering.

  • Frankfurt

    Germany

    Primary EU edge and scrubbing metro

    Digital Realty FRA1-27 · Equinix FR7 · firstcolo FRA4 · maincubes FRA01

  • Amsterdam

    Netherlands

    EU peering and exchange aggregation

    Qupra DC · NIKHEF

  • Zurich

    Switzerland

    DACH backup edge and CHIX presence

    CHIX-CH

  • North Kansas City

    United States

    US central edge and emergency onboarding

    1530 SWIFT - NOCIX

  • Singapore

    Singapore

    APAC edge and remote protection handoff

    Racks Central

Upstream connectivity

Publicly observed upstreams for AS215828. IPv4 and IPv6 supported.

  • ArelionAS1299
  • NUXOA GmbHAS51202
  • BiMajLink d.o.o.AS62255
  • Hurricane Electric LLCAS6939
  • iFog GmbHAS34927
  • XIN BING XIANAS199310

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
Peering policypeering@t-w.dev

Public exchange ports. (17)

Public exchange ports.
ExchangeMetroPortIPv4 / IPv6
FogIXP FrankfurtFrankfurt20G185.0.30.572001:7f8:11c:1:0:21:5828:1
NL-ixAmsterdam10G193.239.119.1192001:7f8:13::a521:5828:2
PITER-IX FrankfurtFrankfurt10G31.44.186.1572001:7f8:109::3:4b14:1
Speed-IXAmsterdam10G185.1.222.202001:7f8:b7::a521:5828:1
INTERIXAmsterdam10G185.1.184.2142001:7f8:134::d5
Kawaii IX AMSAmsterdam10G195.60.92.882602:f93b:1a35:1311::88
Frys-IXAmsterdam10G185.1.160.1172001:7f8:10f::3:4b14:117
nineAmsterdam10G185.1.14.1912001:7f8:12e::21:5828:1
frankonIXNuremberg1G193.34.203.2032001:7f8:15b:1::c122:cbcb
CHIX-CHZurich1G185.1.59.2022001:7f8:cc:333::202
FogIXPRemote20G185.1.147.1962001:7f8:ca:1:0:21:5828:1
TMW-iXFrankfurt10G-2a0e:b107:2888:0:1:21:5828:1
BGP.Exchange - AucklandAuckland1G-2a0e:8f01:1000:20::102
EVIXRemote1G206.81.104.602602:fed2:fff:ffff::60
HN Internet Exchange (Main)Kansas City1G-2a0f:85c1:363:1:21:5828:0:1
BGP.Exchange - SingaporeSingapore1G-2a0e:8f01:1000:7::164
F4IX MCIKansas City100M149.112.75.372602:fa3d:f4:1::37
Verify in bgp.tools
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.

Need 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.

Contact NOC