No replies to this topic

[E5Ky]

I get 100% packet loss in the evenings connecting to all MWO sites and servers. Any time from just before sun down to after sun up. Both the game and forums are unreachable. These are the only sites I can not access globally and this has been going on for a long time now.

I suspect its how traffic is routed in the middle via "Seabone.net" at certain times of the day? How to go about correcting this ? For years this has worked fine without issue.

For a working connection I see this:

[color=#000000]Pinging 192.99.109.192 with 32 bytes of data:[/color][color=#000000]
Reply from 192.99.109.192: bytes=32 time=270ms TTL=43[/color]
[color=#000000]
Reply from 192.99.109.192: bytes=32 time=270ms TTL=43[/color]
[color=#000000]
Reply from 192.99.109.192: bytes=32 time=269ms TTL=43[/color]
[color=#000000]
Reply from 192.99.109.192: bytes=32 time=267ms TTL=43[/color]
[color=#000000]
[/color]
[color=#000000]
Ping statistics for 192.99.109.192:[/color]
[color=#000000]
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),[/color]
[color=#000000]
Approximate round trip times in milli-seconds:[/color]
[color=#000000]
Minimum = 267ms, Maximum = 270ms, Average = 269ms[/color]
[color=#000000]
[/color]
[color=#000000]

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 1 ms 3 ms 6 ms 192.168.0.1
2 8 ms 10 ms 7 ms 10.50.0.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 10 ms 10 ms 10 ms 198.142.250.241
8 9 ms 12 ms 11 ms 198.142.139.118
9 10 ms 10 ms 14 ms 198.142.139.134
10 159 ms 203 ms 159 ms 203.208.190.137
11 175 ms 168 ms 168 ms 203.208.149.253
12 171 ms 169 ms 169 ms 203.208.172.234
13 175 ms 177 ms 173 ms paloalto1.pao.seabone.net [198.32.176.70]
14 239 ms 239 ms 241 ms et10-1-0.miami15.mia.seabone.net [89.221.41.175]
15 234 ms 239 ms 233 ms et4-3-0.miami15.mia.seabone.net [195.22.199.177]
16 * * 463 ms po99-155.mia-5-6k.fl.us [178.32.135.208]
17 266 ms 265 ms 264 ms be100-1263.chi-1-a9.il.us [178.32.135.5]
18 267 ms 269 ms 268 ms be10-1312.bhs-g1-a9.qc.ca [198.27.73.196]
19 272 ms 271 ms 273 ms vl21.bhs-g1-a75.qc.ca [198.27.73.63]
20 269 ms 268 ms 268 ms bhs-g5-a9.qc.ca [178.32.135.194]
21 271 ms 272 ms 271 ms mwomercs.com [192.99.109.192]

Trace complete.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Pinging 192.99.40.103 with 32 bytes of data:
Reply from 192.99.40.103: bytes=32 time=265ms TTL=106
Reply from 192.99.40.103: bytes=32 time=262ms TTL=106
Reply from 192.99.40.103: bytes=32 time=264ms TTL=106
Reply from 192.99.40.103: bytes=32 time=255ms TTL=106

Ping statistics for 192.99.40.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 255ms, Maximum = 265ms, Average = 261ms


Tracing route to ns7000224.ip-192-99-40.net [192.99.40.103]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms 192.168.0.1
2 9 ms 7 ms 9 ms 10.50.0.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 9 ms 10 ms 12 ms 211.29.126.153
7 10 ms 10 ms 9 ms 198.142.139.118
8 9 ms 10 ms 9 ms 198.142.139.134
9 155 ms 156 ms 156 ms 203.208.177.81
10 173 ms 172 ms 170 ms 203.208.171.13
11 166 ms 164 ms 165 ms 203.208.172.234
12 172 ms 172 ms 170 ms paloalto1.pao.seabone.net [198.32.176.70]
13 223 ms 223 ms 224 ms et9-3-0.miami15.mia.seabone.net [195.22.199.179]
14 226 ms 228 ms 230 ms et10-3-0.miami15.mia.seabone.net [89.221.41.177]
15 * 298 ms * po99-155.mia-5-6k.fl.us [178.32.135.208]
16 266 ms 266 ms 263 ms be100-1266.chi-1-a9.il.us [178.32.135.11]
17 255 ms 258 ms 257 ms be10-1312.bhs-g1-a9.qc.ca [198.27.73.196]
18 262 ms 261 ms 261 ms vl20.bhs-g1-a75.qc.ca [198.27.73.229]
19 256 ms 257 ms 256 ms po5.bhs-s4-6k.qc.ca [198.27.73.144]
20 259 ms 256 ms 260 ms ns7000224.ip-192-99-40.net [192.99.40.103]

Trace complete.
[/color]

When the connection doesn't work I see this:

[color=#000000]Pinging 192.99.109.192 with 32 bytes of data:[/color][color=#000000]
Request timed out.[/color]
[color=#000000]
Request timed out.[/color]
[color=#000000]
Request timed out.[/color]
[color=#000000]
Request timed out.[/color]
[color=#000000]
[/color]
[color=#000000]
Ping statistics for 192.99.109.192:[/color]
[color=#000000]
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),[/color]
[color=#000000]
[/color]
[color=#000000]

Tracing route to 192.99.109.192 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 9 ms 9 ms 10.50.0.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 12 ms 12 ms 9 ms 198.142.250.241
8 16 ms 11 ms 10 ms 198.142.139.118
9 11 ms 14 ms 11 ms 198.142.139.134
10 208 ms 212 ms 214 ms 203.208.190.137
11 227 ms 214 ms 218 ms 203.208.149.253
12 205 ms 199 ms 197 ms 203.208.172.234
13 201 ms 204 ms 201 ms paloalto1.pao.seabone.net [198.32.176.70]
14 291 ms 289 ms 283 ms et4-3-0.miami15.mia.seabone.net [195.22.199.177]
15 288 ms 270 ms 283 ms et4-3-0.miami15.mia.seabone.net [195.22.199.177]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Pinging 192.99.40.103 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.99.40.103:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


Tracing route to 192.99.40.103 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 7 ms 9 ms 10.50.0.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 13 ms 12 ms 9 ms 211.29.126.153
7 12 ms 12 ms 11 ms 198.142.139.118
8 10 ms 9 ms 9 ms 198.142.139.134
9 199 ms 201 ms 198 ms 203.208.177.81
10 219 ms 204 ms 221 ms 203.208.171.13
11 217 ms 221 ms 220 ms 203.208.172.234
12 211 ms 224 ms 227 ms paloalto1.pao.seabone.net [198.32.176.70]
13 270 ms 274 ms 273 ms et9-3-0.miami15.mia.seabone.net [195.22.199.179]
14 258 ms 260 ms 267 ms et10-3-0.miami15.mia.seabone.net [89.221.41.177]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.[/color]


Asking if anyone else is experiencing this ? If someone from support can respond to my mail and advise on how to proceed please? I feel like both my ISP and MWO don't want to deal with this.