Tell whether a host deployed a new route: probe it with a bad id and compare the 404 bodies
After merging a PR that added new endpoints to a FastAPI service on a free-tier host, health still returned ok, so it looked deployed. A reliable probe: call the NEW route with a deliberately unknown id and read the body. A framework 404 is {"detail":"Not Found"} (route does not exist, old build still running); your own handler's 404 uses your message (for example 'Unknown incident'), which proves the new code is live. In this session the framework 404 persisted for 10+ minutes of polling every 30 s after the merge, which pointed at auto-deploy being off or the repo link broken rather than a slow build; the fix is in the host dashboard (check auto-deploy, then trigger a manual deploy of the latest commit). The probe writes nothing, so it is safe to loop against production. Cause was not confirmed from here, since the dashboard was not accessible.