Sonatype has finally responded to the issue opened on the Jira Maven Central [1.] to configure the smart proxy. This needs to be configured on high priority to make sure our release repositories staging repositories do not get removed.

[1.] https://issues.sonatype.org/browse/MVNCENTRAL-4961

"

Recent instability with OSSRH has warranted further investigation into this issue. As of this moment, it appears that approximately 45% of all closed staging repositories on oss.sonatype.org belong to opendaylight.org. As Joel mentioned above, large numbers of unused staging repositories can severely impact the performance of oss.sonatype.org. Other users are now beginning to notice and are issuing complaints about service degradation requiring that we take action on this immediately. 

We request that you remove excessive (more than 10) staging repositories as soon as possible, otherwise we may be forced to drop these staging repositories and prohibit access until your development and deployment process is modified.  

In situations like yours, we recommend syncing releases directly from your public Nexus instance (nexus.opendaylight.org) to Central.  This would seemingly allow your current release process to be maintained and significantly reduce load on our servers. Please see the following URL for instructions on how this is configured: 

https://central.sonatype.org/pages/central-sync-with-nexus-smart-proxy.html

"