Hi Glenn,
Sounds like a good idea. It would be nice to have some sort of
monitoring on the API. It would make it easier to determine where
something is going wrong.
Someone just mentioned http://api-status.com/ which seems to go into
the direction you propose, even for several APIs.
Also see
John,
can you already tell us something about the latency issue?
Is it your opinion that the many connect failures I am seeing are
something on my end? Or could that be correlated with the timeouts?
Thanks,
Jaap
You might want to take a look at the service that Apigee provides at
apigee.com, Glenn.
Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod
On Tue, May 11, 2010 at 1:21 AM, glenn gillen gl...@rubypond.com wrote:
On May 11, 4:45 am, John Kalucki j...@twitter.com wrote:
It's probably on our end. I'll post some advice.
On Wed, May 12, 2010 at 12:24 AM, Tjaap jdmeij...@gmail.com wrote:
John,
can you already tell us something about the latency issue?
Is it your opinion that the many connect failures I am seeing are
something on my end? Or could that be
FWIW, our application has been experiencing these same issues for
several weeks now. I've seen repeated overcapacity errors being
returned (the too many tweets HTML page) on both GET and POST
requests. I don't have specifics on likely times of the day, though US
Central nighttime seems much less
On May 11, 4:45 am, John Kalucki j...@twitter.com wrote:
Now that we have a reasonable idea about what is transpiring, I'd
venture to say that the latency distribution will be widest between
about 6:30am to 10:30am PDT (13:30-17:30 UTC), and considerably less
so until perhaps 5pm PDT. The
I’m also seeing a ~5 second delay in responses to requests for
http://api.twitter.com/1/statuses/user_timeline.xml.
It’s consistently 5-7 seconds, but appears to happen both before the
response is sent as well as midway, it sort of feels like both a
timeout waiting for something to happen as well
John,
Chart of failed pings originating in Moab, Utah...
http://tweetprobe.tumblr.com/post/587169206
delayed tweet:ping traceroute
64 bytes from 128.242.240.61: icmp_seq=9 ttl=244 time=36.851 ms
--- api.twitter.com ping statistics ---
10 packets transmitted, 8 packets received, 20% packet loss
round-trip min/avg/max/stddev = 36.851/37.725/39.607/0.902 ms
We're pretty sure that this isn't a connectivity issue. At least, it's
not *just* a connectivity issue.
-John Kalucki
http://twitter.com/jkalucki
Infrastructure, Twitter Inc.
On Mon, May 10, 2010 at 2:06 PM, mikawhite mikawh...@me.com wrote:
delayed tweet:ping traceroute
64 bytes from
Hi John and Ryan,
Thanks for looking into this.
The good news is that now I am seeing faster responses for my
website.
I did not change anything on my end, but maybe you guys did, or the
traffic was more well-behaved :)
In any case, here are my impressions of using the twitter APIs.
Use case:
Now that we have a reasonable idea about what is transpiring, I'd
venture to say that the latency distribution will be widest between
about 6:30am to 10:30am PDT (13:30-17:30 UTC), and considerably less
so until perhaps 5pm PDT. The balance of the day should be OK.
-John Kalucki
Hi, sorry I didn't get back to you earlier. I was only monitoring this
thread:
http://code.google.com/p/twitter-api/issues/detail?id=1543
Right now about 10% of our post fails immediately. Latency is between
0.7s and 3s, with peaks to 7 or 8 seconds.
We are not logging tcp dumps at the moment,
The friend I am developing the app with, tells me that we can't log
tcp traffic ourselves. We'd have to get our host provider involved.
What I do have, is the logfile of updates:
http://dl.dropbox.com/u/6030727/httpresponse_latency.xls
I started this log on Friday. As you can see the
When you say that 10% fail immediately, do you mean that 10% fail in
less than a second? What is the failure indication? This sounds a lot
like a problem on your server, perhaps a shared resource exhaustion --
connections, memory, file descriptors, etc.
I see the similar latency from here in San
Where are your servers located geographically? If you don't see an
hourly correlation, do you see a strong time-of-day correlation or
day-of-wee correlation?
Can you run a ping from your servers during a period of instability
and send the summary at the end of the run?
On Sat, May 8, 2010 at
Same questions for everyone having issues: Where are your servers
located geographically? If you don't see an hourly correlation, do you
see a strong time-of-day correlation or day-of-wee correlation?
Can you run a ping from your servers during a period of instability
and send the summary at the
Our servers are in Amsterdam, in the Netherlands. Response time varies
a lot. When I ping www.twitter.com from the server, this is what I get
back:
PING twitter.com (168.143.162.68) 56(84) bytes of data.
2 packets transmitted, 2 received, 0% packet loss, time 1014ms
rtt min/avg/max/mdev =
We see the same huge latency and timeouts as well (our timeouts are
also at 30 seconds).
We running out of a US data center on multiple machines, we see this
issue on all if our servers.
I agree with @tjaap, would like to hear twitters reaction as well.
On May 7, 6:02 pm, Tjaap
Raj, Naveen, @tjaap,
Do any of you still have tcp dumps of the calls you were making that were
getting long timeouts?
On Sat, May 8, 2010 at 12:08 AM, Naveen Ayyagari
nav...@getsocialscope.comwrote:
We see the same huge latency and timeouts as well (our timeouts are
also at 30 seconds).
We
Any chance that the timeouts are correlated with the top of the hour?
-John Kalucki
http://twitter.com/jkalucki
Infrastructure, Twitter Inc.
On Sat, May 8, 2010 at 12:08 AM, Naveen Ayyagari
nav...@getsocialscope.com wrote:
We see the same huge latency and timeouts as well (our timeouts are
john - I just scanned DM's and tweets that were slow or had no
response from twitter - none were at top of hour - hth
I dont have tcp dumps available.. Ill try to get some captures later
this weekend..
Ill also run through the logs to see if they have any correlation with
top of the hour, but my gut instinct is they do not.
Anywhere specific I should send tcp dumps, as they may contain
username and passwords of
I'm seeing exactly the same: big latency and a lot of timeouts. When
posting a tweet, Twitter sometimes does not return a response within
30 seconds. After my curl times out, the app has no way of knowing if
the post made it or not. Sometimes it will appear on Twitter and
sometimes it won't. This
24 matches
Mail list logo
