Whole npm private scope broken after unpublish of some package versions

In my company we are using npm private packages (aka private scopes) for internal stuff.We quite rely on it.​For the first time we had to unpublish some wrong package versions within our private scope @mycompany.Right after that, the WHOLE private scope @mycompany is broken and we are not able to install package withing our private scope @mycompany anymore!Our whole company is blocked!Even when trying to install private packages unrelated with unpublish, we get the following error message​​npm install @mycompany/utilnpm ERR! code E404npm ERR! 404 Not Found - GET https://registry.npmjs.org/@mycompany%2futil - Not found npm ERR! 404npm ERR! 404 '@mycompany/util@latest' is not in the npm registry.npm ERR! 404 Your package name is not valid, becausenpm ERR! 404 1. name can only contain URL-friendly charactersnpm ERR! 404 npm ERR! 404 Note that you can also install from anpm ERR! 404 tarball, folder, http url, or git url.​​Does anyone already has experienced something like that with private npm scope?​The npm support only open in 3 hours...​

Submitted March 29, 2019 at 10:16AM by yvele