The long weekend is nearly here – time to break out the speakers for a poolside party. Check out Yes... Read the full story
2017-09-04 11:10 AM
"Why then is Optus routing to the US through ASIA?"
Exactly what I asked in https://yescrowd.optus.com.au/t5/Broadband-Telephony/Routing-misconfiguration-sending-some-US-traffi.... I can't find a reasonable explanation for routing *more* traffic to Asia given a break between Australia and Asia.
2017-09-04 11:29 AM
This is definitely a routing fail, as pointed out in the other thread. Am aware of the cable break but .au -> US traffic doesn't need to go the route that has been implemented. Routing to some US destinations is sub standard with packetloss during peak times up to 35%. Over the past 24 hours I've tested the connect to Rackspaces hosted exchange service on connect.emailsrvr.com on three different Optus connections. In the evening packetloss is between 25-35% across all. This is unusable for Outlook. At 6am it was 4% (as oz and Asia sleep). At 11am it had crept back to ~15% which is enough to interupt Outlook connectivity to Rackspace and prevent the sending of large emails. Other thread:
2017-09-05 05:57 PM
Just spoken with a higher level Optus support. Understands problem, but not very confident about being able to do anything about it. In order to get more action on this, it is really a matter of more people ringing up & complaining. Two Optus techs have now told me that. This forum is also a good avenue, but they will use the number of logged phone complaints as the basis for action.
2017-09-05 06:02 PM
Come on, they must know how impossible it is to get Frontline technical support staff to understand let alone escalate a specific network routing issue. It's totally off script.
2017-09-05 06:06 PM
I don't know about anyone else but I'm pretty sure Optus gave me the impression that I'd be able to reliably check my email and send messages over their network. Let's not forget all the other stuff that, drops out, times out and bugs out over their network:
2017-09-05 06:10 PM
Never say never. I think... I think I may have done it. After several calls yesterday and more than an hour in a single live chat session today, the agent asked for my mobile number and said the relevant team would be able to see the link to my other thread here for details. Fingers crossed.
2017-09-05 06:16 PM
The tech told me that they are aware of this and other threads ... I made a point of telling the level 1 tech about it & asked for them to check it out before ringing me back. At least this is progress compared to earlier calls where the first respondent wasn't even aware there was a problem.
2017-09-05 06:21 PM
@ozeannieI just did another tracert to secure.emailsrvr.com and things seems to have changed, no longer going through Asia and only 25 hops. Maybe try it again from your connection??
2017-09-05 06:38 PM
Confirmed, zero packetloss
2017-09-05 07:04 AM
I've put this on a couple of other forums, you may have already seen, but below is my latest tracert. Last night was slower, probably less traffic this morning. Can now send emails but they take a long time to go still.
Here is the tracert:
1 <1 ms <1 ms <1 ms READYSHARE [192.168.1.1]
2 6 ms 7 ms 7 ms 10.81.0.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 10 ms 11 ms 11 ms 126.96.36.199
8 13 ms 13 ms 13 ms 188.8.131.52
9 12 ms 15 ms 11 ms 184.108.40.206
10 160 ms 161 ms 160 ms 220.127.116.11
11 161 ms 162 ms 160 ms 18.104.22.168
12 163 ms 163 ms 163 ms 22.214.171.124
13 218 ms 224 ms 244 ms ae14.cs1.lax112.us.eth.zayo.com [126.96.36.199]
14 209 ms 216 ms 214 ms ae6.cs1.las2.us.eth.zayo.com [188.8.131.52]
15 207 ms 207 ms 207 ms ae0.cs2.las2.us.eth.zayo.com [184.108.40.206]
16 210 ms 209 ms 209 ms ae11.cs2.den5.us.eth.zayo.com [220.127.116.11]
17 208 ms 207 ms 207 ms ae5.cs2.ord2.us.eth.zayo.com [18.104.22.168]
18 207 ms 207 ms 207 ms ae27.cr2.ord2.us.zip.zayo.com [22.214.171.124]
19 232 ms 207 ms 209 ms ae1.mpr1.ord6.us.zip.zayo.com [126.96.36.199]
20 208 ms 209 ms 209 ms ae2.mpr1.ord5.us.zip.zayo.com [188.8.131.52]
21 217 ms 217 ms 218 ms 184.108.40.206.IPYX-076520-ZYO.above.net [208.185
22 * * * Request timed out.
23 215 ms 215 ms 215 ms be42-corea.ord1.rackspace.net [220.127.116.11]
24 217 ms 207 ms 207 ms corea-core5.ord1.rackspace.net [18.104.22.168]
25 208 ms 209 ms 209 ms core5-aggr1401b-14.ord1.rackspace.net [161.47.11
26 208 ms 217 ms 208 ms secure.emailsrvr.com [22.214.171.124]