Basecamp (and Campfire, Highrise, Backpack, etc.) were down for approximately 15 minutes, from 6:20pm to 6:35pm CST this evening. This was the result of our hosting provider making a mistake while hooking up a new network. As of right now, though, everything appears to be running smoothly. We sincerely apologize for that outage. We know you all depend on us to be stable and reliable, and that didn’t happen this evening. We’re doing everything we can to make sure this doesn’t happen again.

We are getting server time out messages this morning – related?

Yes, I too am getting pageloads that are either taking forever, or are not working at all. Is this related, or something else? Thanks!

Everything appears to be running smoothly on our end this morning. Our external monitoring software hasn’t reported any problems (whereas yesterday, it was spitting notifications left and right). Basecamp is loading quite quickly here. If you are having problems accessing Basecamp, please email support with details about the errors you are seeing, as well as your Basecamp account URL, browser and operating system. Thanks!

I just tried to change a person’s username/password and it took about 60 seconds before I got the “success” message.

Josh, have you tried again? There are many variables that can be involved in a slow load time. It could be a temporary glitch, it could be a temporary connection issue, it could be an ISP routing issue, it could be a network congestion issue, etc. If this continues over a longer period of time let us know. Thanks.

Jason,

We are still getting them intermittently – will let you know what happens.

We’ve had this all morning. Is there any progess on what this is and when it will be sorted out?

Matt

Hi
Just to let you know we are getting lots of proxy errors 502 at this end and the only way to proceed is to press refresh – I ended up with duplicate projects until I found out how to get around the error.

Any chance of knowing what the cause is and how long we are likely to keep getting this error?

Sarah

Yes, we’re getting lots of 502 Proxy Errors also… it’s confusing our customers no end and leading to duplicate posts.

Jason

We’re getting 502 errors also, not all the time, but fairly often.

Yes, we’re getting lots of 502 Proxy Errors also… it’s confusing our customers no end and leading to duplicate posts.

Same here

Hmm, we’re looking into this right now. Sorry for the inconvenience.

UPDATE: Should be all fixed. Please let us know if it continues. You may want to clear your browser cache to make sure you’ve cleared out the error message.

Just received Postfix errors around 5 minutes ago.

Here is the error. Just got it again:
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /clients.

Reason: Error reading from remote server

Cleared cache, restarted, cleared again, then tried. I’m still getting the error.

Mee too :(

I believe I finally tracked down the culprit of this and took care of the problem. Please do let us know if you see any more of these going forward today. Thanks for your patience.

Not noticed anything more occuring but have asked all my team to let me know if they have an error appearing from now on.

Many thanks for looking into this so promptly guys.

Cheers

Thanks Sarah.

Everything is good at our end now as well. Thanks!

We now getting 503 error while posting messages

503 Service Unavailable
No server is available to handle this request.

I’ve had periodic 503 errors this morning. The most recent being 10 minutes ago. I was able to finally login after refreshing, but it seems slower than usual.

I’ve also noticed that the email notifications for comments on a post either aren’t being sent, or are delayed.

We haven’t seen any of the 503s in the past couple of hours, but we have identified a problem that can lead to them and we’ll be correcting as soon as possible. Thanks for your patience, and please do continue to report problems that you encounter.

sewmyheadon, please send me a link to a comment that failed to send an email notification for you and I’ll look into it. You can send it directly to mark at 37signals.com. Thanks.