First live-AI day (2026-09-27, prod 6658c26). Incident 91b0b78a-072d-4433-ac75-53018147abff opened 16:51 ET, still active at 19:25 with 40 calls and a 37.4 km path.
It keeps absorbing unrelated Ch 1 (Patched 155.310) traffic via corr: fast/thin and fast/disambig links, e.g. 18:25 "Sam 1 ... report of another four-car accident just east of our location" linked in as fast/thin. Meanwhile the separate Cross County multi-car (17:07, 12 calls) was correctly its own incident, so this is not one scene.
Suspected mechanism: severity-scaled quiet timer (90 min for Major) + reopen-on-link means a busy countywide channel never goes quiet long enough, and fast/thin has no scene/location veto against a new-dispatch phrase ("report of another ... accident").
Test: 09-27 16:45-19:30 ET in /admin Replay (#170). Related: #155 (clearing), #35 (fast/thin dominates).
First live-AI day (2026-09-27, prod 6658c26). Incident `91b0b78a-072d-4433-ac75-53018147abff` opened 16:51 ET, still **active** at 19:25 with 40 calls and a 37.4 km path.
It keeps absorbing unrelated Ch 1 (Patched 155.310) traffic via `corr: fast/thin` and `fast/disambig` links, e.g. 18:25 "Sam 1 ... report of **another four-car accident** just east of our location" linked in as `fast/thin`. Meanwhile the separate Cross County multi-car (17:07, 12 calls) was correctly its own incident, so this is not one scene.
Suspected mechanism: severity-scaled quiet timer (90 min for Major) + reopen-on-link means a busy countywide channel never goes quiet long enough, and fast/thin has no scene/location veto against a new-dispatch phrase ("report of another ... accident").
Test: 09-27 16:45-19:30 ET in /admin Replay (#170). Related: #155 (clearing), #35 (fast/thin dominates).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
First live-AI day (2026-09-27, prod
6658c26). Incident91b0b78a-072d-4433-ac75-53018147abffopened 16:51 ET, still active at 19:25 with 40 calls and a 37.4 km path.It keeps absorbing unrelated Ch 1 (Patched 155.310) traffic via
corr: fast/thinandfast/disambiglinks, e.g. 18:25 "Sam 1 ... report of another four-car accident just east of our location" linked in asfast/thin. Meanwhile the separate Cross County multi-car (17:07, 12 calls) was correctly its own incident, so this is not one scene.Suspected mechanism: severity-scaled quiet timer (90 min for Major) + reopen-on-link means a busy countywide channel never goes quiet long enough, and fast/thin has no scene/location veto against a new-dispatch phrase ("report of another ... accident").
Test: 09-27 16:45-19:30 ET in /admin Replay (#170). Related: #155 (clearing), #35 (fast/thin dominates).