产品体系
可以直接部署的网络原语。
可以单独采购，也可以组合成有冗余的路径。可用性和商务条款按机房确认。
DECISION FRAMEWORK
Start with the traffic primitive.
Each product answers a different network question. Combine them only after the handoff and failure mode are clear.
COMPARE
Choose by the job the link must do.
| Product | Primary job | Common handoff | Operating signal |
|---|---|---|---|
| Transit IP | Internet exit and route control | BGP session at a facility | Routes, prefixes, loss |
| Dedicated Internet | Managed site connectivity | Symmetric last-mile circuit | Availability, latency |
| DDoS Protect | Hostile traffic response | Protected IP space / diversion | Events, mitigation time |
| Cloud Connect | Private workload path | Virtual circuit at a facility | Path, VLAN, throughput |
| Peering / IX | Shorter exchange path | IX port or private VLAN | AS path, RTT, volume |
DELIVERY MODEL
Every order ends with an operating handoff.
A product is complete when the team knows who owns the port, what is monitored and what happens next.
Map requirement
Sites, traffic shape, regions, redundancy and launch date.
Check facility
Confirm product, port, cross-connect and service boundary.
Test path
Configure routing, monitor signals and verify acceptance criteria.
Run the link
Use maintenance notices, NOC escalation and data sheets.
PRODUCT QUESTIONS
Review the operating detail before the quote.
Can I combine products?
Yes. Transit, cloud, peering and DDoS can be composed after the facility and failure mode are confirmed.
Are port bands guaranteed?
Port options are a starting point. Final capacity, optics and delivery date are validated per facility.
What comes with a handoff?
Every service names the routing method, monitoring signals, maintenance path and escalation owner.
How do we request pricing?
Submit sites, bandwidth, regions and timeline. The team returns a practical technical and commercial next step.