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
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.
=============
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
Sent details to Level3 and also to EA support.
Fingers crossed.
