id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	desk	legacy_ref
59	V1 registry API (RegistryServices.asmx) still answering three weeks after EOL	People & Places	M. Ross (Infrastructure)	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.	fault	OPEN	P2		Registry Services / V1 API					Estate & Systems	RS-12040