CFIA AIRS and AVS Maintenance May 24: What Breaks When the System Goes Dark

The Window

CFIA is taking AIRS (Automated Import Reference System) and AVS (AIRS Verification Service) offline May 24, 2026, from 03:00 to 07:00 Eastern. That’s routine network maintenance, happens a few times a year, usually buried in a digest item that most importers never see.

The problem is the timing. Most brokers file PARS releases between midnight and 06:00 for morning dock appointments. If your goods need CFIA clearance and the system can’t talk to AIRS during that window, your release sits in limbo until 07:00 or later. That’s a missed appointment, a rescheduled drayage slot, and if you’re cross-docking perishables through Montreal, it’s an extra day in cold storage you didn’t budget.

What AIRS Actually Does

AIRS is the reference file CBSA uses to verify CFIA admissibility. When a broker files a CAD (Commercial Accounting Declaration, the CARM-era replacement for B3), CBSA queries AIRS to confirm the commodity is cleared or if it needs a hold for inspection, Safe Food for Canadians license check, or phytosanitary certificate validation. AVS is the backend verification layer that cross-checks license numbers, permit expiry, and product registration status.

If AIRS is down, CBSA can’t confirm admissibility. The release doesn’t reject outright, it just doesn’t move. The shipment stays in “pending CFIA clearance” status until the system comes back online and the query completes.

This matters most for:

• Fresh produce and meat (HS chapters 02, 07, 08) arriving overnight for early-morning distribution
• Animal feed and pet food (chapter 23) with SFC license dependencies
• Processed foods under Safe Food for Canadians Regulations that require pre-clearance
• Plant products needing phytosanitary certificates (chapter 06, live plants)

If you’re importing industrial goods, this outage is irrelevant. If you’re moving fresh asparagus from Mexico under CUSMA, it’s a planning problem.

The Four-Hour Gap

Most importers don’t think about the overnight filing window because it’s invisible. Drayage picks up at the port at 08:00, the truck arrives at the warehouse by 10:00, and the goods are on the dock by noon. That only works because the broker filed the CAD and secured PARS release by 05:00, before the port opened.

When AIRS goes dark at 03:00, any filing that hits CBSA between 03:00 and 07:00 can’t complete CFIA verification. If your shipment arrived late, or if the cargo control number was delayed, or if the broker is filing a high volume of entries and yours landed in the queue at 04:30, you’re stuck.

The workaround is to file earlier or file later. Earlier means the broker needs the cargo control number, eManifest data, and commercial invoice by midnight instead of 03:00. That’s tight, especially if the shipment crossed the border at 22:00 and the carrier didn’t transmit eManifest until 23:30. Later means filing after 07:00 and accepting that the goods won’t release until mid-morning at best, which breaks same-day delivery.

NISC Fallback

CFIA’s notice says to contact the National Import Service Centre (NISC) if you need admissibility release during the outage. That’s technically correct but operationally useless for most brokers.

NISC is a manual helpline. You call, explain the shipment, provide the cargo control number and SFC license details, and wait for an agent to review and issue a manual release code. In practice, NISC handles emergency releases for time-sensitive goods (think live animals, urgent pharmaceutical ingredients) and treats routine produce shipments as “wait until the system is back.”

If you have a six-figure pharmaceutical import sitting at Pearson and AIRS is down, call NISC. If you have twelve pallets of California strawberries coming through our Montreal cross-dock, the answer is going to be “system maintenance ends at 07:00, file then.”

The Real Exposure

The four-hour window is predictable, which makes it manageable. The risk is when maintenance runs long or when a secondary system dependency breaks.

We’ve seen AIRS maintenance scheduled for 03:00 to 07:00 stretch to 09:30 because a database migration didn’t complete cleanly. We’ve seen AVS come back online at 07:00 but run slow enough that queries time out and CAD filings still can’t close. And we’ve seen CBSA’s own systems have a bad morning on the same day CFIA is doing maintenance, which compounds the delay.

If you’re importing perishables with a two-day shelf life window, a four-hour delay is annoying but survivable. An eight-hour delay costs you a delivery day and possibly a customer order. That’s when the dwell charges, re-delivery fees, and expedited freight costs start piling up.

The other exposure is when the importer doesn’t know AIRS is down and assumes the broker just didn’t file on time. That’s a communication gap, not a systems issue, but it happens. The broker files at 04:00, the release doesn’t move, the importer calls at 09:00 asking why the shipment isn’t cleared, and the answer is “CFIA maintenance, already knew about it, filed after 07:00, goods will release by 10:00.” If the importer had known in advance, they could have adjusted the delivery appointment or rerouted through a different carrier.

Planning Around It

If you have CFIA-regulated goods arriving the evening of May 23 or early morning May 24, tell your broker to file before 03:00 or after 07:00. That’s the entire fix.

If your shipment is already in motion and can’t be filed early, adjust the dock appointment to reflect a 10:00 or 11:00 clearance instead of 08:00. If you’re using our brokerage team, we’ll flag the AIRS outage when we review the shipment schedule and offer the resequencing option before it becomes a problem.

If you’re moving high volumes of produce or meat through the week, check the CFIA maintenance calendar every quarter. These outages are announced weeks in advance, buried in agency notices that most importers never see. That’s part of what a compliance function is supposed to catch.

The maintenance window itself is short, predictable, and manageable. The cost comes from not knowing it’s happening and filing into the dead zone anyway. If your team doesn’t track OGD maintenance schedules, that’s a process gap worth closing. Get in touch.

Source: CSCB