Starlink PNI · L2 and L3 variants
We connect sites to the organisation's network through Starlink PNI – a private service in two variants: PNI L2 (Ethernet) and PNI L3 (IP). Traffic from the terminals reaches the organisation's network through handover points, bypassing the public Internet. Traffic separation, handover points, quality parameters and support are defined for the specific service variant.
How Starlink PNI works
A Starlink kit on site, transport over LEO satellites to a Starlink gateway and over fibre to a Point of Presence. From there, a dedicated handover point passes traffic to the organisation's network – in the PNI L2 (Ethernet) or PNI L3 (IP) variant. Where it simplifies operations, we run SD-WAN on top of the service. Parameters and scope are defined in the design and the contract.
Service features
The service carries the organisation's VLANs and IP traffic under rules defined in the contract, while Starlink provides reach where there are no terrestrial links or an independent path is needed.
VLAN support, including QinQ – the service carries the organisation's segmentation between sites.
Traffic classes for voice, video and control systems, consistent along the whole path – within the scope agreed in the design.
Availability, response times and escalation rules defined in the contract.
The service can act as the underlay for an MPLS service the organisation already runs.
An MTU larger than the standard 1500 bytes lets the customer's underlay network be carried without fragmentation. The value is set for the service variant.
Our network operations centres (NOC) monitor the service and handle tickets around the clock.
Variants and scope
Point-to-point and multipoint services, VLAN and QinQ, transparent transport between sites and the organisation's network.
Routing, VRF separation and integration with the organisation's existing VPN or MPLS.
Throughput, latency, jitter, MTU and path switchover tests, documented in an acceptance report.
Architecture
Starlink PNI L2/L3 terminates at controlled handover points – two independent, geographically distributed and fully redundant locally – with traffic separation and QoS policy. On site, redundancy is complemented by a second terminal or a backup link that we add through SD-WAN.
Two independent, geographically distributed handover points
A single shared handover would be a single point of failure. That is why we have two independent handover points, geographically distributed, each fully redundant locally. When the organisation's network is connected to both handover points, the failure of one of them – including the whole facility that hosts it – does not stop the service. Connection to both points, switchover times and the scope of redundancy depend on the service variant and the organisation's configuration – they are defined in the design and the contract and verified in acceptance tests.
Responsibilities
Boundaries of responsibility are written into the design and the contract for the specific service variant. A typical split is shown below.
Terminal and satellite service: space segment, ground stations and the provider network up to the handover point.
Service design, configuration, handover points and delivery of traffic to the organisation's network, monitoring and ticket handling in our 24/7 NOC, within the contract.
Internal network, devices and applications, security policy and – unless agreed otherwise – traffic encryption.
Private transport defines the path and traffic separation. Encryption requirements are agreed separately, in line with the customer's security policy – a private path does not automatically mean end-to-end encryption.
Security through discretion
Topology, node locations, configurations and link parameters make attacks easier in the wrong hands. On this website we describe capabilities and models; details are shared only within a project and under a non-disclosure agreement.
PNI L2 carries Ethernet frames: the organisation's VLANs, including QinQ, reach its network unchanged. PNI L3 carries IP traffic, with routing and VRF separation. The variant is chosen to match the organisation's network architecture and application requirements.
With Starlink PNI, traffic from the terminals reaches the organisation's network through a private handover point, without crossing the public Internet. A VPN tunnels traffic across a public network. Differences in routing, SLA and security are assessed for the specific service variant.
Private transport defines the path and traffic separation, but it does not automatically mean end-to-end encryption. Encryption requirements are agreed separately, in line with the organisation's security policy.
The service terminates at two independent, geographically distributed handover points, each fully redundant locally. Continuity when one of them fails requires the organisation's network to be connected to both – this is agreed in the design and the contract. On site, redundancy is complemented by a second terminal or a backup link added through SD-WAN. Switchover times are measured in acceptance tests rather than assumed.
Yes. The service has an SLA – parameters, availability, response times and escalation rules are defined in the contract. It is supervised by our network operations centres (NOC 24/7).
Yes, depending on the design: in the PNI L2 variant (for example, VLAN handover or an underlay for the customer's MPLS) or PNI L3 (routing and VRF separation), agreed with the customer's network team.
Describe your sites, separation and redundancy requirements and where the service should meet your organisation's network. We will propose a PNI L2 or L3 variant and the service scope.
