CARM Goes Dark October 3: What the 12-Hour Maintenance Window Means for Your Weekend Releases

The Maintenance Window

CBSA is pulling CARM offline for scheduled maintenance on Saturday, October 3, 2026, from 0900 to 2100 ET. The CARM Client Portal, CAD EDI, CAD API, the Tariff and Duty Calculator, and the Bond API all go dark for twelve hours. If you’re filing a CAD, checking your Statement of Account, or running tariff scenarios that morning, you’re out of luck until evening.

The notice says to follow System Outage Contingency Plan procedures. That’s CBSA’s formal fallback protocol, and it’s worth understanding what it actually means when CARM is unavailable, because this won’t be the last maintenance window.

What SOCP Means in Practice

When CARM is down, electronic CAD filing stops. Your broker can’t transmit a release via EDI or API. The contingency is paper: a printed CAD summary presented to CBSA at the port of entry or sufferance warehouse, with manual review and release authorization. The accounting part (the full duty and tax calculation, the formal record in the Statement of Account) gets deferred until CARM comes back online.

Cargo still moves. CBSA officers at the border and at inland exam sites have fallback procedures to release goods without live system access. The delay is administrative, not physical, but there are two friction points.

First, paper CAD review is slower. An officer who would normally see a transmitted release in seconds now flips through a printed summary and cross-checks it against the cargo control document and any OGD holds. If your shipment is straightforward PARS or RMD with no exam flag, the delay is minor. If it’s a first-time NRI, or flagged for CFIA inspection, or carrying subject goods under a SIMA case, expect the officer to take their time. There’s no system prompt to auto-clear the low-risk stuff.

Second, the accounting lag creates a Statement of Account gap. Releases processed under SOCP during the outage get recorded retroactively once CARM is back. If you’re tracking your RPP bond utilization weekly or watching your Statement of Account balance ahead of a large payment, Saturday’s releases won’t appear in the system until Sunday evening at the earliest, possibly Monday morning. That’s not a problem for most importers, but if you’re running close to your financial security limit or trying to reconcile October’s duty liability in real time, the lag is annoying.

Why Saturday

CBSA picked Saturday for a reason. The majority of commercial import volume clears Monday through Friday. Weekend operations exist (perishables, e-commerce fulfillment, automotive JIT replenishment, retail cross-dock for Monday store deliveries), but they’re a fraction of weekday throughput. A Saturday outage minimizes the number of CADs filed under contingency and keeps the paper backlog manageable.

If you’re not running weekend freight operations, this maintenance window is invisible. Your Monday morning releases file normally, your broker’s EDI queue is clear, and the only sign anything happened is the CBSA notice in your inbox.

But if you do run Saturday, here’s what to expect. Any cargo arriving Friday night or early Saturday that would normally clear Saturday morning will follow the paper path. If your brokerage team is filing the CAD at 0930 Saturday, they’re printing it and hand-delivering or faxing it to the CBSA officer at the port. Fax is still the formal fallback, and yes, that’s exactly as slow as it sounds. A normal Saturday release that would take two hours might stretch to four.

Perishables and time-sensitive pharma cargo get priority under SOCP, same as they do during normal operations, but the manual workflow adds time even with priority handling. If your cold-chain shipment is scheduled for a Saturday Montreal sufferance warehouse pickup and your buyer is expecting it for a Sunday prep shift, build in buffer. The release will happen, but it won’t happen on the normal EDI timeline.

The Bigger CARM Dependency Question

This maintenance window is planned, communicated two weeks in advance, and scheduled for minimal impact. The real test of CARM contingency planning is an unplanned outage on a Tuesday morning at 0800 when five hundred importers are trying to file CADs for cargo that arrived overnight.

CARM has been stable since Release 3 went live in October 2024, but the system is complex and the EDI integration layer touches every licensed broker in the country. An API failure, a portal authentication bug, or a database latency spike during peak filing hours would trigger the same SOCP procedures, except with a hundred times the volume and zero advance notice.

If your customs program assumes CARM is always available, you’re carrying latent risk. The SOCP procedures work, but they slow everything down, and they assume your broker has a process for paper CAD filing that’s been tested recently. A lot of brokers haven’t touched a fax machine in two years. If CARM goes dark on a weekday and your broker is scrambling to figure out the paper fallback while your cargo sits at the port, that’s a planning failure on both sides.

The mitigation is straightforward: make sure your broker has documented SOCP procedures, knows how to print and submit a paper CAD, and has tested it within the last twelve months. If you’re managing release timelines for perishables, pharma, or JIT manufacturing inputs, ask your broker what the fallback SLA is under SOCP. If the answer is vague, that’s a red flag.

What’s Actually Affected

The October 3 outage hits five things: the CARM Client Portal (where you check your Statement of Account, manage financial security, and update your business information), CAD EDI (the broker-to-CBSA transmission for electronic release filing), CAD API (the newer JSON-based filing method some brokers are migrating to), the Tariff and Duty Calculator (the public tool for running HS classification and duty rate lookups), and the Bond API (used for querying RPP bond status and posting financial security).

If you were planning to log into the Portal on Saturday morning to review your September Statement of Account or adjust your RPP bond coverage, you’ll need to wait until Saturday night. If your compliance team was going to run tariff scenarios for a new product line coming in next week, that’s also on hold.

The Bond API outage is mostly invisible unless your broker is in the middle of posting a new financial security instrument or your finance team is pulling live bond utilization data for a board report. Twelve hours won’t break anything, but it’s worth knowing the system is read-only (at best) during the window.

Your Checklist

If you’re importing this weekend, confirm your broker knows about the outage and has SOCP procedures ready. If you’re not, file this for the next time CBSA announces maintenance or you see an unplanned CARM service disruption notice.

The system works, and the contingency works, but both assume you’ve planned for the gap. Most CARM outages are short and scheduled for low-impact windows. The one that isn’t will happen on a Tuesday morning, and if your first time learning about SOCP is when your broker calls to say your release is delayed, you’re behind.

If you want to walk through what your weekend or after-hours release process looks like when CARM is unavailable, we run that scenario planning regularly. Get in touch.

Source: CSCB