V1 registry API (RegistryServices.asmx) still answering three weeks after EOL

[People & Places]

The V1 Registry Services API was declared end-of-life on 31 Mar 2019 and should have gone dark. It is still taking calls — ProvisionCorporateIdentity, AmendDirectorRecord, HarmoniseGroupStructure — from at least fourteen legacy client integrations that were never migrated (see RS-12210). Every call now returns QUEUED and processes nothing: the countersigning approver mailbox is long dead, so requests simply pile up behind it and no record is created or changed. No functional harm — nothing is actioned — but an EOL service should not still be answering, least of all the reseller-tier endpoint whose authentication was supposed to be decommissioned.

[M. Ross]

It was meant to go dark on the 31st. It's still up and still answering — just parking everything in the queue behind an approver who hasn't logged in for years. Fourteen integrations never moved to V2. Nobody owns the off-switch.

[D. Pike]

Before anyone asks: NOT DNS this time. The clients resolve the endpoint perfectly — that's the whole problem. It answers, says QUEUED, and they go away happy. They'll poll a dead service till the heat death of the universe.

[(housekeeping)]

Still answering. Still QUEUED. Untouched for years on an unowned box. Left OPEN.