Subdomain intermittently serves a deleted site's usage_exceeded page (2+ days) - glowmora-beauty.netlify.app

Support
1

My subdomain glowmora-beauty.netlify.app belongs to project glowmora-beauty (project ID cabbd883-e30f-4382-8248-f02e605f3120, team elivate14) with a successful production deploy, but for 2+ days requests have been intermittently returning a 503 usage_exceeded / “Site not available” page from a previous, now-DELETED site on another team that once held this name.

Timeline:

  1. My old team (isaiahdelgado14-spec) hit its free-tier credit limit and was paused.
    1. I created a new team (elivate14), the old site was renamed to free the name, and I claimed it: sites:create --name glowmora-beauty succeeded, then deployed via CLI.
      1. The old renamed site was then fully deleted from the old team.
        1. Since then the subdomain flaps: some requests serve my live site (200), others serve the deleted site’s stale “usage_exceeded” page (503). Two clients on the same machine consistently get different results at the same time.
      3. Evidence:
      • The unique deploy URL always works: https://6a5aeb6b6657f16d09b5de06--glowmora-beauty.netlify.app
        • getSite API confirms my project owns the name (state: current/ready, default_domain glowmora-beauty.netlify.app)
          • My new team is healthy (270/300 credits available)
            • Sample stale request IDs: 01KXSJH3GRK5XASKTTGGY6KXMM, 01KXSJ9T3KZX8KVFN4D1MHWCG3
          • Could you please purge the stale routing/mapping for glowmora-beauty.netlify.app so it consistently serves project cabbd883-e30f-4382-8248-f02e605f3120? This URL is printed on business cards (QR code), so I’d really appreciate a fix. Thank you!
2

Update ~21h later: the situation has degraded from intermittent to (currently) fully stale — 10 out of 10 requests from my location now return the deleted site’s usage_exceeded 503 page. The unique deploy URL still serves the site correctly, and getSite still shows my project (cabbd883-e30f-4382-8248-f02e605f3120) owning glowmora-beauty.netlify.app with state current/ready. Would really appreciate a purge of the stale mapping when someone gets a chance. Thanks!

3

Update — day 3, and it’s now consistently broken (was intermittent, now 10/10 requests return the deleted site’s usage_exceeded 503). Re-confirmed today: the unique deploy URL serves my site fine (200), and getSite shows my project (cabbd883-e30f-4382-8248-f02e605f3120, team elivate14) owns glowmora-beauty.netlify.app with state current/ready. My team has 270/300 credits — this is purely stale routing from the deleted old site, not my usage. Could a staff member please purge the stale mapping? It’s on printed business cards, so any help is hugely appreciated. Thank you!

4

@hrishikesh sorry to tag you directly — hoping you or another support engineer can help. My subdomain glowmora-beauty.netlify.app has been stuck for ~3 days serving a deleted site’s usage_exceeded 503, even though my project (cabbd883-e30f-4382-8248-f02e605f3120, team elivate14) owns the name with a healthy deploy and 270/300 credits. The unique deploy URL works fine (200). It’s printed on business cards, so a purge of the stale routing would mean a lot. Thank you!