[AusNOG] High latency between TPG AS7545 and Microsoft AS8075

Nathan Collins nathan at mailsecured.com.au
Mon Nov 27 22:27:40 EST 2017 

Faults don't want to hear anything about it, they attributed the latency to high bandwidth usage on the end user's connection.


Hoping a TPG engineer is on-list and can help push it through the first level support hurdle.


I just returned home today and was able to test from my TPG FTTN connection, same result - so definitely not isolated to a particular customer as support are claiming.


 1  192.168.1.1 (192.168.1.1)  3.554 ms  1.883 ms  2.319 ms
 2  10.20.22.239 (10.20.22.239)  9.881 ms  9.405 ms  11.051 ms
 3  cbr-apt-mar-csw2-te-1-8.tpgi.com.au (203.213.56.33)  15.134 ms  15.096 ms  14.004 ms
 4  cbr-apt-mar-crt1-ge-2-0-0.tpgi.com.au (203.219.106.101)  15.132 ms  13.752 ms  13.580 ms
 5  syd-sot-ken-crt1-te-gi-0-4-0-9.tpgi.com.au (203.219.106.113)  15.764 ms  20.028 ms  16.308 ms
 6  203-219-107-82.static.tpgi.com.au (203.219.107.82)  19.769 ms  20.863 ms  16.373 ms
 7  203-219-35-196.static.tpgi.com.au (203.219.35.196)  16.174 ms  15.188 ms  15.764 ms
 8  202.7.171.78 (202.7.171.78)  130.289 ms  128.093 ms  129.700 ms
 9  ae1-0.syd03-96cbe-1b.ntwk.msn.net (204.152.140.113)  129.323 ms
    ae11-0.syd03-96cbe-1b.ntwk.msn.net (104.44.226.159)  129.472 ms  130.187 ms
10  104.44.236.54 (104.44.236.54)  130.487 ms  130.348 ms  130.364 ms


Cheers,

N


________________________________
From: Trent Farrell <tbflists at gmail.com>
Sent: Monday, 27 November 2017 8:10:57 PM
To: Dibbles
Cc: Nathan Collins; AusNOG Mailing List
Subject: Re: [AusNOG] High latency between TPG AS7545 and Microsoft AS8075

This generally happens when their SYD peering session drops (or you aren't being announced out of SYD any more). TPG faults should be able to fix.

On Mon, Nov 27, 2017 at 6:12 PM, Dibbles <dibbles87 at gmail.com<mailto:dibbles87 at gmail.com>> wrote:
Also experiencing the same issue on the same IP address from Newcastle area on NBN.

Tracing route to 104.44.236.54 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     6 ms     6 ms     5 ms  10.20.22.119
  3     6 ms     8 ms     6 ms  syd-gls-har-crt1-he-0-3-0-3.tpgi.com.au<http://syd-gls-har-crt1-he-0-3-0-3.tpgi.com.au> [203.221.3.65]
  4    14 ms    14 ms     7 ms  syd-sot-ken-crt1-he-0-3-0-0.tpgi.com.au<http://syd-sot-ken-crt1-he-0-3-0-0.tpgi.com.au> [202.7.162.74]
  5    13 ms    12 ms    17 ms  203-219-35-132.static.tpgi.com.au<http://203-219-35-132.static.tpgi.com.au> [203.219.35.132]
  6   120 ms   135 ms   120 ms  202.7.171.78
  7   126 ms   124 ms   122 ms  ae1-0.syd03-96cbe-1b.ntwk.msn.net<http://ae1-0.syd03-96cbe-1b.ntwk.msn.net> [204.152.140.113]
  8   125 ms   121 ms   122 ms  104.44.236.54

Trace complete.

On 27 November 2017 at 16:13, Nathan Collins <nathan at mailsecured.com.au<mailto:nathan at mailsecured.com.au>> wrote:

Hi all,


Just wondering if anyone is seeing the same or has any pointers on escalation as TPG frontline support want no bar of it.


I have a couple of users complaining about high latency when accessing some MS hosted game servers (Rainbow Six Siege) from TPG ASDL2 tails in the ACT.  The latency is high enough for the game to force them on to a SE Asia server.


A sample trace is below:


1     1 ms    <1 ms    <1 ms  DSL-AC68R-6208 [192.168.1.1]
2    25 ms    26 ms    26 ms  10.20.23.251
3    30 ms    30 ms    30 ms  203-213-56-193.tpgi.com.au<http://203-213-56-193.tpgi.com.au> [203.213.56.193]
4    31 ms    31 ms    30 ms  cbr-apt-mar-crt1-ge-2-0-0.tpgi.com.au<http://cbr-apt-mar-crt1-ge-2-0-0.tpgi.com.au> [203.219.106.101]
5    32 ms    31 ms    31 ms  syd-sot-ken-crt1-te-gi-0-4-0-9.tpgi.com.au<http://syd-sot-ken-crt1-te-gi-0-4-0-9.tpgi.com.au> [203.219.106.113]
6    34 ms    31 ms    38 ms  203-219-107-82.static.tpgi.com.au<http://203-219-107-82.static.tpgi.com.au> [203.219.107.82]
7    30 ms    31 ms    31 ms  203-219-35-132.static.tpgi.com.au<http://203-219-35-132.static.tpgi.com.au> [203.219.35.132]
8   144 ms   145 ms   144 ms  202.7.171.78
9   154 ms   145 ms   145 ms  ae11-0.syd03-96cbe-1b.ntwk.msn.net<http://ae11-0.syd03-96cbe-1b.ntwk.msn.net> [104.44.226.159]
10   145 ms   145 ms   145 ms  104.44.236.54

High latency seems introduced between hops 8 and 9

A sample from Telstra is below for comparison, hops 7 and 8 look quite normal when traffic traverses from Telstra to AS8075

1    <1 ms    <1 ms    <1 ms  192.168.1.254
2    20 ms    22 ms    19 ms  gw1.act.asp.telstra.net<http://gw1.act.asp.telstra.net> [203.45.244.1]
3    21 ms    23 ms    32 ms  tengigabitethernet0-8-0-2.civ-core2.canberra.telstra.net<http://tengigabitethernet0-8-0-2.civ-core2.canberra.telstra.net> [203.50.10.129]
4    28 ms    32 ms    27 ms  bundle-ether15.chw-core10.sydney.telstra.net<http://bundle-ether15.chw-core10.sydney.telstra.net> [203.50.6.81]
5    26 ms    26 ms    25 ms  bundle-ether1.chw-edge901.sydney.telstra.net<http://bundle-ether1.chw-edge901.sydney.telstra.net> [203.50.11.99]
6    60 ms    25 ms    25 ms  bundle-ether2.ken-edge901.sydney.telstra.net<http://bundle-ether2.ken-edge901.sydney.telstra.net> [203.50.11.102]
7    25 ms    25 ms    25 ms  mic1909400.lnk.telstra.net<http://mic1909400.lnk.telstra.net> [139.130.58.222]
8    38 ms    34 ms    32 ms  ae11-0.syd03-96cbe-1b.ntwk.msn.net<http://ae11-0.syd03-96cbe-1b.ntwk.msn.net> [104.44.226.159]
9    25 ms    26 ms    25 ms  104.44.236.54
10     *        *        *     Request timed out.

Cheers,
N

_______________________________________________
AusNOG mailing list
AusNOG at lists.ausnog.net<mailto:AusNOG at lists.ausnog.net>
http://lists.ausnog.net/mailman/listinfo/ausnog



_______________________________________________
AusNOG mailing list
AusNOG at lists.ausnog.net<mailto:AusNOG at lists.ausnog.net>
http://lists.ausnog.net/mailman/listinfo/ausnog


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20171127/36e14588/attachment.html>

More information about the AusNOG mailing list