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
John,
Chart of failed pings originating in Moab, Utah...
http://tweetprobe.tumblr.com/post/587169206
john - I just scanned DM's and tweets that were slow or had no
response from twitter - none were at top of hour - hth
This issue is resolved this morning, 20100430. Thanks @evan & @ej?
chart updated... http://tweetprobe.tumblr.com/post/551639110
Comcastbonnie confirms this is not unusual:
http://twitter.com/ComcastBonnie/statuses/13083585494
That this error happens for some and not others is not surprising.
With new focus on the Search API this type of issue can be addressed :)
Thursday 2010.04.29 - 11:33am PDT
Search API : No posted @ replies are found
I tried
from:comcastbonnie
from:al3x
from:raffi
Search web is OK.
Updated chart - hth - http://tweetprobe.tumblr.com/post/551639110
Unit = an 'internal tweet' for each null/502/503 result from the
Search API.
--
Subscription settings:
http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
I've charted the Search API over a few months...
http://tweetprobe.tumblr.com/post/551639110
I'm concerned, Raffi :)
--
Subscription settings:
http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
This issue is now fixed.
--
Subscription settings:
http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
The Search API is returning 420 code this afternoon. Did something
change at twitter? To my knowledge, nothing has changed at my location.
Thanks Raffi, though I doubt your comment will make headlines :)
--
To unsubscribe, reply using "remove me" as the subject.
I am using since_id in my app to know when to stop paging on both the
api & search api. My code expects the id to be sequential.
RT @jkalucki: Primary-Key-Density-Change-Pocalypse. Of total doom.
To unsubscribe from this group, send email to
twitter-development-talk+unsubscribegooglegroups.com o
Dean, please start a new thread. Regarding my original thread topic,
support from twitter is awesome.
Details:
Calling "http://search.twitter.com/search.json?to=mrskutcher"; through
my client app did not work until I called same link via a browser.
Once called via the browser, it works in my client app.
Why?
On Nov 15, 10:29 am, Raffi Krikorian wrote:
> personally, that's not how i would do i
Raffi,
Re: streaming API - I chatted with John about this. My take away is
the Streaming API isn't ready for a desktop client with an installed
base over several hundred users. Did I mis-understand?
I'd hope my installed base will eventually be tens of thousands.
On Nov 15, 10:26 am, Raffi Kri
Raffi, please note as soon as I tried the query below via the browser,
it slowly begins to work in the API.
On Nov 15, 10:25 am, mikawhite wrote:
> http://search.twitter.com/search?q=to:mrskutcher
Raffi,
Pls add this to a script - fails every time today.
http://search.twitter.com/search?q=to:mrskutcher
Hi Raffi,
Three issues:
1) Search API returns 15 pages in 59+ seconds. Two weeks ago this was
less than 10 seconds. I sent @ej a tweet last week.
2) 503 Service Unavailable - increasing frequency {I'm now recording a
log to examine which searches this occurs with} {seems "to:xxx" is
most frequ
The uptime of twitter search {API} has degraded to the point of making
our client app useless.
Hoping @twitter finds the issue soon.
Cameron & Marcel,
My app accessing the api also failed on the 8th or 9th. All is ok now.
On Nov 9, 4:35 pm, Cameron Kaiser wrote:
> Could it be an API issue then? The commands are being posted through
> statuses/update.json.
21 matches
Mail list logo