Monday, July 27, 2026
Border pressure, notable changes, and source-linked operating context for this day.
Generated 8:55 AM PDT
85
Represented Ports
--
Avg Wait
--
Peak Wait
10
Anomalies
Commercial coverage
Cited border evidence with source policy for sales, operations, and agent workflows
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.
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.
Published Wait Context
Recent Wait Spikes
Otay Mesa Passenger
Pedestrian Standard · Z-score: 4.8
Otay Mesa Passenger
Passenger Standard · Z-score: -3.0
Laredo 1
Pedestrian Standard · Z-score: 8.7
El Paso Pdn
Passenger Nexus Sentri · Z-score: 5.2
El Paso Pdn
Passenger Standard · Z-score: 3.3
Detroit Windsor
Commercial Standard · Z-score: 0.0
Derby Line
Passenger Standard · Z-score: 5.7
Calais Intl Ave
Passenger Standard · Z-score: 0.0
Buffalo Rainbow
Passenger Standard · Z-score: 5.9
Buffalo Peace
Passenger Standard · Z-score: 18.4
Subscribe
RSS FeedData Sources
Methodology
This briefing is generated from structured Dunvale source snapshots and cited report context. Claim-bearing use stays inside returned evidence, timestamps, units, source names, and any saved 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, no degraded-run caveats, and no blocking claimWarnings. The model does not browse external sources while generating a briefing.
Claim policy
Briefing claims require cited briefing text, cited snapshot rows, or saved packet/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, raw-only, stale, no-row, scheduled, planned, future, retired, unknown, missing-source, parser-lagged, degraded-run, embedding-backlog, search, feed, and briefing-card rows remain context only unless packet/replay evidence says otherwise.
Generation policy
modelProvider/modelVersion: local / gemma4:12b-it-qat
Lane: local_briefing_generation
Briefings are saved as crossing_summaries rows; use claimPolicy plus source_ref/packet evidence for claim-bearing reuse.
OpenAI content/report lanes require explicit gates and use store:false; no-call previews write local artifacts only.
Briefings inherit cited briefing text, cited snapshot rows, saved packet/source_ref claim policy, sourceClaimAudit review, 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.
Do not infer causality from co-occurrence; weather, road, policy, and wait overlap stay contextual unless evidence proves cause.

