pyzor-users

timeout again

[Robert H. L. <la...@la...>]

$ pyzor ping
public.pyzor.org:24441  TimeoutError: 
$ traceroute public.pyzor.org      
traceroute to public.pyzor.org (188.40.77.236), 30 hops max, 40 byte
packets
1  gatekeeper.monsoonwind.com (192.168.0.1)  0.240 ms  0.271 ms  0.122 ms
2  * * *
3  te-3-3-ur10.sanjose.ca.sfba.comcast.net (68.85.190.157)  13.737 ms 
13.705 ms  13.638 ms
4  l-99-ur01.pasadena.tx.houston.comcast.net (68.85.154.141)  15.780 ms 
15.732 ms  15.666 ms
5  pos-0-4-0-0-cr01.sacramento.ca.ibone.comcast.net (68.86.90.141)  17.115
ms  17.062 ms  18.975 ms
6  pos-0-9-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.85.181)  18.919 ms 
21.324 ms  21.217 ms
7  pos-0-0-0-0-pe01.11greatoaks.ca.ibone.comcast.net (68.86.86.50)  26.259
ms  21.096 ms  26.194 ms
8  xe-9-3-0-0.sjc10.ip4.tinet.net (213.200.80.165)  26.098 ms  24.514 ms 
24.426 ms
9  xe-11-2-0.fra21.ip4.tinet.net (89.149.184.77)  191.294 ms
xe-10-0-0.fra21.ip4.tinet.net (89.149.184.85    )  188.578 ms
xe-9-2-0.fra21.ip4.tinet.net (89.149.186.181)  189.760 ms
10  hetzner-gw.ip4.tinet.net (77.67.64.18)  186.708 ms  186.627 ms  189.791
ms
11  hos-bb1.juniper2.rz10.hetzner.de (213.239.240.243)  196.182 ms  196.550
ms  200.327 ms
12  hos-tr3.ex3k5.rz10.hetzner.de (213.239.227.198)  196.711 ms  196.603 ms
198.295 ms
13  pyzor.spamexperts.com (188.40.77.236)  194.788 ms  186.375 ms  191.213
ms

Coming from 173.8.187.197

-- 
END OF LINE
--MCP

Re: timeout again

[Andreas S. <sch...@fa...>]

On Tue, 10 Nov 2009, at 02:01, Robert Hajime Lanning wrote:

> $ pyzor ping
> public.pyzor.org:24441  TimeoutError: 

My logs show timeouts (I checked only the reporting log) too
a few hours ago. Right now it seems to work!?

-- 
-- Andreas

Re: timeout again

[Dreas v. D. <dr...@sp...>]

Hi all,

Andreas Schamanek wrote:
> On Tue, 10 Nov 2009, at 02:01, Robert Hajime Lanning wrote:
>   
>> $ pyzor ping
>> public.pyzor.org:24441  TimeoutError: 
>>     
> My logs show timeouts (I checked only the reporting log) to
> a few hours ago. Right now it seems to work!?
The monitoring does show some issues last night. I presume it was 
because of changes to the machine related to the earlier issues. Should 
all be fine again! Thnx for the notifications.

Regards,

Dreas