CBP Resolves ACE Manifest and In-Bond Notification Delays

Key Points

• CBP confirmed via CSMS #70231481, issued October 19, 2026, that outbound notification delays affecting Air Manifest, Ocean Manifest, Rail Manifest, and In-Bond have been fully resolved.
• All four manifest modes and In-Bond notifications were affected during the incident window.
• Filers with unresolved questions should contact their assigned CBP Client Representative directly.

On this page

1. What happened and what changed
2. Affected filing types and modes
3. What the resolution means for filers
4. What brokers and compliance teams should do now
5. Key references

CBP's Cargo Systems Messaging Service announced on October 19, 2026 that delays in outbound ACE notifications for Air, Ocean, and Rail Manifest as well as In-Bond transactions have been resolved. Filers who experienced missing or late system responses during the outage should verify their queued transactions processed correctly and reach out to their CBP Client Representative for any outstanding issues.

The links in this article go to the primary documents: the official CBP CSMS notice itself. Read the source.

What happened and what changed

CBP's Automated Commercial Environment (ACE) experienced a period in which outbound notifications, the system-generated responses that confirm receipt and processing of manifest and In-Bond filings, were delayed. The issue spanned all three primary cargo transport modes: air, ocean, and rail. In-Bond movement notifications were also affected. CBP's CSMS #70231481 confirmed that the underlying cause has been identified and corrected.

Affected filing types and modes

The delay touched four distinct filing categories within ACE:

• Air Manifest outbound notifications
• Ocean Manifest outbound notifications
• Rail Manifest outbound notifications
• In-Bond outbound notifications

Outbound notifications are the machine-to-machine responses ACE sends back to trade filers and software systems to confirm that a submission was received and acted upon. When these are delayed, filers cannot confirm whether a manifest or In-Bond authorization is active, which can affect cargo release timing and bond liability tracking.

What the resolution means for filers

With the issue resolved, ACE should be generating and transmitting outbound notifications normally for all affected filing types. However, transactions submitted during the delay window may have queued responses that arrived late or out of sequence. Filers relying on automated downstream workflows, such as triggering freight release or updating In-Bond status in a TMS or compliance system, should audit those records to confirm the data integrity of anything processed during the incident period.

CBP has not published a defined incident window in CSMS #70231481, so filers should consult their own system logs to identify any submissions that lacked timely notification responses and cross-check them against current ACE status.

What brokers and compliance teams should do now

• Review ACE transaction logs for Air, Ocean, and Rail Manifest filings and In-Bond movements that may have been submitted during the delay period and confirm that outbound notifications have now been received.
• Check any In-Bond records for accurate status updates, since delayed notifications can affect the recorded arrival and transfer timestamps that CBP uses to enforce bond time limits.
• Contact your assigned CBP Client Representative if you have specific transactions you believe were not properly resolved, as directed by CSMS #70231481.

Key references

• CSMS #70231481: CBP official notice confirming resolution of outbound notification delays for Air, Ocean, and Rail Manifest and In-Bond (October 19, 2026).
• CBP ACE Program Office: Landing page for ACE system updates, CSMS archives, and trade filer resources.