Re: [AusNOG] Anyone else seeing massive packet loss to AWS, us-east-1 via Telia currently?

2018-01-29 Thread Chad Kelly 


On 1/30/2018 12:00 PM, ausnog-requ...@lists.ausnog.net wrote:

Hi Everyone,
A frustrating start to the morning with over 50% packet loss when trying
to hit console.aws.amazon.com. Traffic heading via Vocus is fine up until
it heads into Telia.net, specifically a-100-ic-300087-kbn-b3.c.telia.net

Can't find any noise in the usual places yet that indicate theres an
issue, so wondering if anyone else is seeing the same problem?
Just on the access to the management console you can actually change the 
default region to Sydney so you can at least then access the management 
console without issues.
If you use multiple regions and multiple availability zones you 
shouldn't have any issues with downtime.
It really depends on what your trying to do with the platform, plus not 
all services are available in the Au regions which can be an issue.
While we are on the subject of AWS and networking, they are probably 
already working on this, but they need a point of presence in Perth for 
Cloudfront as it would improve laytency issues with traffic not having 
to go to Sydney or Melbourne depending on the provider.

Regards Chad.

--
Chad Kelly
Manager
CPK Web Services
Phone 03 5273 0246
Web www.cpkws.com.au

___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Anyone else seeing massive packet loss to AWS us-east-1 via Telia currently?

2018-01-29 Thread Roger Lienert 
Hi All,

This is now resolved.

Seems HE has started doing something funky with our routes resulting in sending 
all our traffic to our Asia POP’s rather than our SJC POP.

We have disabled our transit links in HKG and SIN and service has been 
restored, working with HE for a permanent resolution.

Regards,
Roger@Vocus

From: AusNOG <ausnog-boun...@lists.ausnog.net> on behalf of Chris Prangnell 
<chris.prangn...@gmail.com>
Date: Tuesday, 30 January 2018 12:25 pm
To: "ausnog@lists.ausnog.net" <ausnog@lists.ausnog.net>
Subject: Re: [AusNOG] Anyone else seeing massive packet loss to AWS us-east-1 
via Telia currently?

http://status.vocus.com.au/view-incident.aspx?IncidentID=403

On 30 January 2018 at 12:14, Matt Perkins 
<m...@spectrum.com.au<mailto:m...@spectrum.com.au>> wrote:
Yep Vocus is toast somewhere in telia. We dropped international from them and 
issue was resolved quickly.

Matt


On 30/1/18 12:03 pm, Karl Latiss wrote:
Add me to the list
 1?: [LOCALHOST]  pmtu 1500
 1:0.466ms
 1:0.405ms
 2:  
ip-245.202.255.49.in-addr.VOCUS.net.au<http://ip-245.202.255.49.in-addr.VOCUS.net.au>
0.998ms
 3:  
BE-150.cor02.mel07.vic.VOCUS.net.au<http://BE-150.cor02.mel07.vic.VOCUS.net.au> 
158.514ms asymm 11
 4:  
Hu-0-0-0-1.cor02.syd04.nsw.VOCUS.net.au<http://Hu-0-0-0-1.cor02.syd04.nsw.VOCUS.net.au>
 166.813ms asymm 10
 5:  
bundle-200.cor01.sjc01.ca.vocus.net<http://bundle-200.cor01.sjc01.ca.vocus.net> 
166.925ms asymm  9
 6:  
bundle-100.bdr01.sjc01.ca.vocus.net<http://bundle-100.bdr01.sjc01.ca.vocus.net> 
166.976ms asymm  8
 7:  sjo-b21-link.telia.net<http://sjo-b21-link.telia.net>  
167.440ms asymm  8
 8:  nyk-bb3-link.telia.net<http://nyk-bb3-link.telia.net>  
240.303ms asymm 11
 9:  ldn-bb3-link.telia.net<http://ldn-bb3-link.telia.net>  
307.930ms asymm 10
10:  ldn-b7-link.telia.net<http://ldn-b7-link.telia.net>
   307.524ms asymm 12
11:  ldn-b7-link.telia.net<http://ldn-b7-link.telia.net>
   309.738ms asymm 13
12:  no reply
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  no reply
18:  no reply
19:  no reply
20:  no reply
21:  no reply
22:  no reply
23:  no reply
24:  no reply
^C


On 30 January 2018 at 11:34, Giles Pollock 
<glp...@gmail.com<mailto:glp...@gmail.com>> wrote:
Hi Everyone,
A frustrating start to the morning with over 50% packet loss when trying to hit 
console.aws.amazon.com<http://console.aws.amazon.com>. Traffic heading via 
Vocus is fine up until it heads into Telia.net, specifically 
a-100-ic-300087-kbn-b3.c.telia.net<http://a-100-ic-300087-kbn-b3.c.telia.net>

Can't find any noise in the usual places yet that indicate theres an issue, so 
wondering if anyone else is seeing the same problem?

___
AusNOG mailing list
AusNOG@lists.ausnog.net<mailto:AusNOG@lists.ausnog.net>
http://lists.ausnog.net/mailman/listinfo/ausnog




___

AusNOG mailing list

AusNOG@lists.ausnog.net<mailto:AusNOG@lists.ausnog.net>

http://lists.ausnog.net/mailman/listinfo/ausnog



--

/* Matt Perkins

Direct 1300 137 379<tel:1300%20137%20379>Spectrum Networks Ptd. 
Ltd.

Office 1300 133 299<tel:1300%20133%20299>
m...@spectrum.com.au<mailto:m...@spectrum.com.au>

   Level 6, 350 George Street Sydney 2000

Spectrum Networks is a member of the Communications Alliance & TIO

*/

___
AusNOG mailing list
AusNOG@lists.ausnog.net<mailto:AusNOG@lists.ausnog.net>
http://lists.ausnog.net/mailman/listinfo/ausnog



--
Chris Prangnell
Sydney
+61449247557
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Anyone else seeing massive packet loss to AWS us-east-1 via Telia currently?

2018-01-29 Thread Luke Flemington 
Telia has a planned maintenance in London until 06:00 UTC. The timing seems 
suspicious...
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Anyone else seeing massive packet loss to AWS us-east-1 via Telia currently?

2018-01-29 Thread Chris Prangnell 
http://status.vocus.com.au/view-incident.aspx?IncidentID=403

On 30 January 2018 at 12:14, Matt Perkins  wrote:

> Yep Vocus is toast somewhere in telia. We dropped international from them
> and issue was resolved quickly.
>
> Matt
>
>
> On 30/1/18 12:03 pm, Karl Latiss wrote:
>
> Add me to the list
>
>  1?: [LOCALHOST]  pmtu 1500
>  1:0.466ms
>  1:0.405ms
>  2:  ip-245.202.255.49.in-addr.VOCUS.net.au0.998ms
>  3:  BE-150.cor02.mel07.vic.VOCUS.net.au 158.514ms asymm
> 11
>  4:  Hu-0-0-0-1.cor02.syd04.nsw.VOCUS.net.au 166.813ms asymm
> 10
>  5:  bundle-200.cor01.sjc01.ca.vocus.net 166.925ms asymm
> 9
>  6:  bundle-100.bdr01.sjc01.ca.vocus.net 166.976ms asymm
> 8
>  7:  sjo-b21-link.telia.net  167.440ms asymm
> 8
>  8:  nyk-bb3-link.telia.net  240.303ms asymm
> 11
>  9:  ldn-bb3-link.telia.net  307.930ms asymm
> 10
> 10:  ldn-b7-link.telia.net   307.524ms asymm
> 12
> 11:  ldn-b7-link.telia.net   309.738ms asymm
> 13
> 12:  no reply
> 13:  no reply
> 14:  no reply
> 15:  no reply
> 16:  no reply
> 17:  no reply
> 18:  no reply
> 19:  no reply
> 20:  no reply
> 21:  no reply
> 22:  no reply
> 23:  no reply
> 24:  no reply
> ^C
>
>
> On 30 January 2018 at 11:34, Giles Pollock  wrote:
>
>> Hi Everyone,
>> A frustrating start to the morning with over 50% packet loss when trying
>> to hit console.aws.amazon.com. Traffic heading via Vocus is fine up
>> until it heads into Telia.net, specifically
>> a-100-ic-300087-kbn-b3.c.telia.net
>>
>> Can't find any noise in the usual places yet that indicate theres an
>> issue, so wondering if anyone else is seeing the same problem?
>>
>> ___
>> AusNOG mailing list
>> AusNOG@lists.ausnog.net
>> http://lists.ausnog.net/mailman/listinfo/ausnog
>>
>>
>
>
> ___
> AusNOG mailing 
> listAusNOG@lists.ausnog.nethttp://lists.ausnog.net/mailman/listinfo/ausnog
>
>
> --
> /* Matt Perkins
> Direct 1300 137 379Spectrum Networks Ptd. Ltd.
> Office 1300 133 299m...@spectrum.com.au
>Level 6, 350 George Street Sydney 2000
> Spectrum Networks is a member of the Communications Alliance & TIO
> */
>
>
> ___
> AusNOG mailing list
> AusNOG@lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
>


-- 
*Chris Prangnell*
*Sydney*
*+61449247557*
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Anyone else seeing massive packet loss to AWS us-east-1 via Telia currently?

2018-01-29 Thread Matt Perkins 
Yep Vocus is toast somewhere in telia. We dropped international from 
them and issue was resolved quickly.


Matt


On 30/1/18 12:03 pm, Karl Latiss wrote:

Add me to the list

 1?: [LOCALHOST]                      pmtu 1500
 1:            0.466ms
 1:            0.405ms
 2: ip-245.202.255.49.in-addr.VOCUS.net.au 
               0.998ms
 3: BE-150.cor02.mel07.vic.VOCUS.net.au 
                158.514ms 
asymm 11
 4: Hu-0-0-0-1.cor02.syd04.nsw.VOCUS.net.au 
            166.813ms 
asymm 10
 5: bundle-200.cor01.sjc01.ca.vocus.net 
                166.925ms 
asymm  9
 6: bundle-100.bdr01.sjc01.ca.vocus.net 
                166.976ms 
asymm  8
 7: sjo-b21-link.telia.net              
      167.440ms asymm  8
 8: nyk-bb3-link.telia.net              
      240.303ms asymm 11
 9: ldn-bb3-link.telia.net              
      307.930ms asymm 10
10: ldn-b7-link.telia.net                
     307.524ms asymm 12
11: ldn-b7-link.telia.net                
     309.738ms asymm 13

12:  no reply
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  no reply
18:  no reply
19:  no reply
20:  no reply
21:  no reply
22:  no reply
23:  no reply
24:  no reply
^C


On 30 January 2018 at 11:34, Giles Pollock > wrote:


Hi Everyone,
A frustrating start to the morning with over 50% packet loss when
trying to hit console.aws.amazon.com
. Traffic heading via Vocus is fine
up until it heads into Telia.net, specifically
a-100-ic-300087-kbn-b3.c.telia.net


Can't find any noise in the usual places yet that indicate theres
an issue, so wondering if anyone else is seeing the same problem?

___
AusNOG mailing list
AusNOG@lists.ausnog.net 
http://lists.ausnog.net/mailman/listinfo/ausnog





___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog



--
/* Matt Perkins
Direct 1300 137 379Spectrum Networks Ptd. Ltd.
Office 1300 133 299m...@spectrum.com.au
   Level 6, 350 George Street Sydney 2000
Spectrum Networks is a member of the Communications Alliance & TIO
*/

___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Anyone else seeing massive packet loss to AWS us-east-1 via Telia currently?

2018-01-29 Thread Karl Latiss 
Add me to the list

 1?: [LOCALHOST]  pmtu 1500
 1:0.466ms
 1:0.405ms
 2:  ip-245.202.255.49.in-addr.VOCUS.net.au0.998ms
 3:  BE-150.cor02.mel07.vic.VOCUS.net.au 158.514ms asymm 11
 4:  Hu-0-0-0-1.cor02.syd04.nsw.VOCUS.net.au 166.813ms asymm 10
 5:  bundle-200.cor01.sjc01.ca.vocus.net 166.925ms asymm  9
 6:  bundle-100.bdr01.sjc01.ca.vocus.net 166.976ms asymm  8
 7:  sjo-b21-link.telia.net  167.440ms asymm  8
 8:  nyk-bb3-link.telia.net  240.303ms asymm 11
 9:  ldn-bb3-link.telia.net  307.930ms asymm 10
10:  ldn-b7-link.telia.net   307.524ms asymm 12
11:  ldn-b7-link.telia.net   309.738ms asymm 13
12:  no reply
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  no reply
18:  no reply
19:  no reply
20:  no reply
21:  no reply
22:  no reply
23:  no reply
24:  no reply
^C


On 30 January 2018 at 11:34, Giles Pollock  wrote:

> Hi Everyone,
> A frustrating start to the morning with over 50% packet loss when trying
> to hit console.aws.amazon.com. Traffic heading via Vocus is fine up until
> it heads into Telia.net, specifically a-100-ic-300087-kbn-b3.c.telia.net
>
> Can't find any noise in the usual places yet that indicate theres an
> issue, so wondering if anyone else is seeing the same problem?
>
> ___
> AusNOG mailing list
> AusNOG@lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
>
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Anyone else seeing massive packet loss to AWS us-east-1 via Telia currently?

2018-01-29 Thread Mike Walsh 
We're seeing the same thing, but weirdly, one connection is stable, but the
other is flaky, but we have the same tracert from both...


* Working - completely stable

Tracing route to s3-website-us-east-1.amazonaws.com [52.216.224.226]
over a maximum of 30 hops:

  1<1 ms<1 ms<1 ms  192.168.1.1
  280 ms 9 ms 8 ms  203.201.129.249
  3 2 ms 3 ms 2 ms  103.208.4.1
  4 3 ms 9 ms 3 ms  27.127.197.57
  5 4 ms 4 ms 4 ms  ten-1-0-0-889.bdr01.bne03.qld.vocus.net.au
[49.255.191.97]
  6   172 ms   171 ms   172 ms  ten-0-0-0-0.cor01.bne03.qld.vocus.net.au
[114.31.194.100]
  7   167 ms   167 ms   166 ms  BE-109.cor02.syd04.nsw.VOCUS.net.au
[114.31.194.167]
  8   167 ms   167 ms   167 ms  bundle-200.cor01.sjc01.ca.vocus.net
[49.255.255.10]
  9   172 ms   171 ms   171 ms  bundle-100.bdr01.sjc01.ca.vocus.net
[49.255.255.19]
 10   172 ms   176 ms   172 ms  sjo-b21-link.telia.net [62.115.154.12]
 11   168 ms   169 ms   168 ms  las-b21-link.telia.net [62.115.116.41]
 12   200 ms   200 ms   200 ms  dls-b21-link.telia.net [62.115.123.136]
 13   206 ms   206 ms   206 ms  a100-ic-300087-kbn-b3.c.telia.net
[62.115.9.126]
 14 *** Request timed out.
 15 *** Request timed out.
 16 *** Request timed out.
 17 *** Request timed out.
 18 *** Request timed out.
 19   244 ms   251 ms   243 ms  54.239.109.166
 20   230 ms   230 ms   229 ms  54.239.109.181
 21 *** Request timed out.
 22   245 ms   237 ms   237 ms  72.21.197.249
 23 *** Request timed out.
 24 *** Request timed out.
 25 *** Request timed out.
 26 *** Request timed out.
 27 *** Request timed out.
 28 *** Request timed out.
 29   241 ms   237 ms   237 ms  s3-website-us-east-1.amazonaws.com
[52.216.224.226]



*Not Working > 50% packet loss

Tracing route to s3-website-us-east-1.amazonaws.com [52.216.160.194]
over a maximum of 30 hops:

  1<1 ms<1 ms<1 ms  203.201.152.33
  2<1 ms<1 ms<1 ms  ten-1-0-0-889.bdr01.bne03.qld.vocus.net.au
[49.255.191.97]
  3   166 ms   166 ms   167 ms  ten-0-0-0-3.cor01.bne03.qld.VOCUS.net.au
[114.31.194.110]
  4   166 ms   166 ms   166 ms  BE-109.cor02.syd04.nsw.VOCUS.net.au
[114.31.194.167]
  5   166 ms   166 ms   166 ms  bundle-200.cor01.sjc01.ca.vocus.net
[49.255.255.10]
  6   166 ms   166 ms   167 ms  bundle-100.bdr01.sjc01.ca.vocus.net
[49.255.255.19]
  7   167 ms   166 ms   167 ms  sjo-b21-link.telia.net [62.115.154.12]
  8   172 ms   173 ms   173 ms  las-b21-link.telia.net [62.115.116.41]
  9   242 ms   204 ms   204 ms  dls-b21-link.telia.net [62.115.123.136]
 10   268 ms   268 ms   268 ms  a100-ic-300087-kbn-b3.c.telia.net
[62.115.9.126]
 11 *** Request timed out.
 12 *** Request timed out.
 13 *** Request timed out.
 14   292 ms ** 178.236.3.31
 15 *** Request timed out.
 16   318 ms *  295 ms  54.239.108.82
 17   293 ms ** 54.239.108.99
 18 *** Request timed out.
 19 *** Request timed out.
 20 *** Request timed out.
 21 *** Request timed out.
 22 *** Request timed out.
 23 *** Request timed out.
 24 *** Request timed out.
 25 *** Request timed out.
 26   294 ms   294 ms   294 ms  s3-website-us-east-1.amazonaws.com
[52.216.160.194]

Trace complete.

On 30 January 2018 at 10:54, Matt Hare 
wrote:

> Also seeing massive packet loss on our Vocus links next hop after
> a100us-ic-303629-dls-bb1.c.telia.net
>
> ___
> AusNOG mailing list
> AusNOG@lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
>


-- 
Regards,
Mike Walsh

-- Please reply above this line --

[image: Telair Logo]
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Anyone else seeing massive packet loss to AWS us-east-1 via Telia currently?

2018-01-29 Thread Matt Hare 
Also seeing massive packet loss on our Vocus links next hop after
a100us-ic-303629-dls-bb1.c.telia.net
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Anyone else seeing massive packet loss to AWS us-east-1 via Telia currently?

2018-01-29 Thread Nick Stallman 
That's odd. I've just been watching my server monitoring (Datadog) start 
skipping tons of datapoints.


It is also going to us-east-1, but using NTT not Vocus/Telia.
This started at about 10:55 for me. Before that was perfect.
I don't think my traceroute has anything in common with yours?

traceroute to s3-website-us-east-1.amazonaws.com (52.216.161.90), 30 
hops max, 60 byte packets
 2  rtif-118.127.7.2-31.cs-1.as45671.net.au (118.127.7.2)  0.398 ms  
0.462 ms  0.570 ms
 3  ten2-1.br-1-2.as45671.net.au (203.26.198.27)  0.292 ms  0.456 ms  
0.617 ms

 4  203.26.197.9 (203.26.197.9)  13.695 ms  13.707 ms  13.683 ms
 5  xe-1-0-0.gw101.sy1.ap.equinix.com (27.111.240.140)  0.189 ms 
xe-0-0-0.gw101.sy1.ap.equinix.com (27.111.240.142)  0.233 ms 0.213 ms

 6  202.68.70.145 (202.68.70.145)  0.271 ms  0.309 ms  0.316 ms
 7  ae-8.r22.lsanca07.us.bb.gin.ntt.net (129.250.3.164)  157.394 ms  
157.397 ms  157.458 ms
 8  ae-7.r22.dllstx09.us.bb.gin.ntt.net (129.250.7.68)  184.012 ms  
186.950 ms  183.988 ms
 9  ae-2.r10.dllstx09.us.bb.gin.ntt.net (129.250.4.82)  194.855 ms 
ae-2.r11.dllstx09.us.bb.gin.ntt.net (129.250.5.14)  176.294 ms 178.943 ms
10  ae-0.a02.dllstx09.us.bb.gin.ntt.net (129.250.4.204)  184.306 ms 
ae-1.a00.dllstx04.us.bb.gin.ntt.net (129.250.4.202)  199.942 ms  209.388 ms

11  * * ae-2.amazon.dllstx04.us.bb.gin.ntt.net (129.250.201.150) 196.363 ms
12  * * *
13  * * *
14  * * *
15  54.240.229.189 (54.240.229.189)  277.958 ms * *
16  * * *
17  54.239.109.30 (54.239.109.30)  294.726 ms * *
18  54.239.109.251 (54.239.109.251)  285.324 ms * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  s3-website-us-east-1.amazonaws.com (52.216.161.90)  276.608 ms * *


On 30/01/18 11:47, Giles Pollock wrote:

Sure...
Fun thing is I can't get to the ec2-reachability page because it also 
seems to be affected.
for now, I've chosen console.aws.amazon.com 
 (which is going to us-east-1) and 
docs.aws.amazon.com , as well as 
ec2-reachability.amazonaws.com 


All follow the same path it seems...
tracert ec2-reachability.amazonaws.com 



Tracing route to s3-website-us-east-1.amazonaws.com 
 [54.231.114.201]

over a maximum of 30 hops:

  1    <1 ms    <1 ms     1 ms  
  2     2 ms     1 ms     1 ms  
  3   168 ms   167 ms   167 ms BE-150.cor02.mel07.vic.VOCUS.net.au 
 [114.31.196.54]
  4   163 ms   163 ms   163 ms Hu-0-0-0-1.cor02.syd04.nsw.VOCUS.net.au 
 [114.31.192.114]
  5   163 ms   163 ms   163 ms bundle-200.cor01.sjc01.ca.vocus.net 
 [49.255.255.10]
  6   167 ms   168 ms   168 ms bundle-100.bdr01.sjc01.ca.vocus.net 
 [49.255.255.19]
  7   168 ms   173 ms   168 ms sjo-b21-link.telia.net 
 [62.115.154.12]
  8   169 ms   170 ms   169 ms las-b21-link.telia.net 
 [62.115.116.41]
  9   201 ms   201 ms   205 ms dls-b21-link.telia.net 
 [62.115.123.136]
 10   206 ms   205 ms   205 ms a100us-ic-303629-dls-bb1.c.telia.net 
 [213.248.85.222]

 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *      282 ms   282 ms  54.240.229.175
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18   281 ms     *        *     54.239.111.43
 19     *        *        *     Request timed out.
 20     *      280 ms   281 ms  72.21.220.43
 21     *        *        *     Request timed out.
 22  ^C



On Tue, Jan 30, 2018 at 11:40 AM, Andras Toth > wrote:


Hi Giles,

Do you have a traceroute and/or MTR output that you could include?

Do you see packet loss to IP addresses listed on
http://ec2-reachability.amazonaws.com/
 as well? If so, can you
include traceroutes/MTR for those too please?

Andras


On Tue, Jan 30, 2018 at 11:34 AM, Giles Pollock > wrote:

Hi Everyone,
A frustrating start to the morning with over 50% packet loss
when trying to hit console.aws.amazon.com
. Traffic heading via Vocus is
fine up until it heads into Telia.net, specifically
a-100-ic-300087-kbn-b3.c.telia.net


Can't find any noise in the usual places yet that indicate
theres an issue, so wondering if anyone else is seeing the

Re: [AusNOG] Anyone else seeing massive packet loss to AWS us-east-1 via Telia currently?

2018-01-29 Thread Giles Pollock 
Sure...
Fun thing is I can't get to the ec2-reachability page because it also seems
to be affected.
for now, I've chosen console.aws.amazon.com (which is going to us-east-1)
and docs.aws.amazon.com, as well as ec2-reachability.amazonaws.com

All follow the same path it seems...
tracert ec2-reachability.amazonaws.com

Tracing route to s3-website-us-east-1.amazonaws.com [54.231.114.201]
over a maximum of 30 hops:

  1<1 ms<1 ms 1 ms  
  2 2 ms 1 ms 1 ms  
  3   168 ms   167 ms   167 ms  BE-150.cor02.mel07.vic.VOCUS.net.au
[114.31.196.54]
  4   163 ms   163 ms   163 ms  Hu-0-0-0-1.cor02.syd04.nsw.VOCUS.net.au
[114.31.192.114]
  5   163 ms   163 ms   163 ms  bundle-200.cor01.sjc01.ca.vocus.net
[49.255.255.10]
  6   167 ms   168 ms   168 ms  bundle-100.bdr01.sjc01.ca.vocus.net
[49.255.255.19]
  7   168 ms   173 ms   168 ms  sjo-b21-link.telia.net [62.115.154.12]
  8   169 ms   170 ms   169 ms  las-b21-link.telia.net [62.115.116.41]
  9   201 ms   201 ms   205 ms  dls-b21-link.telia.net [62.115.123.136]
 10   206 ms   205 ms   205 ms  a100us-ic-303629-dls-bb1.c.telia.net
[213.248.85.222]
 11 *** Request timed out.
 12 *** Request timed out.
 13 *** Request timed out.
 14 *** Request timed out.
 15 *  282 ms   282 ms  54.240.229.175
 16 *** Request timed out.
 17 *** Request timed out.
 18   281 ms ** 54.239.111.43
 19 *** Request timed out.
 20 *  280 ms   281 ms  72.21.220.43
 21 *** Request timed out.
 22  ^C



On Tue, Jan 30, 2018 at 11:40 AM, Andras Toth  wrote:

> Hi Giles,
>
> Do you have a traceroute and/or MTR output that you could include?
>
> Do you see packet loss to IP addresses listed on http://ec2-reachability.
> amazonaws.com/ as well? If so, can you include traceroutes/MTR for those
> too please?
>
> Andras
>
>
> On Tue, Jan 30, 2018 at 11:34 AM, Giles Pollock  wrote:
>
>> Hi Everyone,
>> A frustrating start to the morning with over 50% packet loss when trying
>> to hit console.aws.amazon.com. Traffic heading via Vocus is fine up
>> until it heads into Telia.net, specifically
>> a-100-ic-300087-kbn-b3.c.telia.net
>>
>> Can't find any noise in the usual places yet that indicate theres an
>> issue, so wondering if anyone else is seeing the same problem?
>>
>> ___
>> AusNOG mailing list
>> AusNOG@lists.ausnog.net
>> http://lists.ausnog.net/mailman/listinfo/ausnog
>>
>>
>
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Anyone else seeing massive packet loss to AWS us-east-1 via Telia currently?

2018-01-29 Thread Chris 
I am seeing very bad packet loss from one of our Vocus connections to 
Telecity/Equinix London starting from about 40 minutes ago, in the 
region of 40-50% packet loss. Traffic from both London -> AU and AU -> 
London is going via he.net in my case, but the packet loss appears to 
only happen on the London -> AU direction.


I added the community 4826:2709 (no export to he.net) to our routes on 
the Vocus (AU) side which fixed that issue for me.


On 30/01/2018 8:34 AM, Giles Pollock wrote:

Hi Everyone,
A frustrating start to the morning with over 50% packet loss when trying 
to hit console.aws.amazon.com . Traffic 
heading via Vocus is fine up until it heads into Telia.net, specifically 
a-100-ic-300087-kbn-b3.c.telia.net 



Can't find any noise in the usual places yet that indicate theres an 
issue, so wondering if anyone else is seeing the same problem?



___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog


___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Anyone else seeing massive packet loss to AWS us-east-1 via Telia currently?

2018-01-29 Thread Andras Toth 
Hi Giles,

Do you have a traceroute and/or MTR output that you could include?

Do you see packet loss to IP addresses listed on
http://ec2-reachability.amazonaws.com/ as well? If so, can you include
traceroutes/MTR for those too please?

Andras


On Tue, Jan 30, 2018 at 11:34 AM, Giles Pollock  wrote:

> Hi Everyone,
> A frustrating start to the morning with over 50% packet loss when trying
> to hit console.aws.amazon.com. Traffic heading via Vocus is fine up until
> it heads into Telia.net, specifically a-100-ic-300087-kbn-b3.c.telia.net
>
> Can't find any noise in the usual places yet that indicate theres an
> issue, so wondering if anyone else is seeing the same problem?
>
> ___
> AusNOG mailing list
> AusNOG@lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
>
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog