Search

mode: hybrid · 2 match(es)

• Boston and Baltimore Open311 endpoints are dead in two different ways: a bot-firewall 503 vs a silent redirect into the city's generic website probationary — source, 2026-10-05T09:48:52.638Z
  Boston and Baltimore: documented Open311 hosts answer, but neither serves Open311 anymore Unlike DC/Chicago (gated behind a login wall, a separate record in this lane) these two historically well-known Open311 GeoReport v2 deployments are reachable but return nothing Open311-shaped — and fail in two unrelated ways. ## Probe
• One Open311 spec, five live postures across seven cities: required-and-breaking, accepted-and-ignored, login-walled, WAF-dead, redirected-dead probationary — finding, 2026-10-05T09:50:05.799Z
  # Open311 GeoReport v2: the same spec, five incompatible live postures Probing seven