I'm connecting from Melbourne Australia, and it's taking up to 10 minutes to connect to the EA servers, then it crashes when trying to connect to multiplayerI managed to make it through once or twice, but all my equipment selections were greyed out so I couldn't select ammo buffs, and my lvl19 Valkyrie had all her powers reset to default. Then it disconnected me.I've never had any trouble before, I haven't changed ISP or been shaped, I've restarted Origin and my computer.Can anyone help? I would like to try and complete the challenge this weekend if possible!Thanks!

Perth, WA here and on iiNet. Also tested with Telstra Cable, Telstra NextG, Internode ADSL and TPG ADSL at other locations to confirm it wasn't just my provider.I found this problem myself at 11:00PM WST (no DST anymore) on Friday 14th of December 2012 right before Project Alamo started and it's been occurring ever since. I've spent the last two weeks with no results whatsoever from EA Support (finally got a response to my emails after more than a week of waiting and it just repeated everything I've already been told and tried before...) to improve the problem and the only time I've been able to get connected is during a very short window from 3:00AM WST to 6:00AM WST.I have been extensively troubleshooting this problem ever since and to date I have done the following with no improvement:Software:Confirmed Windows Firewall was disabled (no other software firewalls installed)Confirmed Avast! Free AntiVirus disabled (set to silent/gaming mode).Uninstalled Avast! Free AntiVirus.Logged out of Origin software, then logged back in again before trying ME3 Multiplayer again.Logged out of all Origin website logins and the Origin software, then logging back in again.Cleared all cache files (Origin, Internet Explorer, Mozilla Firefox, Google Chrome and Apple Safari) and Windows temporary files too.Changed my Origin password.Uninstalled Origin and reinstalled it.Ran repair installation of Mass Effect 3.Uninstalled Mass Effect 3 and all DLC, then reinstalled it along with all previously paid for and free DLC.Hardware:Power cycled my Netgear DGN2000 ADSL/WiFi router for 10 minutes to get a new IP address, then logged into Origin and tried ME3 Multiplayer again.Confirmed all Origin PC port forwarding was enabled correctly.Manually disabled all firewall options built-in to my Netgear router, logged into Origin and tried ME3 Multiplayer again.Factory reset my router, reconfigured it from scratch with firewall off and tried again.Isolation test of phone line to just ADSL router to confirm no line noise/interference issues.Tried another brand new ADSL router, Netcomm NB6Plus4, with default configuration for built-in firewall and custom Origin PC port forwarding enabled.Updated firmware in Netcomm NB6Plus4 to latest version, factory reset it, then repeated previous configuration settings (inc. Origin PC port forwarding)Tried Netcomm NB6Plus4 router with firewall manually disabled.Tried iiNet ADSL from a family member's house in the same suburb with their router (Netgear DG834PN) with same port forwarding.Tried iiNet ADSL from a friend's house in a neighbouring suburb with their router (TP-LINK TD-8840) with same port forwarding.Tried Telstra NextG USB device from my house with five bars signal strength.Tried Telstra Cable from a friend's house in another suburb closer to the CBD with their router (Motorola SBG6580) configured for the same port forwarding.Tried Internode ADSL from a Perth City Internet Cafe through the ADSL router directly (no firewall, DMZ location).Tried TPG ADSL from a Perth CBD business directly off the router (no firewall, DMZ location).Using the UOTrace tool (https://help.ea.com/article/how-to-uo-trace), as requested by one helpful EA Customer Support Advisor after he saw how long my fault has been open for, I performed multiple trace route tests and repeatedly hit xe-11-2-0.edge1.losangeles6.level3.net (4.68.62.9) and 8-3-2.edge1.LosAngels.Level3.net (4.68.70.69) as dead points in the test.Further investigation found that Level3.net is a Tier 1 network backbone provider on the USA Western Seaboard for the Washington and Los Angeles network pipes to Japan, Hawaii, Fiji, Australia and New Zealand. Matched up against the brief period that I rarely connected to the ME3 Multiplayer with the Washington pipe, it left the Los Angeles routers provided by Level3.net as the primary cause of our problems.Armed with this, I went to the ISPs after still no assistance from the EA Support team.Internet Service Providers:Spoke with iiNet Support and they created Fault #2319010 (http://www.iinet.net.au/status/fault.php?id=2319010) after other iiNet customers complained too about Spotify and their multiplayer games connecting to USA servers having problems.Spoke with Telstra Support (Cable & NextG) and they blamed EA Servers for being at fault.Spoke with Internode Support and they couldn't confirm/deny it other than commenting it was a problem with the EA Servers.Spoke with TPG Support and they blamed EA Servers for being at fault.I am using a Windows Vista Ultimate SP2 laptop with an ethernet cable link to my Netgear DGN2000 ADSL/WiFi router. I have never used local wireless networking for this gaming computer when playing Mass Effect 3 Multiplayer. I do not have the Omega DLC installed, but I have everything else except the appearance and weapon DLC packs.This is not a DLC caused problem. It is a Tier 1 network problem with the Level3.net provided services in Los Angeles and only they can fix it, but EA could certainly help by directing some fault information their way since the Internet Service Provider network operation centre teams can only provide the trace route (tracert) information from our side alone.The only way to solve this issue is for all of us in Australia and New Zealand caught on the Sydney-Hawaii-Los Angeles or Auckland-Hawaii-Los Angeles pipe to let our Internet Service Provider support teams know this problem and for EA Support to raise the issue with Level3.net from their side too. Provide your UOTrace results (at least five) to your ISP Support and include it in your EA Support cases too with screenshots of the errors.Otherwise this will never be solved because only one half of the testing is being completed. And if that happens I'll be very upset.(Edit: Added additional troubleshooting I'd forgotten).

j1m13, yeah you're still hitting the xe-11-2-0.edge1.losangeles6.level3.net (4.68.62.9) busted route in your usual results like I am, but the second testing confirmed you're going through a different working Level3.net router in Los Angeles and on to the working Washington pipe.Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst* Unknown Host * 192.168.0.1 1 1ms 1ms 0% 101 / 101 1ms / 1msnexthop.wa.iinet.net.au 203.215.5.243 2 14ms 14ms 0% 101 / 101 14ms / 15mste7-2.per-qv1-bdr1.iinet.net.au 203.215.4.20 3 14ms 14ms 0% 101 / 101 14ms / 15msxe-3-3-0-0.syd-ult-core1.iinet.net.au 203.215.20.6 4 72ms 70ms 0% 101 / 101 66ms / 73msunknown.telstraglobal.net 134.159.126.189 5 73ms 73ms 0% 100 / 100 73ms / 73msi-0-7-1-0.sydo-core02.bi.telstraglobal.net 202.84.223.1 6 69ms 69ms 0% 100 / 100 68ms / 71msi-0-7-0-0.1wlt-core01.bx.telstraglobal.net 202.84.249.54 7 215ms 214ms 0% 100 / 100 214ms / 215msi-0-0-0-0.tlot02.bi.telstraglobal.net 202.40.149.142 8 223ms 223ms 0% 100 / 100 223ms / 223ms8-3-2.edge1.LosAngels.Level3.net 4.68.70.69 9 219ms 100% 0 / 100vlan90.csw4.LosAngeles1.Level3.net 4.69.144.254 10 253ms 252ms 0% 100 / 100 252ms / 253msae-93-93.ebr3.LosAngeles1.Level3.net 4.69.137.45 11 226ms 226ms 0% 100 / 100 226ms / 227ms* Unknown Host * 4.69.132.82 12 286ms 286ms 0% 100 / 100 286ms / 286msae-91-91.csw4.Washington1.Level3.net 4.69.134.142 13 315ms 315ms 0% 100 / 100 315ms / 315msae-43-90.car3.Washington1.Level3.net 4.69.149.197 14 287ms 287ms 0% 100 / 100 287ms / 287msELECTRONIC.car3.Washington1.Level3.net 4.79.169.74 15 311ms 311ms 0% 100 / 100 311ms / 312msfert07-eqx-iad.ea.com 159.153.224.230 16 291ms 291ms 0% 100 / 100 291ms / 291msmeav5-pub.pt.iad.ea.com 159.153.226.105 17 298ms 298ms 0% 100 / 100 298ms / 299msThanks for the continued confirmation of this problem. It is amusing to see some of the Los Angeles routers working now, but the main ones are still borked.=============Edit: Updated with my latest results from the time of this post at 2:39AM Perth WST +8 GMT, no daylight savings. And I also just noticed something interesting with the broken route:8-3-2.edge1.LosAngels.Level3.net 4.68.70.69 9 219ms 100% 0 / 100vlan90.csw4.LosAngeles1.Level3.net 4.69.144.254 10 253ms 252ms 0% 100 / 100 252ms / 253msae-93-93.ebr3.LosAngeles1.Level3.net 4.69.137.45 11 226ms 226ms 0% 100 / 100 226ms / 227ms* Unknown Host * 4.69.132.82 12 286ms 286ms 0% 100 / 100 286ms / 286msThe dead route link causing problems runs through the same routing pathway of four IP addresses... I REALLY need more players in Australia and New Zealand having this problem to run their UOTrace tests and post their results when they can't play ME3 Multiplayer to see if this pattern repeats.=============

Hey everyone,I've managed to get in touch with someone from Level 3, and they've said they'll look into it for us. I'll post when they get back to me with more information/a resolution.

Randrake I'd love to see your UOTrace information to compare it to the AUS and NZ players postings. A USA player having this problem would nail it as being a worldwide issue caused from within the USA zone.Oh and since it nearly just happened to me, if you have a EA Support Case open for this issue DON'T let them close it. Keep updating it, even if they're not responding so the EA automated system doesn't close it after six days of inactivity.(Edit: Reminded to keep your EA Support Case open)

I've had three chances to try this game in the early hours of the morning with the game working perfectly fine.Just by chance, I ran UOTrace at exactly 4am ( Perth Time: GMT +8 ) when it went from the usual results to a different result for a couple of hours, in which time the game works.*Note that the suspect server address is not in the "working results".*Copy and paste back into Notepad for original formatting.The usual ( almost 24/7 ) results;Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst* Unknown Host * 10.1.1.1 1 0ms 0ms 0% 7 / 7 0ms / 0msnexthop.wa.iinet.net.au 203.215.5.244 2 6ms 6ms 0% 7 / 7 6ms / 6mste7-1.per-qv1-bdr2.iinet.net.au 203.215.4.36 3 6ms 6ms 0% 7 / 7 5ms / 7mspo1-100.per-qv1-bdr1.iinet.net.au 203.215.20.130 4 6ms 6ms 0% 7 / 7 6ms / 7mste4-4.ade-pipe-bdr2.iinet.net.au 203.215.20.20 5 34ms 33ms 0% 7 / 7 33ms / 34mspo4-100.ade-pipe-bdr1.iinet.net.au 203.215.20.137 6 34ms 33ms 0% 7 / 7 33ms / 35mste6-4.mel-pipe-bdr1.iinet.net.au 203.215.20.18 7 60ms 45ms 0% 7 / 7 42ms / 60mste6-1-100.mel-pipe-bdr2.iinet.net.au 203.215.20.139 8 43ms 43ms 0% 7 / 7 43ms / 43msxe-2-0-2.syd-mas-core1.iinet.net.au 203.215.20.117 9 61ms 62ms 0% 7 / 7 54ms / 81ms32433.chep02.cu.telstraglobal.net 134.159.130.105 10 60ms 60ms 0% 7 / 7 60ms / 61msi-0-6-1-0.sydp-core01.bi.telstraglobal.net 202.84.223.9 11 67ms 66ms 0% 6 / 6 66ms / 68msi-0-6-0-0.1wlt-core01.bx.telstraglobal.net 202.84.249.93 12 211ms 210ms 0% 6 / 6 210ms / 211msi-0-0-0-1.tlot02.bi.telstraglobal.net 202.40.149.138 13 219ms 219ms 0% 6 / 6 219ms / 220msxe-11-2-0.edge1.losangeles6.level3.net 4.68.62.9 14 218ms 100% 0 / 6vlan90.csw4.LosAngeles1.Level3.net 4.69.144.254 15 227ms 230ms 0% 6 / 6 227ms / 237msae-93-93.ebr3.LosAngeles1.Level3.net 4.69.137.45 16 228ms 229ms 0% 6 / 6 228ms / 231ms* Unknown Host * 4.69.132.82 17 296ms 294ms 0% 6 / 6 294ms / 296msae-71-71.csw2.Washington1.Level3.net 4.69.134.134 18 304ms 302ms 0% 6 / 6 299ms / 304msae-33-80.car3.Washington1.Level3.net 4.69.149.133 19 292ms 291ms 0% 6 / 6 291ms / 292msELECTRONIC.car3.Washington1.Level3.net 4.79.169.74 20 297ms 297ms 0% 6 / 6 297ms / 298msFrom 4am for a couple of hours;Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst* Unknown Host * 10.1.1.1 1 0ms 0ms 0% 4 / 4 0ms / 0msnexthop.wa.iinet.net.au 203.215.5.243 2 6ms 6ms 0% 4 / 4 6ms / 6mste7-2.per-qv1-bdr2.iinet.net.au 203.215.4.38 3 6ms 7ms 0% 4 / 4 6ms / 10msxe-3-3-0-0.syd-mas-core1.iinet.net.au 203.215.20.68 4 61ms 81ms 0% 4 / 4 60ms / 124ms32433.chep02.cu.telstraglobal.net 134.159.130.105 5 64ms 64ms 0% 4 / 4 64ms / 65msi-0-6-1-0.sydp-core01.bi.telstraglobal.net 202.84.223.9 6 64ms 64ms 0% 4 / 4 64ms / 65msi-0-2-2-0.1wlt-core01.bx.telstraglobal.net 202.84.144.221 7 214ms 214ms 0% 4 / 4 214ms / 214msi-0-0-0-5.tlot02.bi.telstraglobal.net 202.40.149.154 8 220ms 219ms 0% 3 / 3 219ms / 220msl3-peer.tlot02.pr.telstraglobal.net 134.159.62.14 9 267ms 259ms 0% 3 / 3 256ms / 267msvlan80.csw3.LosAngeles1.Level3.net 4.69.144.190 10 228ms 231ms 0% 3 / 3 228ms / 239msae-83-83.ebr3.LosAngeles1.Level3.net 4.69.137.41 11 229ms 228ms 0% 3 / 3 227ms / 229ms* Unknown Host * 4.69.132.82 12 289ms 288ms 0% 3 / 3 288ms / 289msae-71-71.csw2.Washington1.Level3.net 4.69.134.134 13 299ms 296ms 0% 3 / 3 290ms / 299msae-23-70.car3.Washington1.Level3.net 4.69.149.69 14 294ms 294ms 0% 3 / 3 294ms / 295msELECTRONIC.car3.Washington1.Level3.net 4.79.169.74 15 296ms 296ms 0% 3 / 3 296ms / 296msfert07-eqx-iad.ea.com 159.153.224.230 16 286ms 286ms 0% 3 / 3 286ms / 287msmeav5-pub.pt.iad.ea.com 159.153.226.105 17 282ms 281ms 0% 3 / 3 281ms / 282ms

ME3 (PC) - Problems connecting to Multiplayer / staying connected

115 Replies

TheDesertRunner
13 years ago
agam3mn0n, I know your anger with this one but I'm certain it's a communication issue up the pipe on the Sydney-Hawaii-Los Angeles path. And yeah, I seriously doubt its a Windows 8 problem either but as a tech' that one is going to be thrown around a lot as a scapegoat until EA openly declare they'll support the O/S. :\
Please run the UOTrace tests and pass the information on to your ISP so they can at least check for the Level3.net routing failure. Though if you're with Telstra or TPG, you have my sympathies since they didn't want to know about it either... hopefully you'll get lucky and the ISP Support will hear you out like iiNet and Internode did.
agam3mn0n
13 years ago
Desertrunner, fortunately, I am with Westnet which is an iinet subsidiary and yes this issue is looking like an issue on the other side of my router. Reverting back to Windows 7 is not exactly a welcome regression but what can we do when thats a typical response. Thanks for the info though, I do appreciate it, I'll send this info along to Westnet...
Cheers
TheDesertRunner
13 years ago
agam3mn0n don't bother downgrading to Windows 7. Other player I know who are using Windows 8 say it works fine, but Origin can be a bit prickly at times when being updated.

Did Westnet report any new information?
DesoPL561
13 years ago
I got the problem for connecting to friends from Origin Games, here the post from my topic.
"
I don't get any game / network error messages, is loading for moment and don't joined the game.
The problem is harder after Retaliation DLC release.
Here screenshot. http://i49.tinypic.com/dg4ia8.jpg No error, never ending joing. ;/
Are on PC."
All this problems i have after the Retaliation DLC, before i can join to few friends games, now i cannot.
J1M_13
Seasoned Rookie
13 years ago
I've had three chances to try this game in the early hours of the morning with the game working perfectly fine.
Just by chance, I ran UOTrace at exactly 4am ( Perth Time: GMT +8 ) when it went from the usual results to a different result for a couple of hours, in which time the game works.
*Note that the suspect server address is not in the "working results".
*Copy and paste back into Notepad for original formatting.
The usual ( almost 24/7 ) results;
Host Name                                           IP Address        Hop    Ping Time   Ping Avg   % Loss    Pkts r/s   Ping best/worst
* Unknown Host *                                    10.1.1.1          1      0ms         0ms        0%        7 / 7      0ms / 0ms
nexthop.wa.iinet.net.au                             203.215.5.244     2      6ms         6ms        0%        7 / 7      6ms / 6ms
te7-1.per-qv1-bdr2.iinet.net.au                     203.215.4.36      3      6ms         6ms        0%        7 / 7      5ms / 7ms
po1-100.per-qv1-bdr1.iinet.net.au                   203.215.20.130    4      6ms         6ms        0%        7 / 7      6ms / 7ms
te4-4.ade-pipe-bdr2.iinet.net.au                    203.215.20.20     5      34ms        33ms       0%        7 / 7      33ms / 34ms
po4-100.ade-pipe-bdr1.iinet.net.au                  203.215.20.137    6      34ms        33ms       0%        7 / 7      33ms / 35ms
te6-4.mel-pipe-bdr1.iinet.net.au                    203.215.20.18     7      60ms        45ms       0%        7 / 7      42ms / 60ms
te6-1-100.mel-pipe-bdr2.iinet.net.au                203.215.20.139    8      43ms        43ms       0%        7 / 7      43ms / 43ms
xe-2-0-2.syd-mas-core1.iinet.net.au                 203.215.20.117    9      61ms        62ms       0%        7 / 7      54ms / 81ms
32433.chep02.cu.telstraglobal.net                   134.159.130.105   10     60ms        60ms       0%        7 / 7      60ms / 61ms
i-0-6-1-0.sydp-core01.bi.telstraglobal.net          202.84.223.9      11     67ms        66ms       0%        6 / 6      66ms / 68ms
i-0-6-0-0.1wlt-core01.bx.telstraglobal.net          202.84.249.93     12     211ms       210ms      0%        6 / 6      210ms / 211ms
i-0-0-0-1.tlot02.bi.telstraglobal.net               202.40.149.138    13     219ms       219ms      0%        6 / 6      219ms / 220ms
xe-11-2-0.edge1.losangeles6.level3.net              4.68.62.9         14     218ms                  100%      0 / 6
vlan90.csw4.LosAngeles1.Level3.net                  4.69.144.254      15     227ms       230ms      0%        6 / 6      227ms / 237ms
ae-93-93.ebr3.LosAngeles1.Level3.net                4.69.137.45       16     228ms       229ms      0%        6 / 6      228ms / 231ms
* Unknown Host *                                    4.69.132.82       17     296ms       294ms      0%        6 / 6      294ms / 296ms
ae-71-71.csw2.Washington1.Level3.net                4.69.134.134      18     304ms       302ms      0%        6 / 6      299ms / 304ms
ae-33-80.car3.Washington1.Level3.net                4.69.149.133      19     292ms       291ms      0%        6 / 6      291ms / 292ms
ELECTRONIC.car3.Washington1.Level3.net              4.79.169.74       20     297ms       297ms      0%        6 / 6      297ms / 298ms

From 4am for a couple of hours;

Host Name                                           IP Address        Hop    Ping Time   Ping Avg   % Loss    Pkts r/s   Ping best/worst
* Unknown Host *                                    10.1.1.1          1      0ms         0ms        0%        4 / 4      0ms / 0ms
nexthop.wa.iinet.net.au                             203.215.5.243     2      6ms         6ms        0%        4 / 4      6ms / 6ms
te7-2.per-qv1-bdr2.iinet.net.au                     203.215.4.38      3      6ms         7ms        0%        4 / 4      6ms / 10ms
xe-3-3-0-0.syd-mas-core1.iinet.net.au               203.215.20.68     4      61ms        81ms       0%        4 / 4      60ms / 124ms
32433.chep02.cu.telstraglobal.net                   134.159.130.105   5      64ms        64ms       0%        4 / 4      64ms / 65ms
i-0-6-1-0.sydp-core01.bi.telstraglobal.net          202.84.223.9      6      64ms        64ms       0%        4 / 4      64ms / 65ms
i-0-2-2-0.1wlt-core01.bx.telstraglobal.net          202.84.144.221    7      214ms       214ms      0%        4 / 4      214ms / 214ms
i-0-0-0-5.tlot02.bi.telstraglobal.net               202.40.149.154    8      220ms       219ms      0%        3 / 3      219ms / 220ms
l3-peer.tlot02.pr.telstraglobal.net                 134.159.62.14     9      267ms       259ms      0%        3 / 3      256ms / 267ms
vlan80.csw3.LosAngeles1.Level3.net                  4.69.144.190      10     228ms       231ms      0%        3 / 3      228ms / 239ms
ae-83-83.ebr3.LosAngeles1.Level3.net                4.69.137.41       11     229ms       228ms      0%        3 / 3      227ms / 229ms
* Unknown Host *                                    4.69.132.82       12     289ms       288ms      0%        3 / 3      288ms / 289ms
ae-71-71.csw2.Washington1.Level3.net                4.69.134.134      13     299ms       296ms      0%        3 / 3      290ms / 299ms
ae-23-70.car3.Washington1.Level3.net                4.69.149.69       14     294ms       294ms      0%        3 / 3      294ms / 295ms
ELECTRONIC.car3.Washington1.Level3.net              4.79.169.74       15     296ms       296ms      0%        3 / 3      296ms / 296ms
fert07-eqx-iad.ea.com                               159.153.224.230   16     286ms       286ms      0%        3 / 3      286ms / 287ms
meav5-pub.pt.iad.ea.com                             159.153.226.105   17     282ms       281ms      0%        3 / 3      281ms / 282ms
Anonymous
13 years ago
Sydney, Australia.
Same issue. I will get to wave 6 in most games and get booted out. Also never have a good connection, ever.
Anonymous
13 years ago
thedesertrunner, awesome work!
Will do as you posted. Because, unless this gets sorted, any future game requiring this pipe through LA is likely to have the same problem, unplayable.
Tye
TheDesertRunner
13 years ago
j1m13, yeah you're still hitting the xe-11-2-0.edge1.losangeles6.level3.net (4.68.62.9) busted route in your usual results like I am, but the second testing confirmed you're going through a different working Level3.net router in Los Angeles and on to the working Washington pipe.
Host Name                                      IP Address         Hop    Ping Time   Ping Avg   % Loss    Pkts r/s   Ping best/worst
* Unknown Host *                               192.168.0.1        1      1ms         1ms        0%        101 / 101      1ms / 1ms
nexthop.wa.iinet.net.au                        203.215.5.243      2      14ms        14ms       0%        101 / 101      14ms / 15ms
te7-2.per-qv1-bdr1.iinet.net.au                203.215.4.20       3      14ms        14ms       0%        101 / 101      14ms / 15ms
xe-3-3-0-0.syd-ult-core1.iinet.net.au          203.215.20.6       4      72ms        70ms       0%        101 / 101      66ms / 73ms
unknown.telstraglobal.net                      134.159.126.189    5      73ms        73ms       0%        100 / 100      73ms / 73ms
i-0-7-1-0.sydo-core02.bi.telstraglobal.net     202.84.223.1       6      69ms        69ms       0%        100 / 100      68ms / 71ms
i-0-7-0-0.1wlt-core01.bx.telstraglobal.net     202.84.249.54      7      215ms       214ms      0%        100 / 100      214ms / 215ms
i-0-0-0-0.tlot02.bi.telstraglobal.net          202.40.149.142     8      223ms       223ms      0%        100 / 100      223ms / 223ms
8-3-2.edge1.LosAngels.Level3.net               4.68.70.69         9      219ms                  100%      0 / 100
vlan90.csw4.LosAngeles1.Level3.net             4.69.144.254       10     253ms       252ms      0%        100 / 100      252ms / 253ms
ae-93-93.ebr3.LosAngeles1.Level3.net           4.69.137.45        11     226ms       226ms      0%        100 / 100      226ms / 227ms
* Unknown Host *                               4.69.132.82        12     286ms       286ms      0%        100 / 100      286ms / 286ms
ae-91-91.csw4.Washington1.Level3.net           4.69.134.142       13     315ms       315ms      0%        100 / 100      315ms / 315ms
ae-43-90.car3.Washington1.Level3.net           4.69.149.197       14     287ms       287ms      0%        100 / 100      287ms / 287ms
ELECTRONIC.car3.Washington1.Level3.net         4.79.169.74        15     311ms       311ms      0%        100 / 100      311ms / 312ms
fert07-eqx-iad.ea.com                          159.153.224.230    16     291ms       291ms      0%        100 / 100      291ms / 291ms
meav5-pub.pt.iad.ea.com                        159.153.226.105    17     298ms       298ms      0%        100 / 100      298ms / 299ms
Thanks for the continued confirmation of this problem. It is amusing to see some of the Los Angeles routers working now, but the main ones are still borked.
=============
Edit: Updated with my latest results from the time of this post at 2:39AM Perth WST +8 GMT, no daylight savings. And I also just noticed something interesting with the broken route:
8-3-2.edge1.LosAngels.Level3.net               4.68.70.69         9      219ms                  100%      0 / 100
vlan90.csw4.LosAngeles1.Level3.net             4.69.144.254       10     253ms       252ms      0%        100 / 100      252ms / 253ms
ae-93-93.ebr3.LosAngeles1.Level3.net           4.69.137.45        11     226ms       226ms      0%        100 / 100      226ms / 227ms
* Unknown Host *                               4.69.132.82        12     286ms       286ms      0%        100 / 100      286ms / 286ms
The dead route link causing problems runs through the same routing pathway of four IP addresses... I REALLY need more players in Australia and New Zealand having this problem to run their UOTrace tests and post their results when they can't play ME3 Multiplayer to see if this pattern repeats.
=============
J1M_13
Seasoned Rookie
13 years ago
Just had another few perfectly good rounds from 4am to 6am. Literally like clockwork.

Since it's been weeks and still nothing from EA support ( which looks like it's going to be cheaply outsourced to be us through this website anyway ), I'm going to send this info and discussion to Level3.net support ( diverts to .com ) and I hope you'll all do the same.
http://www.level3.com/en/contact-us/
Just had another few perfectly good rounds from 4am to 6am. Literally like clockwork.

Since it's been weeks and still nothing from EA support ( which looks like it's going to be cheaply outsourced to be us through this website anyway ), I'm going to send this info and discussion to Level3.net support ( diverts to .com ) and I hope you'll all do the same.
http://www.level3.com/en/contact-us/
EDIT
These are the contacts I sent to;
Level3 - Southern California - Service Management
http://www.getlevel3.com/?loc=southerncalifornia&cid=AFMIT051809_IGMW1
Level3 - Asia Pacific Email
apac@level3.com
J1M_13
Seasoned Rookie
13 years ago
Sent details to Level3 and also to EA support.
Fingers crossed.

Forum Discussion

ME3 (PC) - Problems connecting to Multiplayer / staying connected

115 Replies

Featured Places

Mass Effect Franchise Discussion

Recent Discussions

[PC] Mass Effect Online Access Error in Multiplayer Mode

mass effect Andromeda online access problem

I broke ME3

Mass Effect: Andromeda Online Access Error

Silversun strip crash