Is API working today? cf example

lvv2_com · 2013-06-06T04:59:00.000Z

i also have this problem …and get data from http://search.twitter.com/search.json?lang=zh&q=lvv2&rpp=100&page=1..but yesterday it’s work well…something wrong with the api today!!

itsdanoc · 2013-06-06T06:02:57.000Z

Same issue here. Stopped working this afternoon.

episod · 2013-06-06T14:02:31.000Z

See this issue:

[issue:18242]

socialtwatter · 2013-06-06T14:25:02.000Z

It is not yet the 11th of June ( at least in the UK ) - so this should work. It does not work. There are many threads / tweets etc about this - with a total lack of reply from twitter - status says all is fine - clearly it is not. It’s been 28 hours now.

Please tell us WTF is going on

episod · 2013-06-06T14:32:46.000Z

The issue I reference above, that we accepted around 24 hours ago, acknowledges the issue. It is not yet resolved. This has nothing to do with API v1 retirement.

boxnumber03 · 2013-06-06T14:44:55.000Z

I have always wondered why issues like this do not get included in API Status under Current Performance and Availability Status. To me this is a significant disruption of service, yet the status says “Service is operating normally.”

boxnumber03 · 2013-06-06T14:47:55.000Z

Just want to point out that the update in Issue #1072 misleadingly assumes the problem is confined to low count/rpp values.

BadBlueNews · 2013-06-06T15:21:09.000Z

Taylor, is this addressed by moving to v1.1 API (we had that underway… but not quite there yet)? Thanks

ice1x · 2013-06-06T15:25:35.000Z

Twitter updated the doc page for twitter api yesterday (previos update on this page was on 2012-08-25). They changed the item “limitations” (see that page).
They add the following point:
“In API v1.1, the Search API requires some form ofauthentication – either OAuth 1.0A or app-only auth”
(It wasn’t in previos version of doc) WTF!

They don’t prevent us about this issue. I’m furious! Thanks twitter

ice1x · 2013-06-06T15:26:00.000Z

Twitter updated the doc page for twitter api yesterday (previos update on this page was on 2012-08-25). They changed the item “limitations” (see that page).
They add the following point:
“In API v1.1, the Search API requires some form ofauthentication – either OAuth 1.0A or app-only auth”
(It wasn’t in previos version of doc)

They don’t prevent us about this issue. I’m furious! Thanks twitter

hatchMAP · 2013-06-06T15:51:40.000Z

We’re ready to flip over an update to support the end of life on June 11th,but we still have production code using the old calls until Monday, and would love to see it working before the weekend (when our usage ramps up a little). Hope that is a possibility…

appdevuser · 2013-06-06T16:08:39.000Z

I have the same problem since this morning , no matter what keywords I am using, I only get the result as Jonas’.

Otaviopadovani · 2013-06-06T19:02:14.000Z

Man, this sucks, I’ve probably lost a job because of this problem.

episod · 2013-06-06T19:12:02.000Z

The issue currently affecting the Search API has no relation at all to API v1 retirement or moving to API v1.1. The issue affects both versions of the API equally.

That said, if you’re still using the legacy search.twitter.com API, you’re very late in migrating over to API v1.1 and have a matter of days to do so. For some applications, migrating to API v1.1 requires completely rethinking an application.

We’re continuing to resolve this issue of truncates resultsets across the search API.

PierreLeTexier · 2013-06-06T20:21:00.000Z

Even http://search.twitter.com/search.json?q=hello&rpp=5 doesnt work.
results=[ ]

VAGASFB · 2013-06-06T23:53:25.000Z

@episod,
although there are some threads about this outage, the noise is far less than I could imagine.
Is this interruption spread to all Twitter´s clients, or are there any technical mean to circunvent the issue?

As your last post in this thread, I am assuming that V1 and V1.1 are out.
Yes I am late to trasition to V1.1 :-), then I can not assert that V1.1 is not working, but in my tests it is not working.

Thanks

socialtwatter · 2013-06-07T11:28:28.000Z

All working nicely again - thanks [ though I think it was a little misleading to have search showing as no issues on the status page during all this ]

now just some quick patching before tuesday - as had not previously realised the unauthed search api was getting removed with version 1 api - or that this would take out the old twitter off the shelf javascript widgets - ho hum

I guess the lack of noise would suggest that most people have moved off of the old search api [or didn’t realise what the problem was ?]

Ta,
AJ

boxnumber03 · 2013-06-07T13:56:25.000Z

I wish someone (Taylor?) would explain how the API Status page works? If issues like this one do not qualify, what does qualify?

AJ,
This issue affected both the old Seach API and the new version 1.1 API for search/tweets. So, the API does not explain the lack of noise. The search/tweets API was never fully out of commission. I think most requests worked. Maybe that’s why the issue never made it to the API Status page.

episod · 2013-06-07T14:19:24.000Z

The service we use to monitor API health doesn’t have knowledge about the nature of the actual results it’s getting back. It’s just looking for the equivalent of HTTP 200-series codes instead of 50X series or 40X series. Since the Search API was functioning normally from a HTTP standpoint, it wasn’t able to detect that anything else was amiss.

boxnumber03 · 2013-06-07T14:24:57.000Z

Thanks!