Dunvale
Reports/Morning Briefing/2026-07-24
Published

US Border Intelligence Briefing - July 24, 2026

Generated Jul 24, 6:00 AM PDT

Passenger vehicles and trucks using cleared border lanes after light snow.

Winter northern-border operations

Illustrative editorial image. Not evidence of a specific event, delay, closure, or condition.

Morning Briefing Friday, July 24, 2026

US Border Intelligence Briefing - July 24, 2026

Generated 6:00 AM PDT

10 Active Crossings
123 min Avg Wait
630 min Peak Wait
9 Severe Delays
Current Top Wait Times (minutes) Brownsville Bm (p…630Eagle Pass 2 (pas…90El Paso Pdn (pass…80El Paso Pdn (pass…75Calexico West (pa…60Calexico West (pa…60El Paso Ysleta (p…60Otay Mesa Passeng…60San Ysidro (pedes…60El Paso Bota (pas…55
USD/MXN 30-day trend USD/MXN

# Morning Briefing: U.S. Border Crossings and Supply Chain Conditions

Friday, July 24, 2026

The operating picture this morning is dominated by a single severe outlier on the Southwest border: Brownsville’s passenger standard lane is posting a 630-minute wait, far above every other measured crossing in the current feed. That concentration of delay matters because the rest of the network is mixed rather than broadly stressed. Several lanes are still elevated — including Eagle Pass and multiple El Paso, Calexico, Otay Mesa, and San Ysidro pedestrian/passenger lanes — but the pattern is uneven, with some corridors easing sharply while others remain slow.

The most important change in the last 24 hours is that congestion has rotated rather than simply worsened everywhere. Brownsville’s passenger standard wait surged by 590 minutes day over day, while Brownsville Veterans and several other lanes improved materially, and some commercial or passenger lanes fell back to zero. That combination argues for corridor-specific dispatch decisions rather than a blanket assumption of border-wide deterioration. The current feed is fresh, with the latest CBP/CBSA pull timestamped 2026-07-24T12:59:10.233Z, about one minute old at the time of ingest.

Weather is also relevant, but the alerts are concentrated in the Southwest and northern Plains rather than at a single border point. Extreme Heat Warnings cover parts of Arizona through July 25–27, San Diego is under Heat Advisories through July 27 alongside a Beach Hazards Statement through July 26, and Great Falls has both a Red Flag Warning and a Heat Advisory. The main operational implication is elevated exposure for time-sensitive road movements and airport ground activity, especially where queues are already long. For aviation, San Diego International is under an airport closure notice for non-scheduled transient GA aircraft, which is a localized constraint rather than a broad commercial passenger disruption.

Trade-policy activity remains active, but the documents in the current feed are expressly raw-current policy context and not normalized legal guidance. Several Commerce and ITC notices were published today, and they matter most as a signal of continuing antidumping/countervailing duty administration across consumer and industrial product lines. The broader supply-chain implication is that compliance and landed-cost exposure remain dynamic in select categories, even though these notices should not be treated here as evidence of immediate physical border delay.

Border Crossing Conditions

The longest waits are concentrated in passenger and pedestrian flows, with Brownsville standing out as the most severe point in the feed. Brownsville BM passenger standard is at 630 minutes, far exceeding the next-highest wait, Eagle Pass 2 passenger standard at 90 minutes. El Paso also shows elevated passenger-side pressure: El Paso PDN passenger standard at 80 minutes, El Paso PDN passenger ready at 75 minutes, and El Paso Ysleta passenger ready at 60 minutes. On the California border, Calexico West passenger ready and passenger standard are both at 60 minutes, while Otay Mesa passenger pedestrian standard is 60 minutes and San Ysidro pedestrian standard is also 60 minutes. El Paso Bota passenger standard is 55 minutes, indicating that the slowdowns are not isolated to one city pair.

Operationally, the distinct lane mix matters. The feed shows both standard and ready lanes at some crossings, which suggests different conditions by lane type rather than a single uniform wait at each port. At Brownsville, the passenger standard lane is the acute problem, while the pedestrian standard lane is listed at only 60 minutes in the longest-wait table but also appears in the day-over-day changes as much lower. That divergence underscores why dispatchers should rely on the specific lane type, not just the port name. The current data support that conclusion without identifying a cause.

Significant 24-Hour Changes

The biggest day-over-day move is the Brownsville BM passenger standard lane, which jumped from 40 minutes to 630 minutes. That is the dominant operational change in the feed and should be treated as a priority routing risk until it normalizes. Brownsville also shows mixed improvement elsewhere: Brownsville Veterans passenger ready fell from 90 minutes to 1 minute, and Brownsville Veterans passenger standard fell from 90 minutes to 40 minutes. The same port therefore presents sharply divergent lane performance, reinforcing the need to choose lane type carefully.

Elsewhere, the border picture contains both easing and worsening. Eagle Pass 2 passenger standard increased from 30 to 90 minutes, a sizeable but much smaller deterioration than Brownsville’s. On the positive side, Port Huron commercial standard improved from 47 minutes to 0, and Presidio passenger standard improved from 35 minutes to 0, indicating complete clearance in those lanes at the time of observation. At Otay Mesa passenger, the passenger standard lane improved from 60 to 15 minutes, while the pedestrian standard lane improved from 90 to 60 minutes. Hidalgo passenger ready improved from 45 to 15 minutes. These reductions show that some crossing pressure is easing even as the Texas border sees severe localized congestion.

The day-over-day changes also show the kind of volatility that complicates schedule adherence. A port can move from near-clear conditions to major delay in a single day, as Brownsville did, while another can normalize quickly. Because the feed provides waits but not a cause, the only defensible statement is that conditions are unstable in specific lanes and ports; cause not identified in current feeds.

Trade-Policy Documents

Today’s policy docket is active, but it should be read as compliance context rather than direct evidence of border throughput conditions. Commerce published the final results of the expedited first sunset review of the countervailing duty order on mattresses from China, the continuation of the antidumping duty order on certain crepe paper products from China, and the final results of a countervailing duty administrative review for certain pasta from Italy. Commerce also issued preliminary results of the first full sunset review of the countervailing duty order on phosphate fertilizers from Morocco. The Office of the U.S. Trade Representative separately issued FY 2027 tariff-rate quota allocations for raw cane sugar, refined sugar, and sugar-containing products. The ITC announced an institution of investigation concerning certain anode materials for use in battery cells and batteries.

These items matter because they keep trade remedy exposure active across multiple product classes, but the feed explicitly cautions against treating raw policy-document context as normalized policy-source facts or legal advice. In operational terms, they should be considered background for shippers and brokers managing product-specific compliance, not evidence of immediate lane disruption.

Aviation and Airport Conditions

Aviation conditions are materially simpler than the border picture but still worth tracking. San Diego International Airport has a closure notice for non-scheduled transient GA aircraft, except PPR, effective 2603181300 through 2610010800. The notice is specific and does not indicate a commercial passenger airport-wide closure; it affects a defined segment of general aviation activity. For logistics teams using San Diego as a transfer point or support airport, the limitation may constrain ad hoc movements and some charter support options, but the current feed does not show a broader FAA delay event.

Because the airport notice overlaps with San Diego-area heat and beach hazard alerts, ground handling and schedule slack deserve attention even without a declared commercial disruption. The data do not establish any direct causal link between weather and the airport notice.

Weather Alerts and Crossing Conditions

Weather risk is concentrated along the Southwest and northern tier, with multiple overlapping advisories and warnings. In Arizona, the feed shows Extreme Heat Warning products issued by NWS Tucson AZ at 2:13 AM MST on July 24 running until July 25 at 8:00 PM MST, and by NWS Phoenix AZ at 1:16 AM MST on July 24 running until July 27 at 8:00 PM MST. In Southern California, NWS San Diego CA has issued a Heat Advisory effective July 24 at 2:39 AM PDT through July 27 at 8:00 PM PDT, plus a Beach Hazards Statement from July 24 at 2:30 AM PDT through July 26 at 8:00 PM PDT. In Montana, NWS Great Falls MT has a Red Flag Warning from July 23 at 11:28 PM MDT through July 25 at 9:00 PM MDT, alongside a Heat Advisory from July 23 at 11:21 PM MDT through July 26 at 9:00 PM MDT.

For border operations, the practical message is exposure, not a proven delay mechanism. The feed does not tie the weather alerts to any specific crossing slowdown, but the overlap with elevated waits at Arizona and California ports suggests that shippers should build in margin for drivers, staging, and dwell management. Repeated duplicate entries in the alert list for San Diego indicate feed duplication rather than additional distinct hazards.

Community Intelligence Context

No live community claims are provided in this feed. Accordingly, there is no current community intelligence to use as evidence. Any retired, stale, or raw diagnostic context should be treated as non-claim-bearing background only, and none is available here to extend beyond that limitation.

Macro and Economic Indicators

The macro backdrop is mixed and, in several cases, stale relative to today’s border data. The most recent foreign exchange readings are USD/CAD at 1.4014 and USD/MXN at 17.5120, both as of 2026-07-17, alongside a trade-weighted dollar at 120.53 on the same date. Energy remains elevated, with Brent crude at 86.99 and WTI at 84.38 as of 2026-07-20. U.S. diesel retail is 5.13 as of 2026-07-20, while regional gasoline series show GASDESGCW 4.94, GASDESMWW 4.99, and GASDESWCW 5.88, also as of 2026-07-20. The economic release set also includes BOPGSTB at -57,347.00 as of 2026-02-01, IR at 150.80, PCU484121484121 at 204.62, PCUOMFGOMFG at 275.70, PPIACO at 286.83, and TOTALSA at 16.95, all as of 2026-06-01.

Taken together, these figures do not provide a direct explanation for the crossing patterns, but they frame the cost environment for freight and inventory decisions. The key operational takeaway is that fuel remains expensive enough to amplify the penalty of long queues, especially where the border wait is measured in hours rather than minutes.

Outlook and Operational Watch List

The near-term outlook is straightforward: monitor Brownsville first, because the passenger standard lane is the clearest acute delay in the feed, and then watch whether the pressure spreads to adjacent Texas crossings or remains lane-specific. The rest of the network is mixed, with several lanes easing and a few still sitting at 60 minutes or more. No cause is identified in current feeds for the major swings, so the safest stance is to keep routing flexible and verify lane selection before dispatch.

Watch list for the next operational cycle:

  • Brownsville BM passenger standard for persistence or normalization from 630 minutes.
  • Eagle Pass 2 and El Paso PDN passenger lanes for follow-through on elevated waits.
  • Otay Mesa, San Ysidro, and Calexico West for whether 60-minute pedestrian/passenger waits ease further.
  • San Diego airport status for any expansion beyond transient GA restrictions.
  • Heat warnings in Arizona and Southern California for schedule and driver-impact risk.

Data sources: CBP BWT, CBSA, NWS, FAA ASWS, FRED, Banxico, INEGI IMMEX, STB Rail, Census Bureau, Statistics Canada, Federal Register

dunvale.com | RSS Feed

This report is generated from public government data. It is not investment advice. Dunvale Intelligence makes no warranties regarding accuracy or completeness.

Commercial coverage

Cited border evidence with source policy for sales, operations, and agent workflows

Border Pulse

Coverage options

4

Listed service

1

Custom quote

2

Planned

1

Recommended next step

Choose the listed Laredo service where it fits, or request custom review for San Ysidro, Otay Mesa, Texas lanes, Detroit/Windsor, or another priority crossing.

Pricing

Laredo has a listed monthly service. Otay Mesa and Detroit/Windsor are available for custom quotes. Additional crossings remain in coverage planning.

Account setup

Account teams can activate delivery after scope, access, and billing are approved.

Delivery controls

Commercial delivery, account access, billing, alerts, and automated workflows require an approved account setup.

No delivery, alerts, or account keys are activated from public pages.

Laredo policy watch

2 MVE/USMCA dates tracked for Laredo operating context.

Laredo

Market context

4 operating context families drawn from 268 reports.

Coverage detail

Laredo Border Pulse

commercial ready; listed price; $199/month; 14 facts.

Choose the listed Laredo service where it fits, or request custom review for San Ysidro, Otay Mesa, Texas lanes, Detroit/Windsor, or another priority crossing.

Otay Mesa / San Diego planned coverage

custom review ready; not yet priced; 16 facts.

Choose the listed Laredo service where it fits, or request custom review for San Ysidro, Otay Mesa, Texas lanes, Detroit/Windsor, or another priority crossing.

Otay Mesa custom coverage review

custom review available; custom quote; 16 facts.

Choose the listed Laredo service where it fits, or request custom review for San Ysidro, Otay Mesa, Texas lanes, Detroit/Windsor, or another priority crossing.

Detroit / Windsor custom coverage review

custom review available; custom quote; 21 facts.

Choose the listed Laredo service where it fits, or request custom review for San Ysidro, Otay Mesa, Texas lanes, Detroit/Windsor, or another priority crossing.

Why It Matters

Peak wait: 630 min
Average wait: 123 min
24h changes: 10
Active weather alerts: 10
Source and coverage notes

Cited report/packet claims only

Use cited packet/report evidence for claims; weather, road, policy, and map overlap stays contextual unless evidence proves causality.

Packet or replay citations must expose evidenceId, claimBearing, claimGuidance, evidenceMode, and source_ref claim policy.

Broad source-level claims also require sourceClaimAudit review, /v1/sources claimBearing=true, sourceFactHealth.total > 0, sourceFactHealth.claimBearingPolicyRows > 0, sourceFactHealth.parserLagHours within maxParserLagHours, sourceFactHealth.futureEventsBeyond7d=0 for current road claims, no pending/failed embedding backlog for semantic-only claims, no degraded-run caveats, and no blocking claimWarnings for the source family.

Raw-current, raw-only, stale, no-row, scheduled, planned, future, retired, unknown, parser-lagged, degraded-run, embedding-backlog, feed, search, and briefing source rows remain caveated context unless report citations explicitly review them.

Planned/future traffic rows must be labeled non-current planning context and not cited as current evidence.

Technical generation details

modelProvider/modelVersion: openai / gpt-5.4-mini

Lane: openai_content_optional

OpenAI content/report lanes require explicit gates and use store:false; no-call previews write local artifacts only.

Generated reports inherit cited report text, source facts, packet evidence, saved source_ref claim policy, and /v1/sources source-fact health: sourceFactHealth.total > 0, sourceFactHealth.claimBearingPolicyRows > 0, parser-lag/future-row/embedding-backlog/degraded-run checks, and no blocking claimWarnings.

Generated narrative may use only supplied data context, cited report text, cited packet evidence, or saved source_ref claim policy.

Broad source-level claims require sourceClaimAudit review, /v1/sources claimBearing=true, sourceFactHealth.total > 0, sourceFactHealth.claimBearingPolicyRows > 0, sourceFactHealth.parserLagHours within maxParserLagHours, sourceFactHealth.futureEventsBeyond7d=0 for current road claims, no pending/failed embedding backlog for semantic-only claims, no degraded-run caveats, and no blocking claimWarnings.

Raw-current policy/map rows, no-row, stale, scheduled, planned, retired, inactive, future, unknown, parser-lagged, degraded-run, and embedding-backlog rows are context only unless cited evidence explicitly says otherwise.

Do not assert causality from co-occurrence; say cause not identified in current feeds when context lacks causal evidence.

Persisted with report: yes

Key Metrics

anomalies 24h10
peak crossingbrownsville_bm
severe delays9
airport delays1
report asset idborder-operations-04
avg wait minutes123
report asset urlhttps://dunvale.com/assets/report-library/border-operations-04.webp
peak wait minutes630

Report Info

TypeMorning Briefing
Cadencedaily
ScopeNational

Subscribe

RSS Feed

JSON API: GET /public/reports/morning_briefing/2026-07-24