// IP TRANSIT
IP connectivity for ISPs, WISPs, hosting providers and businesses. Run routing with your ASN, bring your prefixes through AS6517, or receive IPv4 and IPv6 addresses from LAKENETWORKS.
Available throughout the Milan Caldera campus, on hosted infrastructure or together with business connectivity. Port and service profiles are available up to 10 Gbps and are defined in the quotation.
// CONFIGURATIONS
You do not need your own ASN or prefixes. Choose the mode that fits your infrastructure, then we define delivery, capacity and addressing in the quotation.
For networks with an ASN
Establish an eBGP session with AS6517 and manage your network announcements and routing directly.
For customers who already own IP space
We announce your prefixes from AS6517 and route them to the agreed handoff. You do not need to operate a BGP session.
For customers without an ASN or prefixes
We provide the IPv4 and IPv6 space you need and route it over the connection, without BGP on the customer side.
// WHO IT IS FOR
From an upstream for an operator to a routed handoff for a business site, the service is configured around who manages announcements and where traffic needs to arrive.
IP upstream connectivity for networks, POPs and customers, using your ASN or routing managed by LAKENETWORKS.
Connectivity and addressing for servers, clusters and hosted services, using your own IP space or ranges supplied by us.
Public addresses and routing for offices, datacenters and business services, without an ASN or internal BGP operations.
Transit for platforms, appliances and environments that need a dedicated IP handoff and an agreed routing policy.
// TRANSIT AND PEERING
IP Transit uses the AS6517 network to reach the Internet. We also maintain direct peering sessions with networks such as Cloudflare, OVHcloud, Hetzner and other networks present at the IXPs. Peering complements transit with direct paths when the destination is available at the exchange.
Examples of networks reached through direct peering include Fastweb, Aruba, Akamai, Netflix, Meta (Facebook), Fastly, ByteDance and Sky Italia, among many others.
See the AS6517 networkDirect sessions with networks present at IXPs can provide a shorter path. Transit remains available for destinations without a peering route.
Announcements pass the IRR, RPKI and bogon filters already applied to AS6517 sessions.
// DELIVERY
The handoff location determines the interconnection. We check availability and capacity before preparing the quotation.
The service is available throughout the Milan Caldera campus through a cross-connect or VLAN, or directly to servers and devices hosted on our infrastructure.
IP Transit and addressing can be delivered together with FTTH, FTTC, FWA, FTTO or dedicated fibre, subject to coverage.
See business connectivity// BGP POLICY
Downstream sessions apply automatic checks before accepting a route. You do not need to request manual prefix allowlisting: when IRR, RPKI and the other checks are valid, the announcement is accepted according to the session policy. Communities control export and prepending.
See BGP policy and communities// DDoS PROTECTION
IP Transit is also available without DDoS protection. If you add it, protection is quoted separately and the selected mode affects the traffic path.
Traffic keeps its normal path outside mitigation events. It is the first option to consider for delivery in Italy when a more direct route matters.
Traffic always passes through the scrubbing platform in Germany. Mitigation remains permanent, but the path can be longer and add latency.
// QUOTATION
You do not need a complete project. Tell us where you need the handoff, how you want to manage addressing and how much traffic you expect.
Describe the handoff you need. We will reply with a configuration and quotation that fit the infrastructure.
TECHNICAL INFORMATION
No. You need an ASN if you want to operate a BGP session and announce your prefixes directly. Alternatively, we can announce your addresses through AS6517 or provide LAKENETWORKS IP space with a routed handoff.
Yes. With BYOIP we announce your prefixes from AS6517 and route them to your infrastructure. We verify ownership and the required authorisations before activation.
Yes. We can deliver the service together with FTTH, FTTC, FWA, FTTO or dedicated fibre, subject to coverage and the technical characteristics available at the site.
An IP Tunnel carries addresses over GRE or WireGuard on an existing Internet connection. IP Transit is delivered directly to your network, hosted infrastructure or together with the site connectivity.
You can activate IP Transit without DDoS protection. If needed, DDoS Sensor and DDoS Always-On are available as separately quoted options. With Sensor, traffic normally keeps its regular path. Always-On permanently uses the scrubbing platform in Germany and can add latency.
No. Peering reaches networks present at the exchanges directly, while transit provides reachability to the rest of the Internet. Both paths can coexist in the same BGP configuration.
Sessions apply automatic filters for IRR, RPKI, ASN and address bogons, prefix length and authorised prefixes. You do not need to request manual allowlisting for each prefix: the announcement is accepted when it passes the required checks. IRR data is updated every 6 hours.
Yes. With a BGP session you can use the documented AS6517 communities to control export and announcement prepending. The desired policy is defined during configuration.
The standard configuration provides the Full Routing Table (FRT). If your router or project needs a simpler setup, we can provide a default route on request.
We can offer profiles up to 10 Gbps. For example, a 10G port can carry a 1 Gbps profile, with burst considered as part of the agreed configuration.
We prepare a quotation based on the port, requested bandwidth profile, any burst, handoff location, routing mode and additional options.
Do you only need to carry addresses over an existing connection?
See IP Tunnels