Traffic Jam Detection
Where is traffic jammed right now, how badly, and why? This page combines jam segments detected from vehicle speeds with user reports, groups them into ranked hotspots, looks for a nearby cause (crash, road closure, flood), then shows the nearest CCTV so you can see the conditions yourself.
Live hotspot map
Line colour shows congestion level; numbered circles are hotspots by rank. Click a hotspot or list row for details, nearby reports, the nearest CCTV, and verification links. Data refreshes automatically every 2 minutes.
Data comes from user reports and speed estimates and can lag by a few minutes or be wrong. For official traffic management and closures, follow TMC Polda Metro Jaya, the local transport agency (Dishub), and Jasa Marga for toll roads. Do not use your phone while driving.
loading traffic data…
- 0.0 km total jammed
- 0.0 km heavy jams
- 0 hotspots
- 0 severe
- 0 incidents
Hotspots (ranked)
0 of 0 hotspots
Data sources
Fetched by this site's server per area with a 90-second cache. Verification CCTV comes from the catalogues on the CCTV OSINT pages.
- live
Waze Live Map ↗
Jam segments detected automatically from Waze users' vehicle speeds (level 1–5, length, speed, added delay), plus user reports: traffic jams, accidents, road closures, floods, and roadworks.
Waze (Google) · peta lalu lintas publik / feed Waze for Cities - optional
TomTom Traffic Incidents ↗
A second, independent source built from TomTom vehicle-probe & navigation data: jams, accidents, road closures, and floods with delay magnitude. Used to cross-check Waze detections when an API key is configured.
TomTom · Traffic Incident Details API v5 (opsional)
How detection works & traffic OSINT techniques
- Detection: level ≥ 2 jam segments within 350 m of each other (or 900 m on the same road) are merged into one hotspot; user reports within 300 m are attached. Jam reports without a segment only count when backed by ≥ 2 reports or high reliability.
- Score = Σ(length km × level) + added delay/5 minutes + incident weight. "Severe" means a level ≥ 4 queue of ≥ 1 km, ≥ 15 minutes of added delay, or a score ≥ 12.
- Look for a cause: a crash, closure, flood, or roadworks near the queue is usually the cause; without an incident, jams are mostly volume (rush hour, markets, schools, toll gates).
- Visual verification: open the nearest CCTV. Toll and intersection cameras are the strongest evidence that the queue is real, and show which direction is jammed.
- Cross-check: compare with the Google Maps traffic layer, the TMC Polda Metro Jaya account, and an X search for "macet <road name>" for road users' photos/videos.
- Track the trend: the sparkline on the total-jam card shows the change since the page was opened; export GeoJSON/CSV regularly to compare rush-hour patterns across days.
Ethics & limits
- Only aggregate traffic data and public reports. Waze police-location reports are deliberately not shown, and no personal data is collected.
- Do not reshare incident reports as fact before verifying them; user reports can be wrong or stale.
- When there is a crash, respect the victims: do not spread photos/videos of victims or licence plates.