View Full Version : Autopatch server down?
ByteMe
12-12-2007, 02:20 AM
Is anone else having problems with connecting to the autopatch server?
ByteMe
12-12-2007, 06:41 AM
Tracing route to 212.214.41.165 over a maximum of 100 hops
1 4 ms 1 ms 1 ms x.x.x.x
2 15 ms 6 ms 8 ms 73.208.248.1
3 10 ms 8 ms 9 ms 68.85.250.37
4 11 ms 9 ms 9 ms 68.85.244.101
5 15 ms 9 ms 9 ms 68.85.244.98
6 14 ms 11 ms 12 ms 68.85.244.130
7 18 ms 18 ms 22 ms COMCAST-IP.edge3.Dallas1.Level3.net [4.71.198.10
]
8 44 ms 45 ms 42 ms xe-11-3-0.edge3.Dallas1.Level3.net [4.71.198.9]
9 55 ms 53 ms * vlan89.csw3.Dallas1.Level3.net [4.68.19.190]
10 45 ms 51 ms 54 ms ae-83-83.ebr3.Dallas1.Level3.net [4.69.136.161]
11 44 ms 50 ms * ae-7.ebr3.Atlanta2.Level3.net [4.69.134.22]
12 60 ms 55 ms 55 ms ae-2.ebr1.Washington1.Level3.net [4.69.132.86]
13 68 ms 56 ms 55 ms ae-91-91.csw4.Washington1.Level3.net [4.69.134.1
42]
14 60 ms 72 ms 56 ms ae-93-93.ebr3.Washington1.Level3.net [4.69.134.1
73]
15 72 ms 72 ms 72 ms ae-3.ebr3.NewYork1.Level3.net [4.69.132.90]
16 66 ms 72 ms 72 ms ae-63-63.csw1.NewYork1.Level3.net [4.69.134.98]
17 65 ms 64 ms 62 ms ae-13-69.car3.NewYork1.Level3.net [4.68.16.5]
18 65 ms 62 ms 64 ms TDC-SOLUTIO.car3.Level3.net [4.78.182.10]
19 164 ms 164 ms 163 ms pos0-0-1-0.9953M.boanqh1.ip.tele.dk [83.88.26.10
5]
20 * * * Request timed out.
21 * * * Request timed out.
22 167 ms 163 ms 166 ms tge2-1.krs2-p2.mmx.se.sn.net [88.131.143.17]
23 166 ms 164 ms 343 ms 88.131.143.135
24 512 ms 296 ms 296 ms tge1-3.cty-pe3.kid.se.sn.net [88.131.143.172]
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 165 ms 164 ms 163 ms tge1-3.cty-pe2.rby.se.sn.net [88.131.143.156]
29 166 ms 162 ms 166 ms tge1-3.gba-pe2.klk.se.sn.net [88.131.143.152]
30 165 ms 163 ms 163 ms 62.95.55.26
31 * * * Request timed out.
.
.
.
100 * * * Request timed out.
Trace complete.
For some reason it never gets past 62.95.55.26. Any ideas?
NightTwix
12-12-2007, 08:32 PM
for me the trace works for the last hop as well
can you ping the 212.214.41.165 ?
ByteMe
12-13-2007, 07:47 AM
No, couldn't ping either. It was apparently a routing issue and has been fixed now.
WooHoo! :guitar: :guitar: :guitar:
Thanks NT
vBulletin® v3.8.7, Copyright ©2000-2024, vBulletin Solutions, Inc.