Origin

No. Hetzner does not provide a native content delivery network. Hetzner’s Object Storage FAQ explicitly says that Object Storage is not a CDN and recommends placing a third-party CDN in front of it for large-scale global delivery. Hetzner can still be the origin. A CDN can fetch files from Hetzner Object Storage, a cloud server, a dedicated server, or a load-balanced application and cache suitable responses at its edge locations. What Hetzner provides Hetzner provides infrastructure products such as cloud servers, dedicated servers, load balancers, DNS, and S3-compatible Object Storage. These products run applications and store content. Their data-center locations are not a globally distributed CDN cache footprint. ...

Overview Hetzner provides cloud servers, dedicated servers, DNS, load balancers, and object storage. It does not advertise a native content delivery network. Hetzner’s Object Storage documentation recommends placing a third-party CDN in front of a bucket when globally distributed caching is required. Network and architecture Hetzner infrastructure can act as a CDN origin. Its documented cloud locations are in Europe, North America, and Singapore. Those locations are data-centre regions, not a CDN edge footprint. ...

Synopsis An origin that serves multiple CDNs must tolerate their combined fetch patterns and different failure behavior. Topology, shielding, authentication, cache keys, deployment order, and failover controls determine whether content remains correct when traffic moves. Role of the origin in multi-CDN The origin is the source of truth for content and APIs. In a multi-CDN setup more than one provider will fetch from it. The design must handle higher fan in, different retry behaviors, and different cache semantics without breaking correctness. It should also keep the number of variables low so that problems are diagnosable during incidents. ...