Very slow response with API from Slicehost

[Hwee-Boon Yar]

I have been having these very slow API response running on Slicehost
(most of the time way more than 2-3 seconds) for the past 2 days. Is
this something being actively worked on?

It's becoming really painful that people are telling me my app doesn't
work.

--
Hwee-Boon

[Josh Roesslein]

I just did a few tests on my slicehost VPS and the delay seems okay
here. 2-5 seconds range which is about the same I'm getting locally.

Are all API endpoints slow for you or just a select few?

Josh

[RandyC]

I have been seeing enormous numbers of 502's and 500's for API calls
from Qwest DSL business, Rackspace, and Amazon Cloud instances since
Saturday through today. Working through the UI to log into accounts
is equally painful with constant fail whales after two to three
attempts. Seems like a couple of bad hair days so far and very
difficult to get much done. I'm surprised more people aren't talking
about this unless we're the only ones affected.

[Andrew Badera]

What's there to talk about? What can we do? As always we're at
Twitter's mercy and the status blog is 3 days out of date.

I've definitely been seeing them too. Not horrible today, but a pretty
steady stream really since mid-last week I believe.

∞ Andy Badera
∞ +1 518-641-1280
∞ This email is: [ ] bloggable [x] ask first [ ] private
∞ Google me: http://www.google.com/search?q=andrew%20badera

[Hwee-Boon Yar]

2-5 secs for a /help/test.format or getting DM/Mention timeline is
certainly not OK.

And thanks for confirming I'm not alone.

--
Hwee-Boon

[Hwee-Boon Yar]

On Oct 22, 12:05 am, RandyC <bioscienceupda...@gmail.com> wrote:
>  I'm surprised more people aren't talking
> about this unless we're the only ones affected.

Me too. Which is why I'm posting it here. No one else seems to be
complaining. I was beginning to wonder I was alone.

--
Hwee-Boon

[Michael Steuer]

No, seeing the same since Saturday. @rsarver said on Sunday morning he would
post information to the group once they knew what was causing all this, but
I guess 4 days later they still don't know, as we haven't heard anything...

[Hwee-Boon Yar]

Like I have mentioned privately to someone:

"Can I then make a next best suggestion that is most easy to implement
and yet effective? It has been suggested more than once. Post an
update to status.twitter.com. Even a short message. Give us something
to retweet, to forward to users. If you want to know the impact on 3rd
party developers, go to iTunes App Store on your iPhone (I assume you
use one) and read the top few reviews for SimplyTweet. They mention
performance problems and loading errors of SimplyTweet. <snip>. Tell
me how this doesn't hurt us?

Do you not agree that not posting updates under situations like this
(where you know it has been under heavy load for a couple of days)
reflects policy rather than lack of 3rd party developer support
resources? If fact, I'll be blunt and say that this policy directly
suggests to me, as a 3rd party developer, that Twitter doesn't care
about us and is even letting us help shield Twitter from user
complaints."

--
Hwee-Boon

On Oct 22, 12:29 am, Michael Steuer <mste...@gmail.com> wrote:
> No, seeing the same since Saturday. @rsarver said on Sunday morning he would
> post information to the group once they knew what was causing all this, but
> I guess 4 days later they still don't know, as we haven't heard anything...
>

[Ryan Sarver]

Guys,

Thanks for the reports. We are aware of the elevated 50xs and are
working hard to bring it back down to normal. I don't have a specific
timeline that I can give at this point, but we'll update you regularly
if this continues.

I've update @twitterapi with the latest status as well:
http://twitter.com/twitterapi/status/5047567434

As for the follow up regarding this weekends issue, we are still
committed to giving that report, but we haven't gotten all the details
yet. We will update the list when we can produce a full issue report.

Thanks, Ryan

[Dean Collins]

Any reason why the official status page wasn't updated?

http://status.twitter.com/

Based on your last post it appears everything got fixed over the weekend....which we all know it didn't.

Cheers,

Dean

[Dewald Pretorius]

I'm getting between 3 and 10 502's per second, with an added bonus of
about 1 connection refused per second.

Over-worked and under-staffed. That's how I would diagnose the
symptoms, such as our complaining about bad system performance and
poor communication. One human being can only do so much and then the
rest of the tasks land on the floor.

Dewald

On Oct 21, 1:08 pm, Andrew Badera <and...@badera.us> wrote:
> What's there to talk about? What can we do? As always we're at
> Twitter's mercy and the status blog is 3 days out of date.
>
> I've definitely been seeing them too. Not horrible today, but a pretty
> steady stream really since mid-last week I believe.
>
> ∞ Andy Badera
> ∞ +1 518-641-1280
> ∞ This email is: [ ] bloggable [x] ask first [ ] private
> ∞ Google me:http://www.google.com/search?q=andrew%20badera
>