Shared 1 Gbps Ethernet
The standard customer handoff uses a shared 1 Gbps port. Port speed is not a dedicated transit commitment and does not promise sustained throughput, route, latency, or uptime.
Documentation ยท Network
Network handoff
The accepted quote turns the public network model into a specific port, addressing method, transfer meter, management path, and customer acceptance check.
Outbound measured by GB
Published pricing bills traffic leaving the customer handoff for the public internet at $0.01 per decimal GB. Inbound internet transfer is not billed under that model.
IPv6 and optional IPv4
An IPv6 /64 is included with the approved standard handoff. IPv4 /29 availability, price, routing, usable addresses, and justification are confirmed in the accepted quote.
Before handoff
Prepare the customer-controlled side.
Helixrack confirms the facility-side port and addressing details. You remain responsible for the system that uses them.
- Patch firmware and disable unused management and application services.
- Configure the host firewall before exposing the production interface.
- Use a separate management interface or approved management path where the configuration supports it.
- Identify the source addresses and protocols needed for customer administration.
- Prepare an out-of-band bootstrap channel; do not send credentials in ordinary email or intake forms.
- Define the test that confirms customer access without treating application health as a facility test.
Illustrative sample
A handoff record separates facts from secrets.
The example values use documentation-only address ranges and reserved identifiers. They do not describe a live network, route, customer, or allocation.
Download sample handoff (.txt)Record: HXR-NET-EXAMPLE-001
Server: SAMPLE-SERVER-01
Port: EXAMPLE-SW / EXAMPLE-PORT
Link: UP at 1 Gbps
IPv6 prefix: 2001:db8:1200::/64
IPv4 example: 192.0.2.0/29
Transfer meter: outbound decimal GB
Customer firewall: customer controlled
Bootstrap secret: delivered out of band
Acceptance: customer path confirmedNot included in the standard handoff
Customer BGP sessions, customer-provided address space, cross-connects, dedicated transit commitments, additional physical ports, private interconnection, or workload-specific DDoS controls require a separate technical and commercial review. Do not assume availability from the public price table.
Network issue report
Email [email protected] with the server identifier, affected interface or address, first observed time with time zone, source and destination, expected result, actual result, and the last known good state. Remove credentials and unrelated payload data.
Need a nonstandard network handoff?
Include the topology goal and routing requirement during intake so the operating team can evaluate it before shipment.