Atriumstatus

master9da7fa5

← all systems

Chick-in-Waffle

Not monitorednormal

Client case study with 44 assets on the CDN; site URL not yet registered here.

checked 22h ago· owner Atrium — account teamCase study

Checks

Client site

The client's own site is unreachable.

Set NEXT_PUBLIC_CLIENT_CHWF_URL to the client's production URL.

What it is

A full case study on the Atrium site (/work/chick-in-waffle) plus 44 photos and reels staged under clients/CHWF/ on the CDN. Media is served through lib/case-assets.overrides.ts, which means this client is unaffected by the Cloudinary outage.

Where the assets live

public/clients/CHWF/{photos,reels} in the CDN workspace, published to https://cdn.atriumad.com/clients/CHWF/. Run bun run manifest in apps/atrium.cdn to print the delivery URLs, and --snippet to emit the record the website pastes into its overrides file.

Several filenames contain non-breaking spaces. They work, but only with exactly one round of percent-encoding — this client is the reason that rule is documented on the CDN page.

Turning the site monitor on

Set NEXT_PUBLIC_CLIENT_CHWF_URL to the client's production URL in the status app's environment and the monitor below starts running on the next cron. Until then it is paused, and the dashboard says so rather than showing a false green.

When it breaks

Symptom

Case-study media 404s on the Atrium site

Check

The CDN client-asset monitor first — it uses this client's folder shape.

Fix

Re-run the manifest and repaste the URLs; double-encoding is the usual cause.

Needs

  • Atrium websiteThe public marketing site: home, services, work, pricing, about, resources, contact.
  • Asset CDNcdn.atriumad.com — client photos and reels on Hostinger shared hosting.

Incident history

Resolvedchwf-homeHTTP 503, expected 2008/18/2026, 6:46:39 PM · 1m
Resolvedchwf-homeHTTP 503, expected 2008/18/2026, 6:30:27 PM · 1m
Resolvedchwf-homeHTTP 503, expected 2008/18/2026, 6:28:14 PM · 2m