SF.net Operations

@sfnet_ops

Service Outage and other informational alerts. For support, see ticket/IRC/email information on

globally distributed
Joined March 2009

Tweets

@sfnet_ops is blocked

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @sfnet_ops.

  1. We are back at full capacity.

  2. The site will be is currently doing some maintenance. We'll be We are back at full capacity soon

  3. We are back at full capacity.

  4. Maintenance work has concluded successfully, all services operating normally at this time.

  5. The site will be in read only mode during a maintenance window from 23:00-01:00 UTC

  6. full service restoration complete, details at

  7. temporarily running from DR environment while we rebalance I/O

  8. service outage update at

  9. will be put into static read-only DR mode for an hour to allow for some planned maintenance. Developer services will be offline

  10. Subversion for j* projects are offline pending restoration. For more info read this:

  11. update on service restoration,

  12. Mercurial (Hg) service online. Work continues 24x7 on file upload and CVS/SVN/Bzr.

  13. project web (except k* projects), VHOSTs, user web (except b* users), DB are online. Working 24x7 on service restoration.

  14. Git service restored. Work continues 24x7 on project web, file upload service, and other SCMs.

  15. has posted 7/22 update on infra and service restoration,

  16. mailing list services online. Work continues 24x7 on file upload, project web, SCM services. Next full update today (7/22).

  17. Tickets, wiki, forums, mail archives are now up. Code repos, project web, uploads to come. Last update details:

  18. Latest update on service restoration at

  19. directory, download and project summary pages are back online; dev services (SCM, uploads, ML's, project web) pending restoral

  20. down due to storage platform bug, working 24x7 on recovery and data validation, service restoral. Slashdot restored

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·