AT01 operational
Edge node AT01 · Austria

Static assets, served from the edge.

This hostname is a delivery node of the KarumWeb content network. It caches and serves images, scripts, fonts and downloads for customer projects over TLS 1.3.

response headers
$ curl -I https://cdn-at01.karumweb.ru/{zone}/app.9f3c1e.js

HTTP/2 200
content-type: application/javascript
cache-control: public, max-age=31536000, immutable
content-encoding: gzip
x-cache: HIT
x-edge-node: AT01
age: 48211
TLS 1.3modern ciphers only
HTTP/2multiplexed delivery
1 yearimmutable asset caching
24 / 7automated health checks
Platform

What this node does

Every edge node runs the same stack: a caching layer in front of customer origins, with rules managed centrally and pushed to all locations.

Edge caching

Versioned assets are stored on the node and returned without a round trip to the origin.

Origin shield

Origins accept traffic only from edge nodes. Their addresses are never exposed to visitors.

Instant purge

Invalidate a single file, a prefix or a whole zone. Changes reach every node within seconds.

Managed certificates

Certificates are issued and renewed automatically. Assets are served over HTTPS only.

Access rules

Signed URLs, referrer allow-lists and per-zone rate limits protect paid or private content.

Delivery analytics

Requests, cache ratio and transferred volume are aggregated per zone and per location.

Network

Regions

Requests are answered by the nearest healthy location. If a node is drained for maintenance, traffic moves to the neighbouring region.

Direct browsing is not available. Edge hostnames serve files by exact path. Listing a zone or opening its root returns this page. Customer consoles are provided separately with the service agreement.
RegionRoleState
EU Central AT01EdgeOperational
EU WestEdgeOperational
EU NorthEdgeOperational
Control planeConfiguration, purgeOperational
Status

Last 90 days on this node

Each bar is one day. Maintenance windows are announced to customers in advance.

Asset delivery99.98%
Origin pull99.95%
Purge propagation100%
90 days agoToday
Integration

Pointing a project at the edge

Three steps are enough for most static sites and application bundles.

  1. Create a zoneA zone maps a path prefix on the edge to your origin server or storage bucket.
  2. Fingerprint your filesAdd a content hash to file names so that every release gets its own cache entry.
  3. Switch asset URLsReference scripts, styles and media through the edge hostname in your build configuration.
index.html
<!-- before -->
<script src="/static/app.js"></script>

<!-- after -->
<link rel="preconnect"
      href="https://cdn-at01.karumweb.ru">
<script src="https://cdn-at01.karumweb.ru
  /{zone}/app.9f3c1e.js" defer></script>