Back to home
Cloudflare Magic Transit

DDoS protection with Cloudflare Magic Transit for attacks that overwhelm ordinary networks.

Amherst Systems positions Cloudflare Magic Transit as network-layer DDoS protection for public-facing infrastructure. The service places Cloudflare's globally distributed anycast network in front of protected IP space so attack traffic is absorbed and filtered before it can saturate links to your infrastructure.

That matters during large volumetric events because the traffic is spread across a network with more than 405 Tbps of aggregate capacity instead of relying on a single provider edge or appliance to survive the flood.

INTERNET
Cloudflare
CLOUDFLARE
Your Server
Malicious (Blocked)
Legitimate (Passed)
405+

Tbps of global network capacity standing behind the protection model.

L3/L4

Network-layer scrubbing before attack traffic can saturate your origin links.

330+

Cities on Cloudflare's network, spreading attack load across a global edge.

What Cloudflare Magic Transit actually does

Magic Transit protects public-facing network infrastructure at Layer 3 and Layer 4. Instead of waiting for an attack to arrive at your origin router, Cloudflare absorbs inbound traffic across its edge and applies mitigation upstream, where the bandwidth headroom exists.

In practical terms, that means floods aimed at exhausting transit, routing equipment, or server interfaces are handled before they ever become your problem. Legitimate traffic continues toward your servers while malicious packets are identified and dropped at scale.

Anycast Absorption

Traffic is distributed across Cloudflare's globally routed edge instead of being forced into a single upstream path.

Upstream Mitigation

Floods are filtered before they hit your routers, firewalls, or server NICs, which is where large attacks cause real damage.

Headroom for Volume

More than 405 Tbps of network capacity means protection is backed by the network itself, not just a box in front of your rack.

Clean Traffic Forwarding

Legitimate packets keep moving toward your infrastructure while malicious traffic is dropped at the edge.

How the traffic path changes during an attack

Magic Transit works because the protection sits in the network path itself. The service changes where traffic is absorbed, where it is filtered, and what eventually reaches your infrastructure.

01

Traffic is pulled onto Cloudflare's edge

Magic Transit advertises protected IP space across Cloudflare's anycast network, so inbound traffic lands on Cloudflare first instead of your origin circuit.

02

Attack traffic is identified and filtered

Volumetric floods, spoofed packets, and other Layer 3 and Layer 4 abuse are scrubbed across the network before they can exhaust bandwidth upstream.

03

Only legitimate packets continue

Clean traffic is passed on to your servers, keeping applications reachable even while a large attack is still being absorbed in the background.

Why Amherst Systems keeps this on a dedicated product page

The short version belongs on the home page: Cloudflare Magic Transit helps keep infrastructure online during large attacks. The longer version is that network-layer DDoS protection only works when the mitigation capacity sits upstream and globally distributed, which is exactly what this service is designed to do.

Protects the path to your servers, not just the application running on them.
Uses Cloudflare's global edge to spread and scrub volumetric floods at scale.
Keeps the existing Amherst Systems site visual language by reusing the same traffic diagram and card system.

DDoS protection FAQ

Short answers about Amherst Systems DDoS protection and Cloudflare Magic Transit.

What does Amherst Systems DDoS protection cover?

Amherst Systems DDoS protection is built around Cloudflare Magic Transit and is focused on protecting network infrastructure against Layer 3 and Layer 4 attacks.

How does Magic Transit help during a volumetric attack?

Magic Transit places Cloudflare's anycast edge in front of protected IP space so attack traffic can be absorbed and scrubbed upstream before it saturates links to the origin infrastructure.

Is this only application security?

No. The Amherst Systems DDoS protection page focuses on network-layer protection for public-facing infrastructure, not only application-layer filtering.