
Originally Posted by
Norna
Isn't it that S-E works with
Ormuco (from what I can gather, they do data center/cloud services) in keeping their NA/EU data center running? Why would there be such huge packet loss between Ormuco and S-E's server architecture? Also, I looked around at others having similar problems, and saw that a few with posted trace routes have perfect connections until they hit Ormuco, then they either get losses where I do, or between the S-E IP addresses.
If Ormuco is bad it doesn't mean it's SE fault xD
I did a tracert too and the last 3 nodes are the only thing in common.
1 <1 ms 1 ms <1 ms 192.168.0.1
2 1 ms 1 ms 1 ms OPENRG [192.168.1.254]
3 10 ms 11 ms 11 ms 10.134.248.1
4 10 ms 10 ms 10 ms 10.3.233.162
5 11 ms 10 ms 10 ms 10.251.149.209
6 10 ms 10 ms 10 ms 10.251.144.37
7 11 ms 9 ms 10 ms 10.251.145.1
8 11 ms 10 ms 9 ms 10.251.149.194
9 10 ms 10 ms 9 ms 10.3.136.205
10 11 ms 11 ms 10 ms 10.3.128.62
11 11 ms 10 ms 10 ms 10.254.11.73
12 28 ms 14 ms 14 ms 10.254.1.81
13 15 ms 15 ms 15 ms 89.97.200.170
14 25 ms 24 ms 24 ms 89.96.200.1
15 24 ms 24 ms 24 ms 89.96.200.114
16 59 ms 206 ms 99 ms te2-3.ccr01.mil01.atlas.cogentco.com [149.6.152.69]
17 29 ms 28 ms 29 ms te0-0-0-3.ccr21.zrh01.atlas.cogentco.com [154.54.62.6]
18 34 ms 37 ms 34 ms be2023.ccr21.muc01.atlas.cogentco.com [130.117.0.249]
19 38 ms 38 ms 38 ms te0-2-0-2.mpd21.fra03.atlas.cogentco.com [130.117.48.69]
20 47 ms 45 ms 45 ms te0-5-0-3.mpd21.ams03.atlas.cogentco.com [154.54.78.169]
21 57 ms 55 ms 55 ms be2184.ccr21.lpl01.atlas.cogentco.com [154.54.37.70]
22 126 ms 126 ms 126 ms te0-2-0-1.ccr21.ymq02.atlas.cogentco.com [154.54.87.62]
23 127 ms 127 ms 126 ms 38.122.42.34
24 * * * Richiesta scaduta.
25 125 ms 123 ms 124 ms 192.34.76.2
26 124 ms 123 ms 123 ms 199.91.189.234
27 123 ms 124 ms 124 ms 199.91.189.27