Is the Ads API down? Getting error messages from Twitter

ads
ton-upload

#1

@jillblaz FYI can you help us with this?

I’m getting the following error when trying to access Ads API:

Cannot get data from host:
Request: 38200 * Client out-bound request
38200 > GET https://ads-api.twitter.com/0/accounts/18ce53wrop9/targeting_criteria?line_item_id=3lagc

Response: 38200 * Client in-bound response
38200 < 503
38200 < date: Thu, 31 Mar 2016 19:43:01 GMT
38200 < server: tsa_a
38200 < content-length: 158
38200 < x-response-time: 13
38200 < x-frame-options: SAMEORIGIN
38200 < x-transaction: d1b52e2cb54fe3bf
38200 < strict-transport-security: max-age=631138519
38200 < set-cookie: guest_id=v1%3A145945338114403672; Domain=.twitter.com; Path=/; Expires=Sat, 31-Mar-2018 19:43:01 UTC
38200 < x-xss-protection: 1; mode=block
38200 < x-content-type-options: nosniff
38200 < content-disposition: attachment; filename=json.json
38200 < x-connection-hash: 6a87c3eb467af5f62f3b1b95d6ac431b
38200 < x-access-level: read-write
38200 < x-runtime: 0.003285
38200 < content-type: application/json;charset=utf-8
38200 < connection: close
38200 <
{“errors”:[{“code”:“SERVICE_UNAVAILABLE”,“message”:“Service unavailable due to request timeout; please try the request again later”}],“request”:{“params”:{}}}

Removed token authorization, but the rest of the transaction is intact

This has been happening for most of the day today


#2

Hi @lkamitakahara,

That is quite normal, It depends on the day and the workload that Twitter Ads API server has.

I usually get that error (and another with null response) more or less from 10 to 15 times a day. Some days 0,

Regards,


#3

Thanks for the response @hector_borras, is there anyway to see if this is happenning more often today? We cancelled a product release because we can’t complete test cases to see if the release is working properly today. Where can I find out if this is an actual production outage?


#4

Nothing especial today in my case. The only significant issue I can see is 2hours ago I saw 4 503 errors in 10 minutes, but nothing relevant in our case. It happens tu us when we retrieve statistics.

What I do un our solution is to make a attempts strategy. We tray up to 3 times if the same request returns that error.


#5

@hector_borras We had this issue a couple of days ago. We had several “Internal Server Errors” reported when attempting to create a campaign.


#6

That’s way we use our attempts strategy, in order to solve this issues @msbukkuri.

As I read many months ago, from Twitter staff, this is due an server overload


#7

Hi there! Did any one of you ever experience SSL connect error errors?


All lists getting stuck in processing
#8

Nothing here @majoritasdev

All works perfect :smiley:


#9

We are also experiencing a high amount of errors starting yesterday. Additionally it looks like the v0 stats api rate limit is limiting us to 15 minutes where it used to be 1 minute intervals. They changed it to a single minute a while back.
It seems like they might have messed up something with v0 when they turned on v1 yesterday.