As of about 1:00PM PDT today it appears that a number of European ISP's are experiencing issues connecting to the standard backbone line typically used to connect to our server.
Most of the connections being affected by this are still reaching the MWO servers, but the adjusted routes are adding an average of 50ms to their connection latency.
If you are experiencing connection stability issues in Europe, or if you are seeing multiple players drop from matches, this is the likely cause.
We will keep this post updated as more information becomes available.
0
Potential Service Disruption/increased Latency For European Connections
Started by Alexander Garden, Apr 21 2015 01:53 PM
6 replies to this topic
#1
Posted 21 April 2015 - 01:53 PM
#2
Posted 22 April 2015 - 03:03 PM
I got disconnected it the middle of the match (game got swiched back to log-in screen by "An Error Occured - Unknown failure"and now I can't get past "Connecting" screen after the login - it's just stuck there. Any help?
PS. Had no issues at all, everything worked great till now.
PPS. I'm in Europe. Just managed to search for a game but it was back to log-in screen with "Network error occured" <- something like that.
PS. Had no issues at all, everything worked great till now.
PPS. I'm in Europe. Just managed to search for a game but it was back to log-in screen with "Network error occured" <- something like that.
Edited by Ninjah, 22 April 2015 - 03:09 PM.
#3
Posted 22 April 2015 - 10:29 PM
I had the same problem, got disconnected at around 24:00 UTC-1, with "Unknown error" or "Network error occurred". After attempting to login again, I received those error repeatedly. I gave up after 30 minutes of trying.
Quote
traceroute to 192.99.109.192 (192.99.109.192), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 4.910 ms 4.895 ms 4.888 ms
2 BSN-176-255-241.dynamic.siol.net (95.176.255.241) 11.314 ms 11.322 ms 11.763 ms
3 BSN-176-253-5.dynamic.siol.net (95.176.253.5) 13.478 ms 14.143 ms 14.389 ms
4 bpt-b4-link.telia.net (213.248.90.185) 78.782 ms 79.116 ms 79.676 ms
5 prag-bb1-link.telia.net (62.115.143.114) 27.749 ms 28.627 ms 28.820 ms
6 ffm-bb1-link.telia.net (213.155.130.202) 46.864 ms ffm-bb1-link.telia.net (62.115.135.10) 38.756 ms ffm-bb1-link.telia.net (80.91.248.142) 39.579 ms
7 ffm-b11-link.telia.net (62.115.137.127) 40.960 ms ffm-b11-link.telia.net (62.115.137.251) 41.246 ms ffm-b11-link.telia.net (62.115.137.119) 40.077 ms
8 fra-1-6k.de.eu (213.186.32.221) 47.569 ms 48.698 ms 49.205 ms
9 rbx-s11-6k.fr.eu (91.121.131.250) 49.611 ms sbg-g1-a9.fr.eu (91.121.128.127) 51.057 ms rbx-s11-6k.fr.eu (91.121.131.250) 50.267 ms
10 37.187.36.153 (37.187.36.153) 51.008 ms 46.446 ms 47.206 ms
11 mwomercs.com (192.99.109.192) 137.632 ms !X 138.329 ms !X 237.602 ms !X
1 192.168.1.1 (192.168.1.1) 4.910 ms 4.895 ms 4.888 ms
2 BSN-176-255-241.dynamic.siol.net (95.176.255.241) 11.314 ms 11.322 ms 11.763 ms
3 BSN-176-253-5.dynamic.siol.net (95.176.253.5) 13.478 ms 14.143 ms 14.389 ms
4 bpt-b4-link.telia.net (213.248.90.185) 78.782 ms 79.116 ms 79.676 ms
5 prag-bb1-link.telia.net (62.115.143.114) 27.749 ms 28.627 ms 28.820 ms
6 ffm-bb1-link.telia.net (213.155.130.202) 46.864 ms ffm-bb1-link.telia.net (62.115.135.10) 38.756 ms ffm-bb1-link.telia.net (80.91.248.142) 39.579 ms
7 ffm-b11-link.telia.net (62.115.137.127) 40.960 ms ffm-b11-link.telia.net (62.115.137.251) 41.246 ms ffm-b11-link.telia.net (62.115.137.119) 40.077 ms
8 fra-1-6k.de.eu (213.186.32.221) 47.569 ms 48.698 ms 49.205 ms
9 rbx-s11-6k.fr.eu (91.121.131.250) 49.611 ms sbg-g1-a9.fr.eu (91.121.128.127) 51.057 ms rbx-s11-6k.fr.eu (91.121.131.250) 50.267 ms
10 37.187.36.153 (37.187.36.153) 51.008 ms 46.446 ms 47.206 ms
11 mwomercs.com (192.99.109.192) 137.632 ms !X 138.329 ms !X 237.602 ms !X
Quote
PING 192.99.109.192 (192.99.109.192) 56(84) bytes of data.
64 bytes from 192.99.109.192: icmp_seq=1 ttl=54 time=160 ms
64 bytes from 192.99.109.192: icmp_seq=2 ttl=54 time=183 ms
64 bytes from 192.99.109.192: icmp_seq=3 ttl=54 time=206 ms
64 bytes from 192.99.109.192: icmp_seq=4 ttl=54 time=136 ms
64 bytes from 192.99.109.192: icmp_seq=5 ttl=54 time=149 ms
64 bytes from 192.99.109.192: icmp_seq=6 ttl=54 time=172 ms
64 bytes from 192.99.109.192: icmp_seq=7 ttl=54 time=135 ms
64 bytes from 192.99.109.192: icmp_seq=8 ttl=54 time=217 ms
64 bytes from 192.99.109.192: icmp_seq=9 ttl=54 time=240 ms
64 bytes from 192.99.109.192: icmp_seq=10 ttl=54 time=136 ms
64 bytes from 192.99.109.192: icmp_seq=11 ttl=54 time=183 ms
64 bytes from 192.99.109.192: icmp_seq=12 ttl=54 time=207 ms
64 bytes from 192.99.109.192: icmp_seq=13 ttl=54 time=228 ms
64 bytes from 192.99.109.192: icmp_seq=14 ttl=54 time=135 ms
^C
--- 192.99.109.192 ping statistics ---
14 packets transmitted, 14 received, 0% packet loss, time 13015ms
rtt min/avg/max/mdev = 135.619/178.013/240.125/35.781 ms
64 bytes from 192.99.109.192: icmp_seq=1 ttl=54 time=160 ms
64 bytes from 192.99.109.192: icmp_seq=2 ttl=54 time=183 ms
64 bytes from 192.99.109.192: icmp_seq=3 ttl=54 time=206 ms
64 bytes from 192.99.109.192: icmp_seq=4 ttl=54 time=136 ms
64 bytes from 192.99.109.192: icmp_seq=5 ttl=54 time=149 ms
64 bytes from 192.99.109.192: icmp_seq=6 ttl=54 time=172 ms
64 bytes from 192.99.109.192: icmp_seq=7 ttl=54 time=135 ms
64 bytes from 192.99.109.192: icmp_seq=8 ttl=54 time=217 ms
64 bytes from 192.99.109.192: icmp_seq=9 ttl=54 time=240 ms
64 bytes from 192.99.109.192: icmp_seq=10 ttl=54 time=136 ms
64 bytes from 192.99.109.192: icmp_seq=11 ttl=54 time=183 ms
64 bytes from 192.99.109.192: icmp_seq=12 ttl=54 time=207 ms
64 bytes from 192.99.109.192: icmp_seq=13 ttl=54 time=228 ms
64 bytes from 192.99.109.192: icmp_seq=14 ttl=54 time=135 ms
^C
--- 192.99.109.192 ping statistics ---
14 packets transmitted, 14 received, 0% packet loss, time 13015ms
rtt min/avg/max/mdev = 135.619/178.013/240.125/35.781 ms
Edited by PanzerFurrry, 22 April 2015 - 10:42 PM.
#4
Posted 23 April 2015 - 11:33 AM
So what would cause my cmd ping to be ~140ms, while in-game it shows 180-200ms? Europe.
#5
Posted 26 April 2015 - 08:11 AM
Ping normaly 100-105, since 21th april 115-165 + lags and rubberbanding.. well done
#6
Posted 29 April 2015 - 04:10 PM
Chimperator, on 26 April 2015 - 08:11 AM, said:
Ping normaly 100-105, since 21th april 115-165 + lags and rubberbanding.. well done
Let's just ask PGI buy the line off the ISP's shall we?
For further reference: Play on the AU 250ms+ and then we can talk about your "lag".
#7
Posted 03 May 2015 - 11:54 AM
KelesK, on 29 April 2015 - 04:10 PM, said:
Let's just ask PGI buy the line off the ISP's shall we?
For further reference: Play on the AU 250ms+ and then we can talk about your "lag".
Your personaly problem isn't my, u should focus on the great work that PGI do not at people with the same problems like u!
4 user(s) are reading this topic
0 members, 4 guests, 0 anonymous users