Dunvale
Reports/Morning Briefing/2026-05-17
Published

US Border Intelligence Briefing - May 17, 2026

Generated May 17, 6:00 AM PDT

Dunvale Intelligence
Morning Briefing Sunday, May 17, 2026

US Border Intelligence Briefing - May 17, 2026

Generated 6:00 AM PDT

10 Active Crossings
67 min Avg Wait
100 min Peak Wait
9 Severe Delays
Current Top Wait Times (minutes) San Ysidro (passe…100El Paso Pdn (pass…75El Paso Pdn (pass…75San Ysidro (passe…65Douglas (passenge…60Eagle Pass 2 (pas…60El Paso Ysleta (p…60Otay Mesa Passeng…60Otay Mesa Passeng…60Buffalo Rainbow (…50
USD/MXN 30-day trend USD/MXN

Executive Summary

Border wait times show significant variance, with peak delays reaching 100 minutes at San Ysidro while several Texas crossings report minimal wait times. Severe weather alerts are active in the Southwest, and multiple trade policy notices regarding antidumping and countervailing duties have been issued.

Top Delays

  • San Ysidro (passenger_standard): 100 min
  • El Paso (passenger_ready): 75 min
  • El Paso (passenger_standard): 75 min
  • San Ysidro (passenger_ready): 65 min
  • Douglas (passenger_standard): 60 min
  • Eagle Pass 2 (passenger_standard): 60 min
  • El Paso Ysleta (passenger_ready): 60 min
  • Otay Mesa (passenger_ready): 60 min
  • Otay Mesa (passenger_standard): 60 min

Notable Changes

  • Hidalgo (passenger_ready): Decreased by 70 min (from 85 to 15 min).
  • Hidalgo (passenger_standard): Decreased by 70 min (from 90 to 20 min).
  • Eagle Pass 1 (passenger_ready): Decreased by 55 min (from 60 to 5 min).
  • Port Huron (passenger_standard): Decreased by 52 min (from 52 to 0 min).
  • Brownsville Veterans (passenger_standard): Decreased by 50 min (from 60 to 10 min).
  • Hidalgo Anzalduas (passenger_standard): Decreased by 50 min (from 55 to 5 min).
  • Hidalgo Anzalduas (passenger_ready): Decreased by 47 min (from 50 to 3 min).
  • Douglas (passenger_standard): Increased by 45 min (from 15 to 60 min).
  • Champlain (passenger_standard): Decreased by 45 min (from 45 to 0 min).
  • Progreso (passenger_standard):

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: 100 min
Average wait: 67 min
24h changes: 10
Active weather alerts: 9

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 crossingsan_ysidro
severe delays9
airport delays1
avg wait minutes67
peak wait minutes100
crossings monitored10
trade policy docs 7d10

Report Info

TypeMorning Briefing
Cadencedaily
ScopeNational

Subscribe

RSS Feed

JSON API: GET /public/reports/morning_briefing/2026-05-17

US Border Intelligence Briefing - May 17, 2026 — Dunvale