For Logistics & fleet operators
Route and corridor monitoring for logistics
A wildfire closure, a flood advisory or a pileup on your corridor is worth more an hour early than on arrival. CityAlert normalizes 689 official feeds — road-event services, wildfire and flood agencies, weather warnings, disaster alerts — into a GeoJSON stream you can overlay on a TMS or consume as geofenced webhook alerts. Draw a bounding box over a corridor once; get posted when disruption clusters inside it.
- feeds polled
- 689
- focus regions
- 757
- live map
- free
What you get
Geofenced webhook alerts
Register an HTTPS endpoint with a bounding box, category and severity filters. New incidents inside the box are POSTed to you each dispatch tick — road events, wildfires, floods, storms — no polling required.
Cluster mode, built for corridors
A single incident is noise; six in your corridor is a reroute decision. The cluster_threshold option switches delivery to one 'incidents.cluster' post when a threshold of matching events lands inside your geo-fence within the trailing hour — the alert fires on escalation, not chatter.
Road-event and hazard feeds
Road-condition and closure services (e.g. DriveBC), wildfire perimeters and satellite detections, flood advisories, weather warnings and disaster feeds — the disruption categories that actually stop freight, normalized to one schema.
GeoJSON for your TMS
The live stream is a standard GeoJSON FeatureCollection with bbox filtering — overlay current disruptions on your existing routing or dispatch map without a new data pipeline.
Live ops dashboards
Shareable, filterable dashboards give dispatch a common operating picture — scoped to the regions you run, viewable with no accounts.
What it won't do
We'd rather lose a deal than oversell the data — these are the honest limits for logistics & fleet operators.
Minutes, not seconds
Feed freshness is ~10–15 minutes — good for tactical rerouting and same-day planning, not for second-level telematics or emergency braking decisions.
Not a routing engine
CityAlert supplies the disruption layer; ETAs, optimization and driver dispatch stay with your TMS.
Road-closure coverage is feed-bound
Incident-level road data exists where agencies publish it — coverage is strong in the 757 focus regions and thinner elsewhere. Check the sources list for the corridors you run.
Is it a fit?
Built for you if…
- Dispatch teams that want disruption alerts pushed to them along freight corridors.
- Fleet operators who need wildfire, flood and storm risk overlaid on routing.
- 3PLs and brokers who want a shareable live picture for customers on affected lanes.
- Ops teams building agentic monitoring — the MCP server lets AI assistants query corridor status directly.
Probably not if…
- You need second-level or guaranteed-SLA alerting for life-safety dispatch — this is an open-data awareness layer.
- Your lanes run entirely outside feed coverage — verify corridor coverage first.
Free to evaluate; webhooks on the Pro plan
Poll the free GeoJSON API as long as you like to prove coverage on your lanes. Push-webhook delivery, real-time (undelayed) data and higher volumes live on the Developer ($99/mo) and Pro ($499/mo) tiers — self-serve keys, upgrade through Stripe when you're ready.
Full plan details on the pricing page; questions and enterprise scope: [email protected].
Frequently asked questions
How do corridor alerts actually work?
Register a webhook endpoint with a bbox covering your corridor plus the categories and severity you care about. Each dispatch tick (~15 minutes) POSTs newly-seen incidents inside the box. Set a cluster_threshold and instead of per-batch posts you get one incidents.cluster notification when that many matching events are inside the box in the trailing hour — escalation alerts, not chatter.
Can we pull the data into our own maps?
Yes — /api/incidents returns a standard GeoJSON FeatureCollection with bbox, category, severity and recency filters. It drops into Mapbox, Leaflet, ArcGIS or any TMS overlay without transformation.
What's the end-to-end latency?
Upstream feed cadence plus our poll cycle puts most incidents on the wire within ~10–15 minutes of official publication. Wildfire perimeters and weather warnings are effectively that; agency feeds that themselves lag will lag here too.
CityAlert.live is an aggregation and awareness tool — media-sourced incidents are approximate and every pin names its source. For emergencies always follow official channels. See our terms and sources & licenses.