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

US Border Intelligence Briefing - April 24, 2026

Generated Apr 24, 6:13 AM PDT

Dunvale Intelligence
Morning Briefing Friday, April 24, 2026

US Border Intelligence Briefing - April 24, 2026

Generated 6:13 AM PDT

10 Active Crossings
110 min Avg Wait
170 min Peak Wait
10 Severe Delays
Current Top Wait Times (minutes) Otay Mesa Passeng…170Otay Mesa Passeng…170San Ysidro (passe…130Brownsville Bm (p…120Brownsville Gatew…120Eagle Pass 2 (pas…90San Ysidro (passe…90El Paso Ysleta (p…75El Paso Bota (pas…70El Paso Bota (pas…65
USD/MXN 30-day trend USD/MXN

# Dunvale Intelligence: Daily Logistics Briefing

Date: Friday, April 24, 2026

Data Source Freshness: CBP/CBSA border pull is 12 minutes old (as of 12:48:17Z).

Executive Summary

Border operations show high variability, with Otay Mesa experiencing significant increases in wait times (170 minutes) while other corridors report substantial reductions. Multiple weather watches remain active across the region, and the commodity market shows stable pricing for diesel and crude oil.

Top Delays

The longest reported wait times for passenger vehicles are concentrated in the Otay Mesa area:

* otay\_mesa\_passenger (ready/standard): 170 minutes

* san\_ysidro (standard): 130 minutes

* brownsville\_bm (standard): 120 minutes

* brownsville\_gateway (standard): 120 minutes

Notable Changes

Significant fluctuations were observed across several crossings over the last 24 hours:

* Increases: Wait times at otay\_mesa\_passenger (both ready/standard) increased by 80 minutes (from 90 min to 170 min). Eagle Pass 2 (standard) increased by 60 minutes (from 30 min to 90 min).

* Decreases: Douglas (pedestrian\_standard) saw a reduction of 87 minutes (from 90 min to 3 min). Brownsville Gateway (pedestrian\_standard) decreased by 80 minutes (from 120 min to 40 min).

* Specific Data: Brownsville (gateway) saw a decrease of 80 minutes for the pedestrian crossing.

Trade Policy & Regulatory Updates

* Trade Actions: No new trade actions were reported.

Weather & Operational Advisories

* Advisories: No weather advisories were issued.

Commodity & Market Intelligence

* Diesel Price: No specific commodity price data was provided.

Geopolitical & Security Insights

* Security: No security incidents were reported.

Source Intelligence

* Source: N/A

Key Takeaways

* Operational Focus: Be aware of the significant variability in wait times, particularly noting the sharp increases at the Otay Mesa crossing.

* Planning: Plan for potential delays due to the high variability in crossing times.

***

*Disclaimer: This report is based on the data provided and is for informational purposes only. Always verify operational status with official sources.*

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: 170 min
Average wait: 110 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 crossingotay_mesa_passenger
severe delays10
airport delays1
avg wait minutes110
peak wait minutes170
crossings monitored10
trade policy docs 7d10

Report Info

TypeMorning Briefing
Cadencedaily
ScopeNational

Subscribe

RSS Feed

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