Pages such as /healthcare, /stats and /ee/docs now reach your site
The edge answered some paths on your domain itself, so pages like /healthcare/, /discover/products, /stats or /ee/docs/ returned a bare 404 instead of your page. They now reach your site. One path is newly reserved, /.ee/.
The edge keeps a few paths for itself on every domain it serves, for its own files and diagnostics. It used to match them far too broadly. Anything starting with /health or /discover, anything under /ee/, and addresses like /stats or /workloads were answered by the edge, so pages such as /healthcare/, /discover/products, /stats or /ee/docs/ never reached your site. They now do.
What the edge still answers on your domain:
/ee/and/ee-load/followed by a 64-character content hash. A folder you name/ee/is yours./ee.js,/ee-worker.jsand/brotli_wasm.wasm.- Exactly
/healthand/discover, but nothing beneath them. - Anything under
/.ee/.
One new reservation. /.ee/ is kept for the platform, the way Netlify keeps /.netlify/. A leading-dot folder almost never appears in a site by accident, but if yours had files there, they were served before and are no longer.
Still taken: paths under /inference/ are answered by the edge on every domain. That’s a known limit, not yet fixed.