Failed error

[Dan]

Hey is anyone getting the error lately last hour?

curl -u x:x -d 'status=testing tweet' http://api.supertweet.net/1.1/statuses/update.json

failed

[Mr Blog]

We do not see general or widespread failures.

Next time, add -i to show the headers you're getting back:

curl -i -s -u x:x -d 'status=testing tweet' http://api.supertweet.net/1.1/statuses/update.json

It might also simply be a network timeout, which can happen sometimes.

[Dan]

seems whole day today again issues

curl -i -u x:ox -d 'test' http://api.supertweet.net/1.1/statuses/update.jsone

HTTP/1.1 410 Gone

Date: Sun, 08 Sep 2013 21:19:23 GMT

Content-Length: 6

Connection: keep-alive

Server: Apache-Coyote/1.1

failed

curl -u x:x -d 'test' http://api.supertweet.net/1.1/statuses/update.json

failed

anyone else having same issues?

[Mr Blog]

That means rate limiting, which means you either have a bug in your code (like an infinite loop) or you're tweeting too frequently. This is considered abuse of the API and could result in your account being blocked, so take look into it and resolve the problem with your client.

[Daniel]

Thank you for your reply, our tweets happen 3 times a hour... is that too much ? do the rate limits get lifted? I can limit the tweets to twice / hour...

--
You received this message because you are subscribed to the Google Groups "SuperTweet MyAPI Proxy" group.
To unsubscribe from this group and stop receiving emails from it, send an email to supertweet-myapi-...@googlegroups.com.
To post to this group, send email to supertweet-...@googlegroups.com.
Visit this group at http://groups.google.com/group/supertweet-myapi-proxy.
For more options, visit https://groups.google.com/groups/opt_out.

[David Beckemeyer]

That volume would not be enough. Something else must have been going
on, or a bug must have caused more frequent API accesses. Email me the
twitter username and I'll take a look.

[Daniel]

Still getting the failed... you got my email David with the username?

[Mr Blog]

I got the usermame.  Is it possible you're making these requests from a shared IP address, like via a proxy or something so to the supertweet server(s) it appears that we're getting flooded from that IP address?  Do you know the IP address you're sending from?

>> email to supertweet-myapi-proxy+unsub...@googlegroups.com.

>> To post to this group, send email to
>> supertweet-...@googlegroups.com.
>> Visit this group at http://groups.google.com/group/supertweet-myapi-proxy.
>> For more options, visit https://groups.google.com/groups/opt_out.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "SuperTweet MyAPI Proxy" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to supertweet-myapi-proxy+unsub...@googlegroups.com.

> To post to this group, send email to
> supertweet-...@googlegroups.com.
> Visit this group at http://groups.google.com/group/supertweet-myapi-proxy.
> For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "SuperTweet MyAPI Proxy" group.

To unsubscribe from this group and stop receiving emails from it, send an email to supertweet-myapi-proxy+unsub...@googlegroups.com.

[Daniel]

hello the server IP Im sending it from is www.ah.fm ... please check how many tweets go out because my script is set to twice / hour.

Thank you

To unsubscribe from this group and stop receiving emails from it, send an email to supertweet-myapi-...@googlegroups.com.

[SB]

I'm getting the 'failed' error today too, along with a 410 status.

I'm not a huge tweeter, maybe 15 a day.  Did around 12 in an hour last night though, with no issues.

[Mr Blog]

Can you provide the headers you're getting back from the server? If the 'X-TwitterAPI-Status' header is present the response is from Twitter.