Static delivery and edge execution differ
A static deployment returns files that were built or uploaded in advance, such as HTML, stylesheets, images, and scripts. The hosting layer delivers those files without invoking your own server-side code on every visit. That is why a static site's traffic does not appear as edge request usage in the same way.
An edge deployment executes code when a request arrives. That runtime work is counted as request usage, even when the code returns a small response. Static file delivery and edge execution can therefore show different usage for similar visitor traffic; the key distinction is whether the request runs edge code.
Check which host type is serving the route
If you expected request usage, confirm that the deployed hostname and route are attached to the edge host you configured, rather than a static host or an older deployment. Test the public URL and inspect its response behavior; the host type, not the page's visual appearance, determines whether edge code runs.
Static hosts can still consume storage or transfer capacity according to the service's plan and usage rules. A zero edge-request count does not mean the site received no visits. To measure visitor traffic, use an analytics source designed for that purpose; edge execution metrics only describe requests handled by the edge runtime.