Protected IP Transit

Protected IP Transit

Full reachability to the entire internet over BGP, on IPv4 and IPv6, with redundant upstreams, DDoS protection and an SLA you can build on.

Transit that just reaches everything

We carry your traffic to the whole internet over redundant upstreams, hand you full IPv4 and IPv6 routes, and keep the link protected and measured against a clear SLA.

Service parameters

Routing tableFull DFZ (IPv4 + IPv6)
UpstreamsRedundant Tier-1 / regional blend
Port speeds1G / 10G / 100G
BillingPer Gbps: 95th pct / CDR

What's included

Full IPv4 and IPv6 routing tables over BGP
Redundant, diverse upstream capacity
DDoS protection filtering included
99.9% availability SLA with 24/7 NOC
RPKI-validated, filtered route announcements
Scalable bandwidth, burst above commit

Transit, peering and remote IXP in one place

Most operators run transit alongside peering: peering keeps nearby traffic cheap and fast, while transit guarantees the rest of the internet stays reachable and redundant. We deliver both from the same network, together with Anti-DDoS protection filtering the link.

Why our transit

Built for reachability and resilience

Full reachability

We announce your prefixes to the world and hand you the complete DFZ, so every network on the internet is reachable, including the ones you do not peer with.

Redundant upstreams

Traffic is carried over a blend of multiple upstream providers with diverse paths, so a single carrier issue does not take your network offline.

DDoS protection

Volumetric attacks are filtered on our side before they reach your infrastructure, keeping the transit link and your services stable.

SLA & 24/7 NOC

Backed by a 99.9% availability SLA and a 24/7 NOC, with BGP support, route filtering and RPKI for a clean, predictable service.

Benefits

What you get with AS202520 transit

One BGP session, the entire internet reachable
Pairs with peering as a resilient safety net
Lower, predictable cost per delivered Gbps
IPv4 and IPv6 from day one
Scales smoothly as your traffic grows
Carrier-grade routing hygiene (filtering, RPKI)

Need transit you can rely on?

Tell us your traffic profile and target locations, and we will put together a Protected IP Transit quote.

Frequently asked questions

What is Protected IP Transit?

Protected IP Transit is a service that gives your network full reachability to the entire internet while shielding the link from DDoS attacks. As your transit provider we announce your prefixes to the rest of the world and hand you the full routing table (DFZ) in IPv4 and IPv6, with DDoS filtering on our side. Unlike peering, which exchanges traffic only with selected networks, transit reaches every network, including those you do not peer with directly.

How is IP Transit different from peering and remote IXP access?

Peering is direct traffic exchange with specific networks (usually not billed by volume), and remote IXP access lets you join Internet Exchanges without your own physical presence. Transit is complementary: it provides full internet reachability and acts as a safety net for traffic that peering does not cover. A mature operator usually combines both: peering for cheap, nearby traffic and transit for full reachability and redundancy.

Do you provide both IPv4 and IPv6?

Yes. We hand over full IPv4 and IPv6 routing tables over BGP. We can also provide address space for the service or announce your own prefixes (PI/PA) after verifying authorization, following good practice (route filtering, RPKI).

How does billing and SLA work?

Billing is based on contracted bandwidth in Gbps, typically on a 95th-percentile or committed-rate (CDR) model with bursting allowed. The service is covered by an SLA with 99.9% availability and 24/7 NOC support. We tailor the exact parameters and pricing to your network's profile and scale.

Is DDoS protection included?

Yes, transit links are protected by DDoS filtering on our side. Volumetric attacks are mitigated before they reach your infrastructure, keeping your network stable. We agree the exact scope and thresholds when the service is configured.