A Swiss dedicated configuration centred on a listed 100 Gbps port. Transit 100 brings a Xeon Gold foundation and configurable memory and storage to demanding, authorised data-distribution workloads.
A dedicated configuration built around a 100 Gbps port and unmetered traffic. Dual Xeon Gold 6134 processors, 128 GB of DDR4 memory and a 1 TB SSD provide the compute and storage allocation.
Compare the listed specifications and base prices. Final availability, delivery and applicable tax are confirmed on your quote. Illustrations are conceptual.
Understand what makes this service family useful.
The base configuration lists the high-speed port explicitly. Plan the application and storage pipeline around that interface without assuming an end-to-end rate.
The CPU and memory specifications remain visible beside the network. Account for request processing, encryption and application work when sizing the environment.
Select supported primary or additional SSD capacity for served content and active data. Capacity and achievable read rates remain different considerations.
Transit 100 lists unmetered traffic. Review the server, IP and software choices as part of the same network-intensive deployment.
Prepare a Swiss origin for content you are authorised to distribute, with a tested application and storage design.
Serve substantial exports or research datasets to capable receivers while controlling access to private material.
Choose this class of port when workload measurement justifies it and the rest of the stack can support the traffic.
Estimate concurrent transfers, request sizes and the amount of data the application must read or generate. Then test the storage and software path with representative traffic. A high-speed port can be valuable, but it cannot make a receiver or a slow application consume data faster than they are able.
Transit 100 lists SSD storage in its base configuration. Choose additional capacity where the project requires it and define how the data is organised and recovered. Do not infer NVMe storage or a particular disk layout from the network tier; read the actual hardware and selected options.
A distribution service can have a public data path and a tightly controlled management path. Restrict administrator interfaces, protect publishing credentials and review what your applications log. Keep backups for content and configuration so the service can be rebuilt without exposing private access.
The Transit 100 plan lists a physical server, unmetered traffic and five IPs in a /29 allocation. Confirm any IPv6 subnet, baseline protection and recovery console before delivery. Dedicated-capacity commitments, burst use and traffic telemetry need separate operating terms. Keep your monitoring and application benchmark requirements part of the technical brief.
Available choices depend on the selected configuration. See included selections and option prices in the configurator.
Specific answers for this service family.
It describes the listed port specification. Actual throughput depends on storage, CPU, application behaviour, protocol, route and the receiving side.
The Transit 100 base specification lists SSD storage. Review the plan and option labels directly rather than assuming a technology from the network tier.
The configurator includes RAM and disk choices. Check the resulting capacity and price in the final summary and choose them for a measured workload.
Only if your network design requires it. Additional address allocations are optional and should be selected separately from port speed.
Test representative transfers, monitor resource limits, verify receiver performance and keep a rollback plan. Confirm content rights and protect administrative access.
It lists a 100 Gbps port and unmetered traffic. Dedicated-throughput commitments, fair use and burst handling require operator confirmation and documented terms.
The plan lists five IPs in a /29 allocation, with optional additional blocks. Confirm IPv6 and usable allocation before designing the network.
Confirm the monitoring interface, available metrics and retention for the selected service. Include application-side measurements in your monitoring plan.
Confirm root or administrator credentials, secure IPMI or equivalent recovery access, and the baseline protection scope before a real order.
Estimate the data your project moves and understand why a larger port is only one part of network performance.
Read the guideBuild a repeatable transfer model using payload volume, delivery windows and round-trip time, then test it without confusing a port label with useful throughput.
Read the guideTranslate large port classes into storage, CPU, concurrency and operational questions before selecting a high-volume distribution configuration.
Read the guideChoose your resources. Keep control of your identity.