Dunvale
Reports/Morning Briefing/2026-04-26
Published

US Border Intelligence Briefing - April 26, 2026

Generated Apr 26, 6:09 AM PDT

Dunvale Intelligence
Morning Briefing Sunday, April 26, 2026

US Border Intelligence Briefing - April 26, 2026

Generated 6:09 AM PDT

10 Active Crossings
66 min Avg Wait
90 min Peak Wait
5 Severe Delays
Current Top Wait Times (minutes) Brownsville Gatew…90Brownsville Gatew…90Otay Mesa Passeng…90Otay Mesa Passeng…90El Paso Bota (pas…60El Paso Pdn (pass…55El Paso Pdn (pass…54El Paso Bota (pas…50Eagle Pass 2 (pas…45Santa Teresa (pas…35
USD/MXN 30-day trend USD/MXN

# Dunvale Intelligence: Daily Logistics Briefing

Date: Sunday, April 26, 2026

Data Source Freshness: 12 minutes old (As of 12:48:17Z)

Executive Summary

Border operations are currently experiencing significant congestion at Brownsville Gateway and Otay Mesa, with wait times reaching 90 minutes for both passenger ready and standard lanes. Operational shifts were pronounced over the last 24 hours, notably sharp increases at Brownsville Gateway and El Paso PdN, while San Ysidro saw substantial reductions in wait times. Severe weather alerts, including High Wind and Red Flag Warnings, are active across the El Paso corridor.

Top Delays

The longest reported wait times for passenger vehicles are concentrated in the South Texas corridor:

* Brownsville Gateway: 90 minutes (Passenger Ready and Passenger Standard)

* Otay Mesa: 90 minutes (Passenger Ready and Passenger Standard)

* El Paso Bota: 60 minutes (Passenger Standard)

* El Paso PdN: 55 minutes (Passenger Standard)

Notable Changes

Significant variability was observed in wait times over the past 24 hours:

* Increases: Brownsville Gateway saw a 60-minute increase in wait times for both passenger standard (30 $\rightarrow$ 90 min) and passenger ready (30 $\rightarrow$ 90 min) lanes. El Paso PdN also increased significantly, with passenger ready rising 43 minutes (11 $\rightarrow$ 54 min) and passenger standard rising 43 minutes (12 $\rightarrow$ 55 min).

* Decreases: San Ysidro experienced substantial reductions, with passenger standard dropping 70 minutes (100 $\rightarrow$ 30 min) and pedestrian standard dropping 70 minutes (75 $\rightarrow$ 5 min). Progreso saw a 60-minute decrease in passenger standard wait times (60 $\rightarrow$ 0 min).

Trade Policy Context

The International Trade Administration issued multiple final determinations and notices over the past week, primarily concerning anti-dumping and countervailing duties. Key actions include:

* China: Final determinations regarding Chassis and Subassemblies, and Hardwood Plywood Products.

* Mexico: Final Affirmative Countervailing Duty Determination on certain chassis and subassemblies.

* Thailand: Final Affirmative Determination of Sales at Less Than Fair Value for certain chassis and subassemblies.

* Vietnam: Final Affirmative Determination of Sales at Less Than Fair Value for certain chassis and subassemblies.

Aviation & Airport Status

* SAN (San Diego Intl): Currently listed as Closed. The notice specifies closure for non-scheduled transient general aviation aircraft between 00:00 and 23:59.

Weather & Conditions

* No specific weather advisories were provided, but the operational status of the border crossings should be monitored due to the high volume of activity noted in the data.

Economic Indicators

* No economic indicators were provided.

Commodity Prices

* No commodity prices were provided.

Summary

The primary operational concern is the high congestion noted at the Brownsville/El Paso area, coupled with the significant operational changes noted at San Diego International Airport. Travelers should anticipate potential delays.

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: 90 min
Average wait: 66 min
24h changes: 10
Active weather alerts: 7

Claim Policy

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.

Model Generation Policy

modelProvider/modelVersion: local / gemma4:e4b

Lane: local_report_generation

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 report wording is reusable only inside 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, stale, no-row, scheduled, planned, retired, unknown, planned/future, parser-lagged, parser-incomplete, degraded-run, and embedding-backlog rows remain context only unless cited evidence says otherwise.

Do not infer causality from co-occurrence; weather, road, policy, and wait overlap stay contextual unless evidence proves cause.

Persisted with report: no

Key Metrics

anomalies 24h10
peak crossingbrownsville_gateway
severe delays5
airport delays1
avg wait minutes66
peak wait minutes90
crossings monitored10
trade policy docs 7d10

Report Info

TypeMorning Briefing
Cadencedaily
ScopeNational

Subscribe

RSS Feed

JSON API: GET /public/reports/morning_briefing/2026-04-26