AS215828 network, peering, and operational evidence
Public routing data, PoP footprint, IX presence, upstream diversity, contacts, and tooling for engineers evaluating TMW Global Networks.
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.
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.
Frankfurt
Primary EU edge and scrubbing metro
Amsterdam
EU peering and exchange aggregation
North Kansas City
US central edge and emergency onboarding
Singapore
APAC edge and remote protection handoff
Frankfurt, Germany
Primary EU edge and scrubbing metro
Amsterdam, Netherlands
EU peering and exchange aggregation
North Kansas City, United States
US central edge and emergency onboarding
Singapore, Singapore
APAC edge and remote protection handoff
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.
AS51202
NUXOA GmbH
AS1299
Arelion
AS62255
BiMajLink d.o.o.
AS34927
iFog GmbH
AS393577
Tritan Development
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
IX presence
Public exchange ports.
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.