UPDATE: 20 Jan 21:49 GMT-5

There appears to have been a routing issue in our provider's data center. There was a bad connection between two routers outside of the ProjectLocker-specific portion of the network but inside our data center, and traffic through those routers had problems. The resulting packet loss was significant enough to impede network speeds.

Thank you for your patience. At this time, we believe the issue is resolved but will continue to monitor. Please try your connections now and let us know via support@ if you still see performance problems.

UPDATE: 20 Jan 20:59 GMT-5

The network team has identified and tuned a possible culprit. We are testing to determine the status.

UPDATE: 20 Jan 19:05 GMT-5 

Diagnostics on the network have proved inconclusive. We're doing further diagnostics on the server to determine if there's any hardware issue.

UPDATE: 20 Jan 17:29 GMT-5

The network team is performing a more detailed physical investigation of the network to determine where there might be problems.

UPDATE: 20 Jan 17:00 GMT-5

The network team has performed an initial investigation, and we're pushing for additional checking on a packet loss issue we're seeing on some of the internal switches inside the data center and outside of our specific network.

We've been tracking a networking issue affecting some of our customers on some of our servers today (see the list of affected servers below). We are aware of this issue and are actively working to resolve it. 

We will post updates to this blog post, so please check back for status.

Affected servers:

• pl3.projectlocker.com
• git3.projectlocker.com
• svn3.projectlocker.com
• seed3.projectlocker.com
• angel3.projectlocker.com
• venture3.projectlocker.com
• equity3.projectlocker.com
• ipo3.projectlocker.com
• growth3.projectlocker.com

Thank you for your patience as we work to resolve this issue.