Deleted Pages deployment hostname continues serving assets after deletion, causing confusion and potential data exposure.
Deleted Pages deployment hostname continues serving assets after deletion, causing confusion and potential data exposure.
Problem statement normalized from the linked evidence
CANDIDATE VIEW · NOT A PUBLISHED OPPORTUNITY
01
Qualification checklist
Gate decision: Aug 15, 2026
×
At least 3 independent users2 / 3
NOT MET
×
At least 2 independent discussions1 / 2
NOT MET
✓
At least 1 supporting signal1 Blocked workflows
MET
02
Observed signals
Users2
Discussions1
Mentions2
Active days1
Source coverageGitHub
TrendUNKNOWN
First seenAug 07, 2026
Last seenAug 07, 2026
Why the gate is holding
Fewer than 3 independent users
Fewer than 2 independent discussions
Competition research, commercial scoring, and Build Gap analysis do not run until this gate passes.
03
Source evidence
2 evidence records
github · HIGH · Aug 07, 2026
cloudflare/workers-sdk
> [!NOTE] > This is an automated, advisory triage report generated by workers-devprod. It is not an official maintainer response — a maintainer will follow up. 🤖 Automated triage report # Issue Triage: cloudflare/workers-sdk#15083 ## Summary A deleted Pages (Direct Upload) deployment's hash-based `*.pages.dev` hostname continues serving the deployment's static assets more than 20 hours after the deployment was successfully deleted and removed from listings. ## Classification - **Type:** Bug - **Component:** Cloudf…
### Which Cloudflare product? Pages (Direct Upload) ### Wrangler version 4.120.0 ### What happened? A Pages deployment was deleted successfully and no longer appears in either `wrangler pages deployment list` or the Cloudflare Pages deployments API. More than 20 hours later, its hash-based `*.pages.dev` deployment hostname still returns HTTP 200 and serves the deployment's original static assets. Retrying deletion with the original full deployment UUID now returns API error `8000009` (“The deployment ID you have sp…