svn access to codeplex failing with 503 errors

Feb 2, 2016 at 8:29 PM
Edited Feb 2, 2016 at 9:52 PM
I am unable to access codeplex via svn.


Unexpected HTTP status 503 'Service Unavailable' on '/svn/!svn/bln/83772'

Additional errors:
PROPFIND request on '/svn/!svn/bln/83772' failed: 503 Service Unavailable

If this is not a new problem, but rather part of a long-standing instability with codeplex, is there any issue tracking it that has updates or diagnoses or prognoses, or any such information for us end-users? (I mean to ask, could you point somewhere? if I ought to be looking somewhere else for info.)

Thanks for any info.

Other variations observed today:

Unexpected HTTP status 503 'Service Unavailable' on '/svn/!svn/vcc/default'

Another message from an attempt to svn commit:

Unexpected HTTP status 503 'Service Unavailable' on '/svn'
Feb 3, 2016 at 2:41 PM
I received a reply in email saying that they are working on it, but with no estimate of time. I have asked if I can post the reply here, and am awaiting response.
Feb 4, 2016 at 1:25 AM

SVN is really a big issue and we've taken it as the first priority.
We will inform you when the problem is resolved.

Here is the newest SVN report:

"We already know about the issue, unfortunately there isn’t a lot we can do about it without re-writing the SVN bridge.

The problem seems to have happened after the TFS upgrade. Now we are filling the dynamic TCP ports at a high frequency and customers are not able to actually get data via SVN. Currently we are evaluating if we can get rid of the SVN part of CodePlex and recommending to customers that use SVN and report the issue that we can migrate their code to git."


Xuefei Wang
CodePlex Team