Monitoring Cargo Client Sites for Agencies: SSL, DNS, and Platform Failures
Cargo is a portfolio platform built for designers, photographers, and creative professionals. Agencies managing Cargo portfolio sites for clients appreciate the platform's visual quality and minimal setup — but the same abstraction that makes Cargo easy to use creates a monitoring blind spot. SSL is managed by the platform, CNAME records point to Cargo's CDN infrastructure, and there is no public status page for platform incidents. When something breaks, the agency learns about it from the client.
This post covers the specific failure modes for Cargo client portfolios and the monitoring setup that catches them before clients do.
How Cargo Handles SSL and Custom Domains
Cargo supports custom domains for client portfolios via CNAME configuration. The agency adds a CNAME record in the client's DNS pointing to Cargo's CDN, connects the custom domain in Cargo's settings, and Cargo provisions and manages the SSL certificate for the domain.
From the agency's perspective, the setup is straightforward: one CNAME record, one domain connection in Cargo, and the portfolio is live on the client's domain with HTTPS. But the monitoring surface is the same as any platform-managed SSL setup: the agency has no direct control over certificate issuance, renewal timing, or platform infrastructure status. Failures are invisible until they produce a visible symptom.
The Failure Modes to Watch
1. Cargo platform incidents with no public status page
Cargo does not maintain a public status page with real-time incident data. When Cargo's CDN experiences degradation, a platform deployment introduces a bug, or infrastructure issues affect portfolio delivery, there is no upstream signal for agencies.
The practical consequence: when a Cargo platform incident causes multiple client portfolios to fail simultaneously, the agency diagnoses each portfolio independently before identifying the common cause. A designer managing five client portfolios gets five separate client calls. The investigation starts at the individual domain level and works backward to the platform — a process that takes significantly longer than checking a status page.
What to monitor: Cargo platform status through external monitoring. When platform incidents are active, the upstream cause becomes visible immediately alongside per-domain SSL and DNS alerts.
2. CNAME drift after registrar transfers and DNS migrations
Cargo custom domains use a CNAME pointing to Cargo's CDN. When a client transfers their domain to a new registrar — typically for renewal cost savings or to consolidate all domains under one account — the DNS records from the previous registrar or DNS provider need to be manually recreated at the new one.
The CNAME record is one of those records. It is not automatically migrated during a registrar transfer. The client's IT team or billing contact handles the transfer without agency involvement, and the CNAME recreation is easy to overlook.
The failure timeline follows the DNS TTL: the old CNAME continues resolving for existing browser cache holders, then fails once the TTL expires. New visitors encounter a DNS resolution failure immediately after the CNAME breaks. The agency typically learns about it hours or days later when the client notices traffic has dropped or a visitor mentioned the site isn't loading.
What to monitor: CNAME record integrity for all Cargo custom domains, verified by multiple independent DNS resolvers on each check interval. Any change to the expected CNAME target fires an alert immediately — before the TTL expiry window masks the failure.
3. Domain expiry on client-controlled registrars
Creative agencies build Cargo portfolios on client-owned domains. The registrar account, billing contact, and renewal notifications are controlled by the client — not the agency. When a domain expires, the Cargo portfolio site disappears completely and immediately.
Domain expiry on client-controlled registrars is a common failure mode for creative agencies: the client changes email providers, billing contact information goes out of date, or the domain was registered years ago by a previous vendor whose contact information is still on file at the registrar.
The agency is not in the notification path for any of these scenarios. The first indication is typically a client call reporting that the portfolio site is down — sometimes days after the domain expired, after the registrar grace period has begun and the domain is entering a pending deletion state.
What to monitor: Domain expiry approaching within 30 days, tracked separately from SSL expiry. The 30-day lead time allows the agency to prompt the client to renew before the domain lapses and the portfolio goes dark.
4. SSL certificate chain issues on platform-managed certificates
Cargo manages SSL certificates for custom domains as a platform service. Certificate renewal is handled by Cargo's infrastructure without agency involvement. When renewal fails — due to a CNAME drift, a Cargo infrastructure issue, or a certificate authority change — the failure is invisible until the certificate expires and browsers start rejecting it.
Platform-managed SSL with no external monitoring creates a gap: the agency has no visibility into whether the certificate currently in service is healthy, approaching expiry, or in a broken renewal state. The first indication of a certificate failure is often a visitor's browser warning.
What to monitor: Full SSL chain validation for each Cargo custom domain — expiry date, issuer, chain completeness, and domain match — checked independently on every monitoring interval. Certificate expiry fires at 30 days; chain breaks and issuer changes fire immediately.
What a Cargo Monitoring Setup Looks Like
An effective monitoring setup for a Cargo creative agency portfolio covers four layers:
SSL certificate monitoring: Validates the full certificate chain independently of Cargo's platform management — expiry date, issuer, chain completeness, domain match, and SAN coverage. Fires at 30 days before expiry and immediately on any certificate change or chain break.
DNS record monitoring: Watches the CNAME record to Cargo's CDN for every custom domain. Fires immediately on any CNAME change. Also tracks domain expiry separately with a 30-day advance alert for client-controlled registrars.
HTTP uptime monitoring: Basic availability check for the Cargo portfolio site. Catches full outages, CDN delivery failures, and configuration errors.
Vendor status monitoring: Tracks Cargo platform status externally. When a platform incident is active, it appears in the alert feed alongside per-domain alerts — allowing the agency to distinguish a platform incident from a per-client configuration issue.
Why Design Agencies Are Particularly Exposed
Design and creative agencies have a monitoring risk profile that differs from technical development agencies in one important way: the technical infrastructure is not the core service, and it doesn't receive the same ongoing technical attention.
A web development agency has developers who understand DNS, check certificate expiry dates, and notice when a CNAME record has gone stale. A design agency has designers and account managers who focus on creative quality — and who rely on the hosting platform to handle infrastructure correctly.
When the hosting platform's managed SSL fails or a client DNS change breaks the CNAME, a design agency typically has no technical staff in a position to catch it proactively. External monitoring fills that gap without requiring a technical team.
How Merlonix Covers Cargo Client Portfolios
Merlonix is designed for agencies managing client portfolios across different platforms. Adding a Cargo portfolio domain takes under two minutes: DNS TXT record verification, then SSL and DNS monitoring starts automatically.
Each client's portfolio domains are organized under their client account. When a CNAME breaks after a registrar transfer, the alert fires within minutes. When domain expiry approaches, the alert fires 30 days ahead. When a Cargo platform incident is active, the vendor status feed surfaces it separately from per-domain alerts.
Start a free trial and add your first Cargo portfolio domain.
→ Related: Framer Agency Monitoring → Related: Ghost Agency Monitoring → Related: What Causes DNS Record Drift → Related: When a Client Domain Expires: What To Do → Related: How to Audit Client SSL Certificates