Well I think I've fixed it.  Not sure what the problem was, but restarting a
few things on the server made the errors go away.  Very odd.  We'll see if
it comes back.

Jesse

On Sun, Oct 25, 2009 at 1:48 AM, Jesse Stay <jesses...@gmail.com> wrote:

> I'm sending from Slicehost.  Not seeing any roadblocks of any sort.  FWIW
> my other Slicehost servers sending calls to Twitter are working just fine.
>  It seems to be just this specific IP.  Here's my Traceroute:
>
> traceroute to twitter.com (128.121.146.100), 30 hops max, 60 byte packets
>  1  174-143-24-2.slicehost.net (174.143.24.2)  4.000 ms  4.000 ms  4.000
> ms
>  2  core7-aggr511a-1.dfw1.rackspace.net (98.129.84.148)  0.000 ms  0.000
> ms  0.000 ms
>  3  98.129.84.180 (98.129.84.180)  0.000 ms  0.000 ms  0.000 ms
>  4  12.87.41.177 (12.87.41.177)  4.000 ms  4.000 ms *
>  5  cr2.dlstx.ip.att.net (12.122.138.118)  4.000 ms  4.000 ms  4.000 ms
>  6  dlstx01jt.ip.att.net (12.122.80.101)  24.001 ms  24.001 ms  24.001 ms
>  7  192.205.35.118 (192.205.35.118)  140.008 ms * *
>  8  ae-1.r20.dllstx09.us.bb.gin.ntt.net (129.250.4.37)  4.000 ms  0.000 ms
>  0.000 ms
>  9  as-1.r20.asbnva02.us.bb.gin.ntt.net (129.250.3.43)  40.003 ms  48.003
> ms  40.002 ms
> 10  xe-2-3.r00.asbnva02.us.bb.gin.ntt.net (129.250.3.63)  140.008 ms
>  140.008 ms  140.008 ms
> 11  * * *
> 12  * * *
> 13  * * *
> 14  * * *
> 15  * * *
> 16  * * *
> 17  * * *
> 18  * * *
> 19  * * *
> 20  * * *
> 21  * * *
> 22  * * *
> 23  * * *
> 24  * * *
>  25  * * *
> 26  * * *
> 27  * * *
> 28  * * *
> 29  * * *
> 30  * * *
>
> On Sun, Oct 25, 2009 at 12:36 AM, Michael Steuer <mste...@gmail.com>wrote:
>
>> Rate limits generate specific http error codes when met, not connection
>> resets... I'm assuming you, Twitter or someone in the middle is experiencing
>> some sort of network related issue. Have you tried tracerouting to Twitter
>> and see if you hit any roadblocks on the way?
>>
>>
>>
>> On Oct 24, 2009, at 10:02 PM, Jesse Stay <jesses...@gmail.com> wrote:
>>
>> This is a whitelisted account on a whitelisted IP so I don't see how it
>> could be a rate-limit.  It's using basic auth - is there an easy way to use
>> oAuth for whitelisted accounts?  This has worked for the last year or so up
>> until today.
>>
>> Jesse
>>
>> On Sat, Oct 24, 2009 at 10:20 PM, Atul Kulkarni <<atulskulka...@gmail.com>
>> atulskulka...@gmail.com> wrote:
>>
>>> Are you using Basic Auth? Are you using the same account to tweet and are
>>> u tweeting simultaneously while working? If none of the above then u have
>>> reached ur rate limit. Wait for an hour and try again. Else I don't
>>> understand what could have happened. I had this a few days back and reason
>>> was rate limit.
>>>
>>> On Sat, Oct 24, 2009 at 11:16 PM, Jesse Stay < <jesses...@gmail.com>
>>> jesses...@gmail.com> wrote:
>>>
>>>> I'm seeing constant Connection Reset by Peer errors on one of my
>>>> servers.  Is anyone else seeing this?  Have I hit a limit of some sort?
>>>>  It's been happening all day long it seems.
>>>>
>>>> Jesse
>>>>
>>>
>>>
>>>
>>> --
>>> Regards,
>>> Atul Kulkarni
>>> <http://www.d.umn.edu/~kulka053>www.d.umn.edu/~kulka053
>>>
>>
>>
>

Reply via email to