Maintenance: Router Maintenance: Thursday, February 6, 2014 (02/06/2014) Start Time: 06:00 AM UTC End Time: 12:00 PM UTC [Completed]

Date / Time: Thursday, February 6, 2014 (02/06/2014) Start Time: 06:00 AM UTC End Time: 12:00 PM UTC 

Services affected: api*, bugz*, dav*, git*, hostdeploy*, ldap*, svn*, teamforge*, trac*

Description: Our hosting service provider will be performing routine maintenance on their routers.  There may be possible network interruption for any of the servers above, but should last no longer than 30 minutes for each service.

Update : Our upstream service provider has completed the scheduled maintenance. All the services should be accessible now. However, if you still have any related issues please feel free to file a support ticket to us. We will gladly assist you in further. Thank you for your patience.

Have more questions? Submit a request

25 Comments

  • 0
    Avatar
    Davin Arakaki

    is this happening right now?

  • 0
    Avatar
    Talha Asad

    I am very disappointed with your GIT servers. They are not accessible every other day. Cloud services are suppose to be robust!

  • 0
    Avatar
    Eyelock SVN Administrator

    We are facing access issues... is it due to this maint ?

    Unable to connect to a repository at URL

    'https://xxxxxxxxxxxxxxxxxx'
    OPTIONS of
    'https://xxxxxxxxxxx':
    could not connect to server (https://xxxxxxxxxxxx)

  • 0
    Avatar
    Luca Vezzadini

    Guys,

    it's been days now since we've had serious problems with your services. If this is not going to end we'll have to switch to a different provider, no doubt.

    Can you provide us with a clear plan of service outages at least? Or are we bound to live with random outages for the days to come?

        Luca

     

  • 0
    Avatar
    Laragon Temp

    We cannot connect to our SVN repository. It's been at least 45 minutes for us...

  • 0
    Avatar
    Kallol Netherlands

    Cannot connect to SVN server anymore, getting the following error:
    Error: Unable to connect to a repository at URL
    Error: 'https://XXXXX.svn.cloudforge.com/portal'
    Error: OPTIONS of 'https://XXXXX.svn.cloudforge.com/portal': SSL handshake failed: A
    Error: connection attempt failed because the connected party did not properly respond
    Error: after a period of time, or established connection failed because connected
    Error: host has failed to respond.
    Error: (https://XXXXXXX.svn.cloudforge.com)

    Is this also due to the maintenance?? If yes, do you know when will it be over??

  • 0
    Avatar
    Luca Vezzadini

    We've been stuck all morning (with Git)...

  • 0
    Avatar
    James Heliker

    Our SVN services have been down longer than the specified 30 minutes. Any word on when it will come back up?Thanks!

  • 0
    Avatar
    Harbinder Singh

    This is the second day in row , since yesterday evening. It is really frustrating , please provide a clear plan of service .

  • 0
    Avatar
    Simon Quantrill

    Still got problems here gues im going to have to wait till 12:0o pm!! take a day of work and go relax by the pool!

  • 0
    Avatar
    Jens Aggergren

    Wait so this was posten jan 15? why didn't we get a mail alert about this maintenance window?!

  • 0
    Avatar
    James Heliker

    I understand that maintenance windows can't always be precisely timed, however PLEASE try to be accurate if you're going to give a "should last no longer than..." statement. This is wreaking havoc for my business, the extended delay couldn't have happened on a worse night. We would have made other preparations if my team had expected to be unable to reach SVN for the full six hours instead of 30 minutes.

  • 0
    Avatar
    Ashok

    Hi All,

     

    Please accept our apologies for the inconvenience caused. Our infrastructure team is in discussion with our upstream provider regarding the maintenance duration. We will keep you posted with more details once I have an update internally. Thank you for your patience.

    Thanks,

    Ashok.

  • 0
    Avatar
    Luca Vezzadini

    Totally agree with James here. The problem is not how long in advance you can warn us but how long this outages are lasting, While 30 minutes is already a lot bat can be accepted, what's been going on today (and also the days before) is not, sorry.

  • 0
    Avatar
    Riccardo Corsi

    +1 for jheliker comment

  • 0
    Avatar
    Davide Montorio

    We're experiencing the same problems, but since two days!

  • 0
    Avatar
    Jesper Rasmussen

    When will the european svn service be up again?  

    At 12 PM UTC (as written in the post) or at 12 AM UTC (as we hope) ???

     

     

  • 0
    Avatar
    Ming Yan

    Should we still expect SVN to be back online @12PM UTC? Less than 1 hour away? Please update.

  • 0
    Avatar
    Codesion Master

    Could we please have an update, SVN has been down since 9.30 UK time.

  • 0
    Avatar
    Pascal Morin

    Someone on Cloudforge side can please write an update about the Git service status?

  • 0
    Avatar
    Tom Chiverton

    3rd or 4th day in a row some part of CloudForge has been off-line for hours. 3 hours and counting with no Trac today :-(

  • 0
    Avatar
    Ashok

    Hi Alessandro,

    We have just got an update from our upstream provider that the maintenance has been completed. All the services should be accessible in with in the next few minutes. However, if you still have any connectivity issues please file a support ticket.

    Thank you,

    Ashok.

  • 0
    Avatar
    Jiri HAJEK

    30 minutes max? It's already more than 3 hours today and some more outages in the past days! There's obviously something terribly wrong and there's absolutely no info from Cloudforge. Is this a serious business or what?

  • 0
    Avatar
    Ufficio Tecnico

    Also we were still down  more than three hours, we have the standard license.

    someone who uses the licensed professional (sla 99.9) was operating or had the same problem?

    if it was operating properly, we can evaluate the upgrade...

     

  • 0
    Avatar
    Ashok

    Hi Jiri,

    I have tested your repository from the back-end and it is up and accessible . Please do file a support ticket with the complete error message if you still have this issue. We will gladly assist you.

     

Article is closed for comments.