CanFlow Global
eManifest Portal Outage: What Just Happened
← All insights
emanifestcerscbsa-portalacipars

eManifest Portal Outage: What Just Happened

eManifest and CERS portals had a 2.5-hour outage this morning. CBSA traced the root cause to browser cache, not their system infrastructure.

CBSA’s eManifest and CERS portals went down this morning for two and a half hours. The outage ran from 10:00 to 12:30 ET, affecting every broker and carrier filing advance cargo data or export declarations through the web interface.

The root cause turned out to be cached browser data. CBSA’s resolution: clear your cache, cookies, and browsing history, then log back in. That’s an unusual diagnosis for what initially looked like a system-wide portal failure.

What eManifest Actually Does

eManifest is the portal brokers and carriers use to submit advance commercial information (ACI) for goods arriving in Canada. For highway shipments, that means PARS (Pre-Arrival Review System) data. For marine and air, it’s the cargo control document and conveyance reporting.

The timing matters. Marine ACI cargo data is due 24 hours before loading at the foreign port. PARS can be submitted up to 30 days before arrival, though most brokers file closer to the border crossing. When the portal is down during morning filing hours, that’s a problem for time-sensitive shipments.

CERS (Canadian Export Reporting System) is the export equivalent. It’s how exporters and forwarders report goods leaving Canada, replacing the old paper B13A process. Less critical for most customs brokers, but essential for anyone handling outbound commercial shipments.

Two and a Half Hours Is Manageable

This wasn’t a long outage. By lunch it was resolved. But even a short portal interruption creates a backlog, especially in the 09:00-11:00 window when brokers are filing PARS for same-day or next-day arrivals.

If you’re a highway carrier with a truck crossing at 14:00 and your broker can’t file PARS until 12:30, you’re cutting it close. CBSA expects the data well ahead of arrival for release prior to payment. A late PARS filing doesn’t block the crossing, but it pushes the shipment into a slower release stream.

For marine and rail, the impact is smaller. Those shipments have longer lead times built in, and a two-hour portal hiccup doesn’t usually move the needle on vessel arrival schedules.

The Browser Cache Angle

This incident was unusual: CBSA determined the root cause was cached browser data on the user side, not a problem with their portal infrastructure.

That suggests the “intermittent issue” wasn’t a true system outage. More likely, a recent portal update or configuration change conflicted with stale cached assets in users’ browsers. Some brokers could log in, others couldn’t. It looked like a CBSA system problem because multiple users were affected at the same time, but the fix was local.

This is rare. Most CBSA portal issues are legitimate system interruptions: maintenance windows, authentication failures, database timeouts. A cache conflict that presents as a service outage is harder to diagnose because the error symptoms vary by user.

If you filed PARS successfully this morning before 10:00, your cached session was fine. If you logged in fresh at 10:15 and hit a blank screen or error message, you got the bad cache. CBSA’s TCC notice correctly identified the fix, but it took them until 12:30 to get the word out and confirm the workaround resolved it for everyone.

Practical Takeaways

If you use eManifest or CERS through a browser (not EDI), clear your cache monthly. Browser updates and portal changes pile up. A fresh cache eliminates one variable when login issues appear.

If you see a CBSA TCC notice about an “intermittent” portal issue, check whether other brokers in your network are affected. Intermittent usually means some users are fine, others aren’t. That’s your signal to try the basic fixes: clear cache, different browser, incognito mode. Don’t wait two hours for a TCC resolution notice if the workaround is a 30-second cache clear.

This is why high-volume brokers file via EDI. The eManifest web portal is reliable most of the time, but EDI connections bypass the browser entirely. If your operation files 50+ PARS per week, you’re already past the threshold where EDI makes sense.

Why Portal Uptime Matters

eManifest and the CARM Client Portal are the two web interfaces brokers live in daily. eManifest handles pre-arrival cargo data. CARM handles post-release accounting: CAD filings, Statement of Account reviews, RPP bond monitoring, duty and tax payments.

When eManifest goes down, you can’t file new PARS or update existing ones. That delays release for time-sensitive shipments. When CARM goes down, you can’t file CADs, check importer account balances, or pull the monthly Statement of Account. Those have longer deadlines, so a short CARM outage is less disruptive than an eManifest outage during morning filing hours.

Both portals are more stable now than in the first year of CARM. Release 3 went live October 21, 2024, and the first six months had their share of issues: timeouts, slow page loads, session drops. Things have improved since then. A two-hour hiccup caused by browser cache is minor compared to the early CARM days.

Still, any portal interruption during peak filing hours gets attention. Brokers work on tight turnarounds. A shipment that arrives at a Montreal sufferance warehouse mid-morning expects CBSA release by end of day. If the broker can’t file PARS until afternoon because the portal was down, that timeline compresses. FENGYE LOGISTICS’ Montreal sufferance warehouse handles inbound clearances daily, and a few hours of portal downtime can ripple into next-day pickup schedules if the exam queue backs up.

This One Was Noise

Most CBSA TCC notices are either scheduled maintenance (ignore unless it affects your filing window) or actual system outages (wait it out, file when it’s back). This morning’s incident was neither. It looked like an outage, but the fix was client-side.

That’s worth knowing. The next time you see “intermittent portal issue,” try clearing your cache before assuming CBSA’s system is down. If that fixes it, you’re back to filing in 30 seconds instead of waiting for a TCC resolution notice.

We cleared the cache and resumed filing by noon. Still hitting eManifest errors? Get in touch.

Source: CSCB

Talk to a broker