Office 365 errors with users on Telecom New Zealand

Forums › IT Pro and developers › Office 365 errors with users on Telecom New Zealand

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9

1948 posts

Uber Geek
+1 received by user: 459
Inactive user

#741978 8-Jan-2013 22:37

Yep... And I can trace route to both IP networks from the SingTel Looking glass.

Using a Telecom Direct APN on my phone. Granted it's going via LA... But...

traceroute 122.63.47.xxx

Type escape sequence to abort.
Tracing the route to 122-63-47-xxx.mobile.telecom.co.nz (122.63.47.xxx)

1 203.208.155.2 0 msec 0 msec 4 msec
2 ge-1-0-0-0.sngc3-ar2.ix.singtel.com (203.208.172.158) 0 msec 4 msec 0 msec
3 so-1-0-3-0.lonlx-cr2.ix.singtel.com (203.208.151.97) 4 msec 0 msec 4 msec
4 203.208.153.122 165 msec
ge-3-0-0-0.sngc3-ar3.ix.singtel.com (203.208.182.78) 172 msec 172 msec
5 ge-4-0-0-0.laxow-cr1.ix.singtel.com (203.208.183.149) 325 msec
203.208.171.230 180 msec
ge-4-0-0-0.laxow-cr1.ix.singtel.com (203.208.149.105) 184 msec
6 67.17.192.5 181 msec 172 msec 220 msec
7 xe-4-2-1.edge1.LosAngeles9.Level3.net (4.68.63.105) 169 msec 176 msec 181 msec
8 ae-1-60.edge2.LosAngeles9.Level3.net (4.69.144.15) 212 msec 193 msec 196 msec
9 TELECOM-NEW.edge2.LosAngeles9.Level3.net (4.53.230.14) 204 msec 220 msec 208 msec
10 ae0-3.labr5.global-gateway.net.nz (203.96.120.85) 209 msec 204 msec 217 msec
11 ae1-3.sjbr2.global-gateway.net.nz (203.96.120.94) [MPLS: Label 334720 Exp 2] 212 msec 217 msec
so2-0-2.tkbr9.global-gateway.net.nz (202.50.232.41) [MPLS: Label 378656 Exp 2] 240 msec
12 ae10-10.tkbr10.global-gateway.net.nz (202.50.232.206) 244 msec
ae2-3.akbr4.global-gateway.net.nz (203.96.120.193) [MPLS: Label 379536 Exp 2] 237 msec 240 msec
13 ae7-3.tkbr10.global-gateway.net.nz (202.50.232.130) 236 msec
ae10-10.tkbr10.global-gateway.net.nz (202.50.232.206) 236 msec *
14 * * *
15 * * *
16 * * *
17 * * *
18 * *
122-63-47-xxx.mobile.telecom.co.nz (122.63.47.xxx) 793 msec
sngc3-sr1

But I am getting a similar trace route not completing to a Telecom DSL Subscriber.

traceroute 125.236.203.xx

Type escape sequence to abort.
Tracing the route to 125-236-203-xx.adsl.xtra.co.nz (125.236.203.xx)

1 203.208.155.2 4 msec 0 msec 0 msec
2 ge-1-0-0-0.sngc3-ar2.ix.singtel.com (203.208.172.158) 124 msec 88 msec 40 msec
3 ge-1-1-3-0.sngtp-dr2.ix.singtel.com (203.208.152.21) 0 msec 4 msec 0 msec
4 203.208.178.186 177 msec 172 msec 172 msec
5 so-3-0-3-0.laxow-cr1.ix.singtel.com (203.208.151.234) 184 msec
ge-4-1-1-0.sngc3-dr1.ix.singtel.com (203.208.149.138) 185 msec
so-3-0-3-0.laxow-cr1.ix.singtel.com (203.208.151.234) 184 msec
6 67.17.192.5 180 msec 184 msec 180 msec
7 xe-4-2-1.edge1.LosAngeles9.Level3.net (4.68.63.105) 209 msec 192 msec *
8 ae-2-70.edge2.LosAngeles9.Level3.net (4.69.144.79) 184 msec 184 msec 185 msec
9 TELECOM-NEW.edge2.LosAngeles9.Level3.net (4.53.230.14) 216 msec 224 msec 217 msec
10 ae0-3.labr5.global-gateway.net.nz (203.96.120.85) 212 msec 212 msec 212 msec
11 xe3-1-0.akbr4.global-gateway.net.nz (202.50.232.21) [MPLS: Label 377168 Exp 2] 248 msec 249 msec
ae2-3.tkbr9.global-gateway.net.nz (203.96.120.141) [MPLS: Label 345120 Exp 2] 216 msec
12 ae5-2.akbr5.global-gateway.net.nz (202.50.232.78) 248 msec
ae6-3.akbr5.global-gateway.net.nz (202.50.232.106) 249 msec
ae0-10.akbr4.global-gateway.net.nz (202.50.232.38) [MPLS: Label 364960 Exp 2] 228 msec
13 ae6-3.akbr5.global-gateway.net.nz (202.50.232.106) 217 msec * 248 msec
14 * 125-236-192-9.adsl.xtra.co.nz (125.236.192.9) 248 msec *
15 125-236-192-9.adsl.xtra.co.nz (125.236.192.9) 217 msec 252 msec
222.152.45.82 249 msec
16 222.152.45.82 216 msec 248 msec *
17 * * *
18 * * *
19 * * *
Traceroute incomplete due to query timeout

ping 125.236.203.xx

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 125.236.203.xx, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 213/225/244 ms
sngc3-sr1

And to a different Telecom DSL line over an older DSL connection.

traceroute 219.88.65.xx

Type escape sequence to abort.
Tracing the route to 219-88-65-xx.adsl.xtra.co.nz (219.88.65.xx)

1 203.208.155.2 0 msec 0 msec 4 msec
2 203.208.171.169 0 msec 0 msec 0 msec
3 203.208.152.53 36 msec 64 msec 84 msec
4 203.208.171.190 180 msec 181 msec 228 msec
5 ge-4-1-1-0.sngc3-dr1.ix.singtel.com (203.208.149.138) 184 msec
so-2-0-3-0.plapx-cr2.ix.singtel.com (203.208.149.246) 184 msec
so-3-0-3-0.laxow-cr1.ix.singtel.com (203.208.151.234) 189 msec
6 67.17.192.5 184 msec 184 msec 189 msec
7 xe-4-2-1.edge1.LosAngeles9.Level3.net (4.68.63.105) 188 msec 192 msec 189 msec
8 vlan90.csw4.LosAngeles1.Level3.net (4.69.144.254) [MPLS: Label 1486 Exp 0] 192 msec
vlan70.csw2.LosAngeles1.Level3.net (4.69.144.126) [MPLS: Label 1469 Exp 0] 193 msec
vlan90.csw4.LosAngeles1.Level3.net (4.69.144.254) [MPLS: Label 1486 Exp 0] 188 msec
9 ae-83-83.ebr3.LosAngeles1.Level3.net (4.69.137.41) [MPLS: Label 1488 Exp 0] 180 msec
ae-63-63.ebr3.LosAngeles1.Level3.net (4.69.137.33) [MPLS: Label 1488 Exp 0] 184 msec
ae-93-93.ebr3.LosAngeles1.Level3.net (4.69.137.45) [MPLS: Label 1488 Exp 0] 196 msec
10 ae-3-3.ebr1.SanJose1.Level3.net (4.69.132.9) [MPLS: Label 1499 Exp 0] 197 msec 196 msec 196 msec
11 ae-61-61.csw1.SanJose1.Level3.net (4.69.153.2) [MPLS: Label 1403 Exp 0] 185 msec
ae-91-91.csw4.SanJose1.Level3.net (4.69.153.14) [MPLS: Label 1374 Exp 0] 184 msec 184 msec
12 ae-32-90.car2.SanJose2.Level3.net (4.69.152.204) 188 msec
ae-22-60.car2.SanJose2.Level3.net (4.69.152.12) 181 msec 180 msec
13 TELECOM-NEW.car2.SanJose2.Level3.net (4.59.4.94) 228 msec 229 msec 228 msec
14 ae0.sjbr2.global-gateway.net.nz (203.96.120.73) 228 msec 225 msec 224 msec
15 so5-0-2.akbr4.global-gateway.net.nz (202.50.232.33) [MPLS: Label 377984 Exp 2] 245 msec 248 msec 249 msec
16 xe1-0-0.tkbr10.global-gateway.net.nz (202.50.232.29) 252 msec 249 msec 248 msec
17 * * *
18 222-154-128-1.jetstream.xtra.co.nz (222.154.128.1) [MPLS: Label 136 Exp 0] 268 msec 272 msec 268 msec
19 * * *
20 * * *
21 * * *
22 * *
Traceroute incomplete due to query timeout

ping 219.88.65.xx

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 219.88.65.xx, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 296/298/301 ms
sngc3-sr1

But pings work fine.

So I think SingTel / Microsoft have sorted their problem.

bender

220 posts

Master Geek
+1 received by user: 17

#742039 9-Jan-2013 07:56

No there is still the remaining issue of why Global Gateway is receiving the return path via Los Angeles.

The performance will be terrible rather than the ~120ms path from Singapore back to NZ via Australia.

ZeeBOB

26 posts

Geek

#742067 9-Jan-2013 09:36

Tested and things appear to be back to "normal".

The 300ms latency is still a pain but I'm not sure what to do about it

blur

384 posts

Ultimate Geek
+1 received by user: 3

#742088 9-Jan-2013 09:49

bender: No there is still the remaining issue of why Global Gateway is receiving the return path via Los Angeles.

The performance will be terrible rather than the ~120ms path from Singapore back to NZ via Australia.

Yep, it seems to be back to normal, but I have to say that the performance is terrible.

I'm getting around 160 - 170KB/sec dowload speed on attachments from the servers in Singapore which in my view is terrible. Upload speed is worse, with it taking over a minute to attach a 3Mb file to an email. Something seriously needs to be done about the speed.

I mean it is all very well locating New Zealand mailboxes on servers in Singapore because we are in the Asia Pacific region, but if there is no direct route to them what is the point? It would make more sense to me to locate them on the east coast of the US on the basis of the pacific cable.

My HTPC - Case Antec Fusion Remote, MOBO Intel DH67BLB3, CPU Intel Core i5-2400S 2.5 GHz, RAM 8GB DDR3 1333, HDD 120Gig Corsair Force Series 3 SSD system | WD Caviar Black 2TB data, Tuners Black Gold BGT3595 dual DVB-S/S2, dual DVB-T, Video nVIDIA GeForce GT 520, 1024MB, Sound Intel® High Definition Audio (onboard), OS Windows 7 x64

plambrechtsen

1948 posts

Uber Geek
+1 received by user: 459
Inactive user

#742091 9-Jan-2013 09:58

bender: No there is still the remaining issue of why Global Gateway is receiving the return path via Los Angeles.

The performance will be terrible rather than the ~120ms path from Singapore back to NZ via Australia.

Again this is not Telecom or Global Gateways fault. It's SingTel who are routing incorrectly via LA as the route there is fine.

You need to continue to escalate with Microsoft to get them to sort out their BGP routing with SingTel back to Telecom's AS4771 IP range.

trib

13 posts

Geek
+1 received by user: 1

#742411 9-Jan-2013 17:57

hi all,

this was the main reason that we created SCA (Steelhead Cloud accelerator) product.

Have a look at this youtube demo video

If anyone of you would like a demo for your users, Please let me know. I work for Riverbed.

Cheers
Trib

Apple TV

Stream your favourite shows now on Apple TV (affiliate link).

gehenna

8667 posts

Uber Geek
+1 received by user: 3883

Moderator

Trusted

Lifetime subscriber

#742808 10-Jan-2013 13:42

How are things going for everyone now?

blur

384 posts

Ultimate Geek
+1 received by user: 3

#742834 10-Jan-2013 14:25

gehenna: How are things going for everyone now?

The problem has been solved. I actually got an email from Microsoft support basically saying that the problem wasn't with their servers, but rather with their provider (SingTel) and that they worked it through to a conclusion.

That said, the speed is still slow. When I am downloading attachments from OWA the BEST I get is 160Kb/sec, but usually it's around 100Kb/sec which is boardering on unusable.

I am considering starting a new thread to try and encourage people from NZ to all call and make complaints about the speed.

Can anybody else comment on the speeds that they are getting?

trig42

5889 posts

Uber Geek
+1 received by user: 2094

ID Verified

#742848 10-Jan-2013 14:54

blur:
gehenna: How are things going for everyone now?

The problem has been solved. I actually got an email from Microsoft support basically saying that the problem wasn't with their servers, but rather with their provider (SingTel) and that they worked it through to a conclusion.

That said, the speed is still slow. When I am downloading attachments from OWA the BEST I get is 160KB/sec, but usually it's around 100KB/sec which is boardering on unusable.

I am considering starting a new thread to try and encourage people from NZ to all call and make complaints about the speed.

Can anybody else comment on the speeds that they are getting?

Do you mean 100Kb/s? Beacuse 100KB/s is pretty quick.

Regs

4066 posts

Uber Geek
+1 received by user: 206

Trusted

Snowflake

#742886 10-Jan-2013 16:10

blur:
gehenna: How are things going for everyone now?

The problem has been solved. I actually got an email from Microsoft support basically saying that the problem wasn't with their servers, but rather with their provider (SingTel) and that they worked it through to a conclusion.

That said, the speed is still slow. When I am downloading attachments from OWA the BEST I get is 160Kb/sec, but usually it's around 100Kb/sec which is boardering on unusable.

I am considering starting a new thread to try and encourage people from NZ to all call and make complaints about the speed.

Can anybody else comment on the speeds that they are getting?

who is your ISP and what is your connection type?

Sales Engineer
Snowflake
www.snowflake.com

about.me/nzregs
Twitter: @nzregs

blur

384 posts

Ultimate Geek
+1 received by user: 3

#743180 11-Jan-2013 10:23

Regs:

who is your ISP and what is your connection type?

Our ISP is Telecom and we connect with a 2Wire 2701HGV-W Gateway. It tells me that we are connected at 16428Kbps down and 875Kbps up.

Since this outage, I have started to query other service providers for other options in terms of more business focused solutions.

Any suggestions in this regard?

Dell

Shop now for Dell laptops and other devices (affiliate link).

BlakJak

1330 posts

Uber Geek
+1 received by user: 735

Trusted

#743188 11-Jan-2013 10:31

You're asking this in the Telecom forum. :P

If you don't have Fibre to your premesis the easiest options will be HSNS Lite based, but you're limited to several mbit/sec symmetric. Several ISPs can offer you HSNS Lite on Telecom/Chorus Copper, including Telecom themselves.

HSNS is at least, business grade connectivity.

No signature to see here, move along...

blur

384 posts

Ultimate Geek
+1 received by user: 3

#743190 11-Jan-2013 10:36

BlakJak: You're asking this in the Telecom forum. :P

If you don't have Fibre to your premesis the easiest options will be HSNS Lite based, but you're limited to several mbit/sec symmetric. Several ISPs can offer you HSNS Lite on Telecom/Chorus Copper, including Telecom themselves.

HSNS is at least, business grade connectivity.

Good point!

I'm going to get a feasibility study done as to whether we can connect to fibre. My understanding is that we have Chorus fibre running past the gate so I’d be interested to see what the cost will be to get ourselves connected.

If we are able to connect, what are our options then?

Zeon

3926 posts

Uber Geek
+1 received by user: 759

Trusted

#743191 11-Jan-2013 10:38

blur:
Regs:

who is your ISP and what is your connection type?

Our ISP is Telecom and we connect with a 2Wire 2701HGV-W Gateway. It tells me that we are connected at 16428Kbps down and 875Kbps up.

Since this outage, I have started to query other service providers for other options in terms of more business focused solutions.

Any suggestions in this regard?

This issue isn't related to the ISP but rather is a symptom of the way the internet is designed and works. The only advantage of paying your ISP $1000 a month instead of $100 is they may sort out routing issues with other parties on your behalf but that is not guaranteed Where there are carriers in between you lose control and as can be seen, Telecom cannot influence the routes without Singtel/Microsoft support.

If you want greater reliability choose a New Zealand based provider where there is control.....

Speedtest 2019-10-14

Zeon

3926 posts

Uber Geek
+1 received by user: 759

Trusted

#743192 11-Jan-2013 10:40

blur:

Good point!

I'm going to get a feasibility study done as to whether we can connect to fibre. My understanding is that we have Chorus fibre running past the gate so I’d be interested to see what the cost will be to get ourselves connected.

If we are able to connect, what are our options then?

We pay around $2000 a month for 100mbps unlimited national and 100mbps unlimited international between 0900-1700 (10mbps other times) with Orcon. Minimum charges are going to be around $600 a month or so. Installation may be around $1-2k on a 2 year contract (at least with Telstra fibre). Orcon is very cheap comparatively to other ISPs though.

Speedtest 2019-10-14

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9