Network connections
Internet routes and network equipment carry traffic between users, upstream networks and datacenter infrastructure.
FIRST SERVER
Network Infrastructure
Connectivity and DDoS protection options for public-facing infrastructure. Protection availability and scope are confirmed for each service and location.
Network architecture
Connectivity and traffic protection
Network infrastructure connects hosted systems to the internet. Where DDoS mitigation is available, traffic can pass through filtering systems before reaching the service.
DDoS mitigation
Filtering systems assess traffic and may block or limit attack patterns. Detection and mitigation depend on the network, attack type and available protection.
Service infrastructure
Permitted traffic reaches physical servers and virtual machines. Application security, access controls and software maintenance remain separate responsibilities.
Conceptual traffic flow, not a diagram of a specific network. Protection is service- and location-dependent; filtering can affect legitimate traffic and does not guarantee immunity from every attack.
DDoS protection capabilities
FIRST SERVER can provide services with DDoS mitigation options where supported by the selected network and datacenter. Protection is not automatically included with every service, IP address or location.
Protection scope includes eligible protocols and addresses, attack coverage, activation methods, traffic limits and filtering behaviour, as specified for the service. Network-level filtering and application-level protection address different risks and may require separate solutions.
Common types of DDoS attacks
A distributed denial-of-service attack attempts to overwhelm a service with traffic or requests from many sources, making it slow or unavailable to legitimate users.
Volumetric attacks
Large traffic volumes consume available bandwidth. UDP floods and reflection or amplification traffic can congest connections even before traffic reaches the server.
Protocol & connection attacks
Attacks such as SYN floods target connection handling and network resources. Firewalls, load balancers and servers can be affected.
Application-layer attacks
HTTP request floods can exhaust web applications, APIs or expensive backend operations. Application-aware controls may be needed in addition to network filtering.
Who can be affected?
Any internet-facing service can be targeted. Online shops, business websites, SaaS platforms, APIs, game servers, DNS services and remote-access endpoints can all experience disruption. A small project may also be affected by an attack on shared upstream infrastructure.
Protection scope
- Service location, public IP addresses and exposed protocols.
- Normal traffic patterns, peak bandwidth and sensitivity to latency.
- Whether protection is always active or activated on demand.
- Coverage for network attacks versus HTTP/application attacks.
- Filtering limits, possible false positives, escalation and incident handling.
No mitigation service can promise immunity to every attack. Application security, software updates, access controls and backups remain important. The agreed order and SLA define the actual commitments.