Failed to update and/or display the timeline since yesterday, using 1.1 API

[EURO SELLER]

Hi,

Since yesterday I had encountered 502 errors from SuperTweet API using 1.1 API set via PHP curl.

I am keeping the rate limit and there is no change since the day before yesterday that the code was working.

Is there the same experience around you? Or could you please give me some suggestions, insights or hints?

[David Beckemeyer]

If you want help, do your homework and read the docs.

We ask users to provide the same details every time:

1. what the IP address from which you are sending the request?

2. What IP address did you get the response from?

3. Show full request and response with all headers (less authorization)

4. Does the respone include "X-TwitterAPI-Status" header? See:
http://supertweetnews.140plus.com/p/new-header-added-to-supertweetnet-proxy-responses/jIsmL

> --
> 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?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[EURO SELLER]

That was REST API service side issue. I confirmed the error had been resolved.

Thanks for all of your responses.

2013年4月17日水曜日 9時49分38秒 UTC+9 EURO SELLER:

[EURO SELLER]

Hi,

I would like to report another symptom...

After I found a SuperTweet call was successful on Site A, the same code was ported on Site B and this site's call was unsuccessful with 

502 error. Either SuperTweet proxy site or Twitter site is checking the caller's IP address with a certain algorithm?

Or it was merely caused by the server overload? 

I have no idea about this matter. Any information are welcome.

2013年4月17日水曜日 9時49分38秒 UTC+9 EURO SELLER:

Hi,

[David Beckemeyer]

Check the X-TwitterAPI-Status header and that will tell you whetehr
the response is from SuperTweet or Twitter.

http://www.supertweet.net/about/api

If the header is there, the response was proxied from Twitter,
otherwise it's from SuperTweet directly.

[Daniel]

api.supertweet.net is not responding for past hours...

ping api.supertweet.net

PING api.supertweet.net (50.18.251.175) 56(84) bytes of data.

[Mr Blog]

This issue should be resolved.