We’re hitting statusCode 7000 — “Team is not yet configured for notarization” — but not on a fresh account. One of our teams notarized successfully throughout June and July 2025, with multiple accepted submissions that were stapled and shipped. Then, in 2026, the same team started failing with 7000 with no change on our side. So this is not only a new-account provisioning gap. A team that was fully working can apparently be flipped into the 7000 state. The second unusual thing is that this is happening across multiple separate developer teams that we manage: different legal entities, different Team IDs, and different Apple IDs. They all started returning 7000 in the same window. A per-account random assignment does not explain several unrelated teams failing simultaneously. That points to a systemic backend event rather than individual account misconfiguration. For the record, on the technical side, everything checks out: Developer ID Application certificate Hardened runtime Secure timestamp codesign --verify --deep --strict passes Notarization log returns issues: null Another symptom worth noting: some of our recent submissions do not even reach a Rejected status. They sit in In Progress indefinitely and never resolve, which notarytool cannot recover from. We have opened cases through Developer Program Support. If anyone has had a previously working account recover from 7000 — as opposed to a brand-new account — I would really like to hear what finally moved it and roughly how long it took. And if Apple staff are watching: multiple unrelated teams entering this state at once seems like it should be diagnosable from your side as more than a coincidence.