Steve's comment that he's seen this over the past few days over set
timespans - in our case, the problems are most prevalent between noon
and 6PM, eastern.
Also, here's my full traceroute:
Packets
Pings
Host Loss% Snt Last
Avg Best Wrst StDev
1. 209-20-64-2.slicehost.net 0.0% 3526 0.0
0.0 0.0 292.0 10.5
2. 209.20.79.225 0.6% 3526 0.0
0.0 0.0 252.0 8.0
3. ge-6-13-115.car1.StLouis1.Level3.net 0.2% 3526 196.0
10.1 0.0 304.0 35.5
4. ae-11-11.car2.StLouis1.Level3.net 0.7% 3526 0.0
13.4 0.0 328.0 41.4
5. ae-4-4.ebr2.Chicago1.Level3.net 0.7% 3526 8.0
9.7 4.0 584.0 17.0
6. ae-2-56.edge3.Chicago3.Level3.net 0.6% 3526 4.0
9.5 4.0 304.0 21.8
7. 4.68.63.198 0.5% 3526 4.0
23.5 4.0 360.0 46.9
8. xe-0-3-0.r21.chcgil09.us.bb.gin.ntt.net 0.4% 3526 4.0
4.8 4.0 224.0 7.8
9. p64-7-0-3.r20.snjsca04.us.bb.gin.ntt.net 25.7% 3526 56.0
55.3 52.0 228.0 9.3
10. xe-1-3.r02.mlpsca01.us.bb.gin.ntt.net 11.1% 3526 52.0
68.6 52.0 564.0 44.5
11. mg-1.c00.mlpsca01.us.da.verio.net 0.4% 3526 56.0
73.2 52.0 4536. 92.4
12. 128.121.150.205 0.6% 3526 52.0
53.4 52.0 356.0 12.2
13. 128.121.146.85 0.4% 3526 56.0
57.8 52.0 512.0 18.5
14. 128.121.146.100 0.6% 3525 52.0
56.1 52.0 436.0 17.0
--Eric
On Feb 20, 2009, at 11:27 AM, Matt Sanford wrote:
>
> The times may help me do some network troubleshooting, what timezone
> is that?
>
> On Feb 20, 2009, at 08:13 AM, swggy wrote:
>
>>
>> I've been seeing the same thing - it started about 3 days ago. I
>> installed a q&d delay/retry loop to manage it and log the times on a
>> couple of API calls - rate_limit_status.json & test.json
>>
>> It seems to be mostly gone today - has only happened once so far at
>> 07:02:22.
>>
>> Yesterday this was a continual problem, with a solid burst locking me
>> out from 14:46:05 to 14:47:16 (I'm retrying every 3 seconds), and
>> ongoing from that point sporadically, at times replying with nothing
>> for 3 or 4 retries before getting a reasonable reply until 19:45:04 -
>> and other than the 1 today, no problems at all from that point.
>>
>>
>> On Feb 19, 4:53 pm, Chris <[email protected]> wrote:
>>> Howdy,
>>>
>>> I am making API calls to Twitter using PHP ('Arc90 Twitter API
>>> Client'
>>> Library) to update a users status, and about 3 out of 10 times CURL
>>> returns a HTTP status code of 0 - with no other data returned.
>>>
>>> But if I try again and again it will usually work within a few
>>> repeats. Does anyone have any ideas about this?
>>>
>>> Thanks for your help,
>>>
>>> Chris.
>
