Packet Loss at gw-hetzner.init7.net
(1/1)
zwisch:
Hi Richard,
It seems there's a lot of packet loss at gw-hetzner.init7.net and it's giving me a lot of trouble while doing problems. Is it your webhost?
Here's the traceroute log:
Code:
D:\Users\***>tracert www.chesstempo.com
Tracing route to www.chesstempo.com [176.9.45.175]
over a maximum of 30 hops:
1 2 ms <1 ms <1 ms 192.168.1.1
2 43 ms 26 ms 12 ms lo-100.lns02.tor.packetflow.ca [206.248.154.122]
3 12 ms 64 ms 29 ms 69.196.136.164
4 52 ms 28 ms 11 ms 10gigabitethernet1-2.core2.tor1.he.net [209.51.1
91.173]
5 33 ms 99 ms 33 ms 10gigabitethernet10-3.core1.nyc4.he.net [184.105
.223.173]
6 105 ms 149 ms 129 ms PAIX-NYC.init7.net [198.32.118.38]
7 150 ms 107 ms 104 ms r1lon2.core.init7.net [77.109.128.69]
8 104 ms 107 ms 114 ms r1lon1.core.init7.net [82.197.168.41]
9 124 ms 118 ms 149 ms r1nue1.core.init7.net [77.109.140.254]
10 112 ms 109 ms 110 ms gw-hetzner.init7.net [77.109.135.102]
11 137 ms * * hos-bb2.juniper2.rz15.hetzner.de [213.239.240.15
8]
12 118 ms 127 ms 135 ms hos-tr3.ex3k6.rz15.hetzner.de [213.239.244.71]
13 138 ms * 111 ms static.175.45.9.176.clients.your-server.de [176.
9.45.175]
Trace complete.
D:\Users\***>tracert www.chesstempo.com
Tracing route to www.chesstempo.com [176.9.45.175]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 39 ms 60 ms 50 ms lo-100.lns02.tor.packetflow.ca [206.248.154.122]
3 112 ms 15 ms 11 ms 69.196.136.164
4 118 ms 156 ms 142 ms gw-init7.torontointernetxchange.net [206.108.34.
62]
5 135 ms 104 ms 121 ms r1lon1.core.init7.net [77.109.140.193]
6 158 ms 149 ms 131 ms r1nue1.core.init7.net [77.109.140.254]
7 130 ms 166 ms 151 ms gw-hetzner.init7.net [77.109.135.102]
8 122 ms * 156 ms hos-bb2.juniper2.rz15.hetzner.de [213.239.240.15
8]
9 128 ms 153 ms 138 ms hos-tr3.ex3k6.rz15.hetzner.de [213.239.244.71]
10 113 ms 112 ms 146 ms static.175.45.9.176.clients.your-server.de [176.
9.45.175]
Trace complete.
D:\Users\***>tracert www.chesstempo.com
Tracing route to www.chesstempo.com [176.9.45.175]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 45 ms 20 ms 10 ms lo-100.lns02.tor.packetflow.ca [206.248.154.122]
3 12 ms 11 ms 11 ms 2150.ae3.bdr03.tor.packetflow.ca [69.196.136.163
]
4 112 ms 151 ms 121 ms gw-init7.torontointernetxchange.net [206.108.34.
62]
5 112 ms 125 ms 124 ms r1lon1.core.init7.net [77.109.140.193]
6 119 ms 148 ms 121 ms r1nue1.core.init7.net [77.109.140.254]
7 * 110 ms 121 ms gw-hetzner.init7.net [77.109.135.102]
8 * * 164 ms hos-bb2.juniper2.rz15.hetzner.de [213.239.240.15
8]
9 * * 130 ms hos-tr3.ex3k6.rz15.hetzner.de [213.239.244.71]
10 * 154 ms * static.175.45.9.176.clients.your-server.de [176.
9.45.175]
11 118 ms 113 ms 139 ms static.175.45.9.176.clients.your-server.de [176.
9.45.175]
Trace complete.
richard:
Hi Zwisch,
gw-hetzner.init7.net looks like the last hop of your packets before they arrive at my German hosting provider (chesstempo is still a few hops further down the chain from there, but all hops after gw-hetzner.init7.net definitely belong to my hosting provider). Looking at your traces, I'd guess that init7 is having congestion issues at the edge of my hosting providers network (hetzner), and that machine is init7's gateway router to hetzner. It is hard to tell from this information alone if the problem is init7 sending on the packets to hetzner or in hetzner having trouble receiving them, although the last trace suggestions init7 itself is the issue rather than the next hop down. I can try pushing my hosting provider, but they are likely to say the issue is init7's rather than theirs. Similarly your ISP is going to say something similar, "looks like an upstream problem", which is true, but doesn't help resolve the issue.
Having a look at init7's current status reports, I found this:
http://www.init7.net/en/status/&ticket=6631&utm_source=twitterfeed&utm_medium=twitter
Basically init7 is having connectivity problems into Germany, they are rerouting traffic over other links, but probably they are now overloaded until they can fix the outage. Hopefully the issue is fixed soon, but for now it looks like something neither I or my hosting provider has control over. Please let me know if the problem continues, and I'll take it up with hetzner who might have some info on when init7's connectivity issues are likely to be resolved.
Regards,
Richard.
zwisch:
Ah, okay, thanks for the info. I'll let you know if the problem happens again.
rombelstielz:
As already mentioned in another thread the Rombelstielz sometime experiences the same problem, also at hetzner.de: http://chesstempo.com/chess-forum/site_feedback/suggestion_preload_solution_next_exercise-t4798.0.html;msg38647#msg38647
richard:
Quote from: rombelstielz on Jun 19, 2013, 11:00:37 PM
As already mentioned in another thread the Rombelstielz sometime experiences the same problem, also at hetzner.de: http://chesstempo.com/chess-forum/site_feedback/suggestion_preload_solution_next_exercise-t4798.0.html;msg38647#msg38647
Hi rombelstielz,
This probably isn't excatly the same issue, as in your traceroute the first packet drop started inside hetzner, whereas zwisch's example indicates the first packets are going missing at the hop before hetzner. Also one traceroute in isolation is hard to draw conclusions from as when a hop is dropping packets they will show up in the traceroute as drops anywhere between the dropping host and the end point even if it is only one host that drops the packets (this is due to the way traceroute metrics work). You can see this in play in zwisch's traceroutes where packets drop all the way from the init7 gateway machine up to the CT server, usually the drop point is the first one to start regularly dropping in the path, but it can often take a few traceroutes to reliably determine that.
Regards,
Richard.
Navigation
[0] Message Index