Unable to create a Developer Support case - Contact Us form resets with no Case ID

Hello Amazon Developer Community team,

I am trying to contact Appstore Developer Support through the Contact Us form regarding a private account identity verification issue. I am not asking for any identity verification details to be reviewed publicly.

Each time I complete and submit the Contact Us form, the page returns to a blank or new Contact Us form. I receive:

  • No submission confirmation
  • No confirmation email
  • No Case ID
  • No case appears in My Appstore Cases

I have already tried different browsers and devices, incognito mode, clearing cache and cookies, disabling browser extensions, changing the network connection, using the English interface, and submitting plain text without attachments. The result is always the same.

Because the form does not create a case, I currently have no private channel through which to request assistance.

Could a community moderator please advise how I can create a valid private support case, or help notify the Developer Support team that the Contact Us form is failing to generate a Case ID?

I understand that identity verification details cannot be discussed in the public community. I will provide any account-specific or identity-related information only through an official private support channel.

Thank you.

Hello,

Thanks for posting. We can confirm that case 21311472981 was successfully created on 7/24/2026. Please let us know if the issue persists.

I’m having the same issue

Hello,

Could you please share the steps you followed to create the contact-us case — including the URL you used and the categories you selected from the drop-down menus — and we’ll investigate further.

Thank you.

Literally just trying to go to the “Console” tab when logged in issues a “404 Page not found”:

https://developer.amazon.com/settings/console/registration?return_to=/settings/console/home

Same with trying to “Complete Registration” from the red arrow on my initials in the top right:

Please advise.

Jason

Could you try clearing your browser cache and attempting again?