CBSA Scheduled Maintenance June 4 — Why the

The Notice

CBSA issued TCC26-0109 for a three-hour maintenance window on June 4, 2026, 20:30 to 23:30 ET. The notice says there are no planned outages, services should remain available. That last sentence is why you still need to read the System Outage Contingency Plan before 20:30 hits.

“No planned outage” means the Agency expects everything to stay up. It does not mean everything will. I’ve filed through four maintenance windows in the past year where CARM Client Portal stayed live but CCN lookups took forty seconds instead of four, and one where PARS acknowledgments stopped returning for twenty minutes. The window was scheduled, the degradation was not.

If you’re running a consolidated load that needs release codes before a 22:00 drayage pickup at the Port of Montreal, that twenty-minute gap turns into a detention charge and a morning reschedule. The contingency plan exists because maintenance windows create risk, even when CBSA doesn’t expect them to.

What Actually Breaks During Maintenance

Most scheduled windows touch backend infrastructure — database replication, load balancer patches, certificate renewals. The user-facing systems stay up, but performance degrades or specific API calls time out.

Common failure modes:

• CARM Client Portal login succeeds, but CAD submission returns a 504 timeout. The file goes nowhere, you get no transaction number, and you don’t know whether to resubmit or wait.
• eManifest accepts the A8A or A1 inbound cargo report, but the ACI status check never updates. Your driver is at primary inspection with no arrival record.
• PARS release prior to payment shows “processing” for fifteen minutes, then errors out. The goods are already on the dock, and your drayage carrier is billing waiting time.
• FIRMS lookups fail silently. You can’t validate the bonded warehouse code on an in-bond move, so you hold the shipment until the system comes back.

None of these are catastrophic if you catch them in real time and have a fallback. All of them are expensive if your broker files at 21:00, walks away, and assumes the CAD posted.

What the Contingency Plan Actually Says

The CBSA System Outage Contingency Plan is a twelve-page PDF that brokers are supposed to keep current. Most importers have never seen it. Here’s what matters:

Paper fallback for commercial releases. If CARM or PARS is unavailable, brokers can present a paper CAD (Form BSF715) at the port of entry or sufferance warehouse. The officer manually processes the release. This works, but it’s slow — expect a two-to-four-hour delay while the officer verifies your BN15, confirms the bond is on file, and enters the data by hand once the system comes back.

Verbal release authority. For time-sensitive shipments (live animals, perishables, certain pharma), CBSA can authorize verbal release by phone. The broker calls the local commercial operations unit, provides the cargo control number and importer BN, and CBSA issues a conditional release. The CAD still has to be filed within 24 hours, but the goods move. This option is rarely used because it requires officer discretion, and most ports don’t staff for it during evening maintenance windows.

Alternative port routing. If the primary port’s systems are down and the maintenance window runs past your drayage cutoff, you can redirect in-bond to a secondary location. This only works if the carrier is still on the highway and the bonded move was already authorized. Once the truck is at the dock, rerouting costs more than waiting.

ACI / eManifest paper contingency. Carriers can present a paper cargo control document if eManifest is unavailable. The driver needs a printed manifest with the CCN, shipper, consignee, and commodity description. CBSA will manually log the arrival and issue a paper receipt. The electronic record gets reconciled later. Detention risk is high because manual processing at commercial primary inspection takes fifteen to thirty minutes per truck.

What Brokers Should Do Before 20:30

If you have shipments arriving or releasing during the window, file early. A CAD submitted at 18:00 with a release code in hand by 19:30 is immune to a 21:15 portal timeout. If the shipment isn’t arriving until Friday morning, there’s no operational reason to file Thursday night during a maintenance window.

Confirm your sufferance warehouse has a current copy of the contingency plan and knows how to accept a paper BSF715. Most warehouse teams can handle it, but if they’ve only seen electronic releases since CARM went live, the first paper CAD during a system hiccup is going to cause confusion. Our Montreal facility keeps printed contingency SOPs at the dock supervisor station for exactly this reason.

If you’re an importer working with a broker, ask whether they monitor CBSA system status during filing. Some brokers submit the CAD and assume success unless they get an error email. If the portal degrades during the maintenance window, that assumption costs you a day.

When “No Planned Outage” Is Actually Reassuring

Not all maintenance windows are equal. A 20:30 to 23:30 ET window on a Thursday night is low-risk for most commercial traffic. The Port of Montreal’s last inbound drayage appointments are usually complete by 20:00, and Friday morning arrivals don’t need release codes until 06:00. If you’re releasing overnight for a weekend pickup, you have cushion.

A maintenance window from 14:00 to 17:00 on a Wednesday is a different problem. That’s peak filing time for same-day release, and any degradation creates a bottleneck that cascades into evening drayage. CBSA schedules most maintenance outside business hours for exactly this reason, but “no planned outage” during a midday window would make me file everything I could at 13:30.

The June 4 window is a non-event for most importers unless you’re running high-volume daily consolidations that rely on sub-hour release turnaround. If that’s your pattern, you already know it, and you’ve already built buffer into your dock schedule.

Why This Still Goes in the Compliance File

Every CBSA technical notice — planned maintenance, system degradation, policy clarification — gets logged in the importer’s compliance record whether or not it affected your shipments. If CBSA later questions why a CAD was filed late or why a PARS shipment sat at the warehouse for six hours, “there was a maintenance window and we followed the contingency plan” is documentation. “We didn’t know there was a maintenance window” is not.

Most importers don’t track CBSA technical notices unless their broker forwards them. If you’re managing compliance in-house or you’re the supply chain lead responsible for explaining delays to your VP, subscribe to the CSCB daily digest or set up a CBSA MyAccount notification for TCC (Trade Community Communication) messages. The signal-to-noise ratio is poor — most notices are irrelevant to your operation — but the ones that matter are time-sensitive.

Maintenance Windows Are Routine Until They Aren’t

I’ve filed through dozens of CBSA maintenance windows without incident. I’ve also had two in the past eighteen months where the portal went dark for forty minutes outside the scheduled window, and one where the CARM payment system came back up in read-only mode and wouldn’t accept bond references until the next morning. The odds are low, but the downside is high enough that having the contingency plan printed and having your broker’s after-hours contact number is cheap insurance.

June 4 will almost certainly be uneventful. If it isn’t, you’ll want to know what a BSF715 looks like and which officer to call.

If your broker doesn’t forward CBSA maintenance notices or doesn’t have an after-hours protocol for system outages, that’s a gap. We track every TCC message and route them to affected clients before the window opens. Get in touch.

Source: CSCB