TMWTMW Global NetworksTMW Global Networks
Network

AS215828 network, peering, and operational evidence

Public routing data, PoP footprint, IX presence, upstream diversity, contacts, and tooling for engineers evaluating TMW Global Networks.

Open Looking GlassBGP communities

Autonomous System

AS215828

AS-SET

AS-TMW

RIR

RIPE NCC

Protocol support

IPv4 + IPv6 unicast

Peering policy

Open, no traffic ratio requirement

Public validation

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.

PeeringDBPublic peering profile, facilities, policy, and NOC contactsbgp.toolsGlobal routing, originated prefixes, upstreams, peers, and RPKIRIPE DBAuthoritative aut-num object for AS215828Looking GlassBGP route lookup, ping, traceroute, and advertisementsStatus PageLive service and network component availability

PoP map

Published metros and facilities

TMW publishes its active interconnection facilities in PeeringDB. The map below focuses on the public footprint used for transit, protected transit, tunnel handoff, and peering.

4
public facility metros
17
listed IX ports
6
public upstreams
AS-TMW
exported AS-SET
FrankfurtPrimary EU edge and scrubbing metroAmsterdam · NewEU peering and exchange aggregationZurichDACH backup edge and CHIX presenceNorth Kansas CityUS central edge and emergency onboardingSingaporeAPAC edge and remote protection handoff

Frankfurt, Germany

Primary EU edge and scrubbing metro

Digital Realty FRA1-27Equinix FR7firstcolo FRA4maincubes FRA01
New

Amsterdam, Netherlands

EU peering and exchange aggregation

Qupra DCNIKHEF

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

Upstreams

Multi-homed by design.

Public route collectors currently observe these upstreams for AS215828. Customer prefixes are accepted only after ownership, IRR, and RPKI checks.

AS1299

Arelion

IPv4 + IPv6

AS51202

NUXOA GmbH

IPv4 + IPv6

AS62255

BiMajLink d.o.o.

IPv4 + IPv6

AS6939

Hurricane Electric LLC

IPv4 + IPv6

AS34927

iFog GmbH

IPv4 + IPv6

AS199310

XIN BING XIAN

IPv4 + IPv6

Peering policy

Open policy, clean requirements.

TMW peers openly where both networks can exchange traffic cleanly. Public policy points are kept simple so turn-up can be handled by engineers, not procurement loops.

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

IX presence

Public exchange ports.

Verify in bgp.tools
ExchangeMetroPortIPv4 / IPv6
FogIXP FrankfurtFrankfurt20G185.0.30.57 / 2001:7f8:11c:1:0:21:5828:1
NL-ixAmsterdam10G193.239.119.119 / 2001:7f8:13::a521:5828:2
PITER-IX FrankfurtFrankfurt10G31.44.186.157 / 2001:7f8:109::3:4b14:1
Speed-IXAmsterdam10G185.1.222.20 / 2001:7f8:b7::a521:5828:1
INTERIXAmsterdam10G185.1.184.214 / 2001:7f8:134::d5
Kawaii IX AMSAmsterdam10G195.60.92.88 / 2602:f93b:1a35:1311::88
Frys-IXAmsterdam10G185.1.160.117 / 2001:7f8:10f::3:4b14:117
nineAmsterdam10G185.1.14.191 / 2001:7f8:12e::21:5828:1
frankonIXNuremberg1G193.34.203.203 / 2001:7f8:15b:1::c122:cbcb
CHIX-CHZurich1G185.1.59.202 / 2001:7f8:cc:333::202
FogIXPRemote20G185.1.147.196 / 2001: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.60 / 2602: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.37 / 2602:fa3d:f4:1::37

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
TMW Global Networks

Carrier-grade DDoS protection, IP transit, and hosting for networks that need direct operational support.

All systems operational

Hosting

  • Dedicated Servers
  • Cloud VPS
  • KVM Server
  • IP-Transit
  • Network
  • BGP Communities
  • Colocation

Services

  • TMW Shield
  • TMW CDN / Proxy
  • On-Prem
  • Filter Profiles
  • Status page

Guides

  • Guides
  • FAQ
  • Attack Reports
  • Case Studies
  • What is a Cloud Server?
  • What is a VPS?
  • What is DDoS Protection?
  • TCP & UDP Ports Explained
  • TCP/IP Explained

Company

  • Solutions
  • About
  • DDoS Frankfurt
  • abuse@t-w.dev
  • noc@t-w.dev
  • Contact
  • Under Attack?

© 2026 TMW Global Networks. All rights reserved.

ImprintPrivacyTermsTMW Shield Terms