[AusNOG] High Latency to AS15169

[Saxton, Joseph (SYD-FED)]

Been noticing this as well. Might be time to switch to cloudflare's 1.1.1.1 __

Server:		8.8.8.8
Address:	8.8.8.8#53

Non-authoritative answer:
www.supermicro.com	canonical name = prospective.shared.global.fastly.net.
Name:	prospective.shared.global.fastly.net
Address: 151.101.2.107
Name:	prospective.shared.global.fastly.net
Address: 151.101.66.107
Name:	prospective.shared.global.fastly.net
Address: 151.101.130.107
Name:	prospective.shared.global.fastly.net
Address: 151.101.194.107


real	0m0.210s
user	0m0.006s
sys	0m0.026s

CloudFlare

Server:		1.1.1.1
Address:	1.1.1.1#53

Non-authoritative answer:
www.supermicro.com	canonical name = prospective.shared.global.fastly.net.
Name:	prospective.shared.global.fastly.net
Address: 151.101.30.107


real	0m0.018s
user	0m0.004s
sys	0m0.007s

On 5/10/18, 10:46 am, "AusNOG on behalf of Paul Gear" <ausnog-bounces at lists.ausnog.net on behalf of ausnog at libertysys.com.au> wrote:

    This seems to be re-breaking on a scheduled basis:
    
    https://urldefense.proofpoint.com/v2/url?u=https-3A__libertysys.com.au_imagebin_15387001474777-5F1538700147-5F1538438400.png&d=DwIGaQ&c=Ftw_YSVcGmqQBvrGwAZugGylNRkk-uER0-5bY94tjsc&r=srheiojgNn4Jg0keeQ9hj6cyp8zgHx0m-eTRLdD3nnw&m=51ezH6kfqUL4Txbm2H37IQAKdncM3og4KKaIcIghgV8&s=sHa98LlAHDYP7DL1KjORdC_SODCRrctJJRpte9maxY8&e=
    
    On 04/10/18 15:33, Jason Leschnik wrote:
    > I'm seeing quad-8 hitting the larger delay, but google.com
    > <https://urldefense.proofpoint.com/v2/url?u=http-3A__google.com&d=DwIGaQ&c=Ftw_YSVcGmqQBvrGwAZugGylNRkk-uER0-5bY94tjsc&r=srheiojgNn4Jg0keeQ9hj6cyp8zgHx0m-eTRLdD3nnw&m=51ezH6kfqUL4Txbm2H37IQAKdncM3og4KKaIcIghgV8&s=3UjYz0Cby6hmruhz77xyF-wl1zb3O1Yd9GfEgzTnS1U&e=> is 8ms from a few locations.
    > 
    > On Thu, 4 Oct 2018 at 14:39, Ross Tsolakidis wrote:
    > 
    > 
    >     Thishappens often, we graph it for fun.
    >     (not default smokeping timers, very low impact).
    > 
    >     image.png
    >      
    >     Regards,
    >     Ross.
    > 
    > 
    >     On Thu, Oct 4, 2018 at 2:30 PM Nathan Brookfield
    >     wrote:
    > 
    >         We never saw it come back.
    > 
    >         Nathan Brookfield
    >         Chief Executive Officer
    > 
    >         Simtronic Technologies Pty Ltd
    >         https://urldefense.proofpoint.com/v2/url?u=http-3A__www.simtronic.com.au&d=DwIGaQ&c=Ftw_YSVcGmqQBvrGwAZugGylNRkk-uER0-5bY94tjsc&r=srheiojgNn4Jg0keeQ9hj6cyp8zgHx0m-eTRLdD3nnw&m=51ezH6kfqUL4Txbm2H37IQAKdncM3og4KKaIcIghgV8&s=7nQ8nJwbWNxeq_GTWZkgQPOVY2YvUHslU0G54FVRL-I&e=
    > 
    >         On 4 Oct 2018, at 14:12, Tim Jackson wrote:
    > 
    >         Gone offshore again?
    > 
    >         <image.png>
    > 
    >         On Wed, Oct 3, 2018 at 2:30 PM Jen Linkova wrote:
    > 
    >             I believe the latency should be back to usual values now.
    > 
    >             On Wed, Oct 3, 2018 at 1:55 PM Dave Browning wrote:
    > 
    >                 All,
    > 
    >                 Just to keep the list updated on this issue, Google have
    >                 confirmed there is a wide spread problem and the
    >                 appropriate Engineer's are on the case
    > 
    >                 Cheers,
    > 
    >                 Dave Browning | Senior Network Engineer
    >                 P 1300 791 678 D 07 3708 0008
    >                 Level 1, 12 Railway Tce, Milton QLD 4064
    
    
    _______________________________________________
    AusNOG mailing list
    AusNOG at lists.ausnog.net
    https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.ausnog.net_mailman_listinfo_ausnog&d=DwIGaQ&c=Ftw_YSVcGmqQBvrGwAZugGylNRkk-uER0-5bY94tjsc&r=srheiojgNn4Jg0keeQ9hj6cyp8zgHx0m-eTRLdD3nnw&m=51ezH6kfqUL4Txbm2H37IQAKdncM3og4KKaIcIghgV8&s=-pqvy3KucQpmDa1waXPuxsWJ7h5e6YDQA72LQ9ZGIFQ&e=
    


This message contains information which may be confidential and privileged. Unless you are the intended recipient (or authorized to receive this message for the intended recipient), you may not use, copy, disseminate or disclose to anyone the message or any information contained in the message.  If you have received the message in error, please advise the sender by reply e-mail, and delete the message.  Thank you very much.