Re: [outages] CrowdStrike BSOD

2024-07-19 Thread Phil Lavin via Outages 
> CrowdStrike just BSODed thousands, if not millions, of Windows machines all 
> over the world

What’s the link, if any, to the Azure outage? I’m guessing $lots of machines 
rebooting at the same time triggered an overload? 
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Twelve99 / AWS usw2 significant loss

2024-01-26 Thread Phil Lavin via Outages 
I see the AWS->me path has just changed to Cogent. me->AWS path still appears 
to be Twelve99. Loss and latency has now subsided.

Thanks


> On 26 Jan 2024, at 08:19, Phil Lavin  wrote:
> 
> Hi Folks,
> 
> Cross posting to outages and nanog.
> 
> Can anybody from Twelve99 / AWS investigate high loss and latency around SJO 
> between Twelve99 and AWS?
> 
> Traces below:
> 
> 88.99.88.67 to 216.147.3.209:
> 
>My traceroute  [v0.94]
> phil (10.88.10.10) -> 216.147.3.209   
> 2024-01-26T08:16:16+
> Keys:  Help   Display mode   Restart statistics   Order of fields   quit
>  Packets   
> Pings
> Host   Loss%   Snt   Last   Avg  
> Best  Wrst StDev
> 1. 10.88.10.254 0.0%   1760.2   0.1   
> 0.1   0.3   0.1
> 2. fe-fw-01.lavin.me.uk 0.0%   1760.4   0.4   
> 0.2   0.7   0.1
> 3. 10.69.69.1   0.0%   1760.5   0.4   
> 0.2   0.7   0.1
> 4. static.225.8.4.46.clients.your-server.de 0.0%   1760.8   1.0   
> 0.5   8.2   1.0
> 5. core22.fsn1.hetzner.com  0.6%   1760.8   2.0   
> 0.7  39.0   4.6
> 6. static.213-239-254-234.clients.your-server.de0.0%   1763.2   3.8   
> 3.1  36.5   3.3
> 7. nug-b1-link.ip.twelve99.net  0.0%   1763.3   3.5   
> 3.1  24.1   1.6
> 8. hbg-bb2-link.ip.twelve99.net86.9%   175   18.9  18.9  
> 18.7  19.2   0.1
> 9. ldn-bb2-link.ip.twelve99.net92.0%   175   30.5  30.6  
> 30.4  30.8   0.1
> 10. nyk-bb1-link.ip.twelve99.net 4.6%   175   99.5  99.5  
> 99.3 100.1   0.2
> 11. sjo-b23-link.ip.twelve99.net56.3%   175  296.8 306.0 
> 289.7 315.0   5.5
> 12. amazon-ic-366608.ip.twelve99-cust.net   80.5%   175  510.0 513.5 
> 500.7 539.7   8.4
> 13. (waiting for reply)
> …...
> 26. 216.147.3.209   59.1%   150  534.2 534.4 
> 513.5 549.7   8.1
> 
> 44.236.47.236 to 178.63.26.145:
> 
> jcasc-rtc01 (10.96.54.240) -> hc-ping.com   
> 2024-01-26T08:10:24+
> Keys:  Help   Display mode   Restart statistics   Order of fields   quit
>Packets   Pings
> Host Loss%   Snt   Last   Avg  
> Best  Wrst StDev
> 1. ip-10-96-50-153.us-west-2.compute.internal 0.0%   2670.2   0.2   
> 0.2   0.4   0.0
> 2. ec2-34-221-151-225.us-west-2.compute.amazonaw  0.0%   2676.8  15.9   
> 0.7 114.1  24.1
> 3. (waiting for reply)
> 4. (waiting for reply)
> 5. (waiting for reply)
> 6. 241.0.2.5  0.0%   2670.4   0.4   
> 0.3   1.2   0.1
> 7. 242.0.42.195   0.0%   2671.2   1.7   
> 0.5  23.9   3.0
> 8. 240.2.144.12   0.0%   2675.2   5.2   
> 5.2  27.4   1.4
> 9. amazon-ic-375418.ip.twelve99-cust.net  0.0%   2675.3   5.2   
> 5.2   6.1   0.1
> 10. port-b4-link.ip.twelve99.net   0.0%   2675.3   5.5   
> 4.9  35.5   3.0
> 11. port-b3-link.ip.twelve99.net   0.0%   2675.8   5.9   
> 5.6  11.8   0.5
> 12. palo-b24-link.ip.twelve99.net  4.9%   267   21.1  21.5  
> 21.0  58.4   3.1
> 13. sjo-b23-link.ip.twelve99.net   0.0%   266   21.4  22.7  
> 21.3  86.2   6.5
> 14. nyk-bb1-link.ip.twelve99.net  58.1%   266  432.7 422.7 
> 407.2 438.5   6.5
> 15. ldn-bb2-link.ip.twelve99.net  98.1%   266  485.6 485.4 
> 481.6 491.1   3.9
> 16. hbg-bb2-link.ip.twelve99.net  92.5%   266  504.1 499.8 
> 489.8 510.1   5.9
> 17. nug-b1-link.ip.twelve99.net   55.5%   266  523.5 519.6 
> 504.4 561.7   7.6
> 18. hetzner-ic-340780.ip.twelve99-cust.net53.6%   266  524.4 519.2 
> 506.0 545.5   6.9
> 19. core22.fsn1.hetzner.com   70.2%   266  521.7 519.2 
> 498.5 531.7   6.6
> 20. static.213-239-254-150.clients.your-server.de 33.2%   266  382.4 375.4 
> 364.9 396.5   4.1
> 21. static.145.26.63.178.clients.your-server.de   62.0%   266  529.9 518.4 
> 506.9 531.3   6.1
> 
> 
> Thanks

___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Twelve99 / AWS usw2 significant loss

2024-01-26 Thread Phil Lavin via Outages 
Thanks, ytti. I have raised a case with AWS but I expect it to be as 
unproductive as usual. In this type of issue, there is often a friendly 
Engineer keeping an eye on NANOG list or IRC channel who can mitigate it. 
Hoping that to be the case this time, also.


> On 26 Jan 2024, at 08:40, Saku Ytti  wrote:
> 
> On Fri, 26 Jan 2024 at 10:23, Phil Lavin via NANOG  wrote:
> 
> 
>> 88.99.88.67 to 216.147.3.209:
>> Host   Loss%   Snt   Last   Avg  
>> Best  Wrst StDev
>> 1. 10.88.10.254 0.0%   1760.2   0.1  
>>  0.1   0.3   0.1
>> 7. nug-b1-link.ip.twelve99.net  0.0%   1763.3   3.5  
>>  3.1  24.1   1.6
>> 8. hbg-bb2-link.ip.twelve99.net86.9%   175   18.9  18.9  
>> 18.7  19.2   0.1
>> 9. ldn-bb2-link.ip.twelve99.net92.0%   175   30.5  30.6  
>> 30.4  30.8   0.1
>> 10. nyk-bb1-link.ip.twelve99.net 4.6%   175   99.5  99.5 
>>  99.3 100.1   0.2
>> 11. sjo-b23-link.ip.twelve99.net56.3%   175  296.8 306.0 
>> 289.7 315.0   5.5
>> 12. amazon-ic-366608.ip.twelve99-cust.net   80.5%   175  510.0 513.5 
>> 500.7 539.7   8.4
> 
> This implies the problem is not on this path, because #10 is not
> experiencing it, possibly because it happens to return a packet via
> another option, but certainly shows the problem didn't happen in this
> direction yet at #10, but because #8 and #9 saw it, they already saw
> it on the other direction.
> 
> 
>> 44.236.47.236 to 178.63.26.145:
>> Host Loss%   Snt   Last   Avg  
>> Best  Wrst StDev
>> 1. ip-10-96-50-153.us-west-2.compute.internal 0.0%   2670.2   0.2   
>> 0.2   0.4   0.0
>> 11. port-b3-link.ip.twelve99.net   0.0%   2675.8   5.9   
>> 5.6  11.8   0.5
>> 12. palo-b24-link.ip.twelve99.net  4.9%   267   21.1  21.5  
>> 21.0  58.4   3.1
>> 13. sjo-b23-link.ip.twelve99.net   0.0%   266   21.4  22.7  
>> 21.3  86.2   6.5
>> 14. nyk-bb1-link.ip.twelve99.net  58.1%   266  432.7 422.7 
>> 407.2 438.5   6.5
>> 15. ldn-bb2-link.ip.twelve99.net  98.1%   266  485.6 485.4 
>> 481.6 491.1   3.9
>> 16. hbg-bb2-link.ip.twelve99.net  92.5%   266  504.1 499.8 
>> 489.8 510.1   5.9
>> 17. nug-b1-link.ip.twelve99.net   55.5%   266  523.5 519.6 
>> 504.4 561.7   7.6
>> 18. hetzner-ic-340780.ip.twelve99-cust.net53.6%   266  524.4 519.2 
>> 506.0 545.5   6.9
>> 19. core22.fsn1.hetzner.com   70.2%   266  521.7 519.2 
>> 498.5 531.7   6.6
>> 20. static.213-239-254-150.clients.your-server.de 33.2%   266  382.4 375.4 
>> 364.9 396.5   4.1
>> 21. static.145.26.63.178.clients.your-server.de   62.0%   266  529.9 518.4 
>> 506.9 531.3   6.1
> 
> This suggests the congestion point is from sjo to nyk, in 1299, not AWS at 
> all.
> 
> You could try to fix SPORT/DPORT, and do several SPORT options, to see
> if loss goes away with some, to determine if all LAG members are full
> or just one.
> 
> 
> At any rate, this seems business as usual, sometimes internet is very
> lossy, you should contact your service provider, which I guess is AWS
> here, so they can contact their service provider or 1299.
> 
> -- 
>  ++ytti

___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

[outages] Twelve99 / AWS usw2 significant loss

2024-01-26 Thread Phil Lavin via Outages 
Hi Folks,

Cross posting to outages and nanog.

Can anybody from Twelve99 / AWS investigate high loss and latency around SJO 
between Twelve99 and AWS?

Traces below:

88.99.88.67 to 216.147.3.209:

My traceroute  [v0.94]
phil (10.88.10.10) -> 216.147.3.209   
2024-01-26T08:16:16+
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
  Packets   
Pings
 Host   Loss%   Snt   Last   Avg  
Best  Wrst StDev
 1. 10.88.10.254 0.0%   1760.2   0.1   
0.1   0.3   0.1
 2. fe-fw-01.lavin.me.uk 0.0%   1760.4   0.4   
0.2   0.7   0.1
 3. 10.69.69.1   0.0%   1760.5   0.4   
0.2   0.7   0.1
 4. static.225.8.4.46.clients.your-server.de 0.0%   1760.8   1.0   
0.5   8.2   1.0
 5. core22.fsn1.hetzner.com  0.6%   1760.8   2.0   
0.7  39.0   4.6
 6. static.213-239-254-234.clients.your-server.de0.0%   1763.2   3.8   
3.1  36.5   3.3
 7. nug-b1-link.ip.twelve99.net  0.0%   1763.3   3.5   
3.1  24.1   1.6
 8. hbg-bb2-link.ip.twelve99.net86.9%   175   18.9  18.9  
18.7  19.2   0.1
 9. ldn-bb2-link.ip.twelve99.net92.0%   175   30.5  30.6  
30.4  30.8   0.1
10. nyk-bb1-link.ip.twelve99.net 4.6%   175   99.5  99.5  
99.3 100.1   0.2
11. sjo-b23-link.ip.twelve99.net56.3%   175  296.8 306.0 
289.7 315.0   5.5
12. amazon-ic-366608.ip.twelve99-cust.net   80.5%   175  510.0 513.5 
500.7 539.7   8.4
13. (waiting for reply)
…...
26. 216.147.3.209   59.1%   150  534.2 534.4 
513.5 549.7   8.1

44.236.47.236 to 178.63.26.145:

jcasc-rtc01 (10.96.54.240) -> hc-ping.com   
2024-01-26T08:10:24+
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
Packets   Pings
 Host Loss%   Snt   Last   Avg  
Best  Wrst StDev
 1. ip-10-96-50-153.us-west-2.compute.internal 0.0%   2670.2   0.2   
0.2   0.4   0.0
 2. ec2-34-221-151-225.us-west-2.compute.amazonaw  0.0%   2676.8  15.9   
0.7 114.1  24.1
 3. (waiting for reply)
 4. (waiting for reply)
 5. (waiting for reply)
 6. 241.0.2.5  0.0%   2670.4   0.4   
0.3   1.2   0.1
 7. 242.0.42.195   0.0%   2671.2   1.7   
0.5  23.9   3.0
 8. 240.2.144.12   0.0%   2675.2   5.2   
5.2  27.4   1.4
 9. amazon-ic-375418.ip.twelve99-cust.net  0.0%   2675.3   5.2   
5.2   6.1   0.1
10. port-b4-link.ip.twelve99.net   0.0%   2675.3   5.5   
4.9  35.5   3.0
11. port-b3-link.ip.twelve99.net   0.0%   2675.8   5.9   
5.6  11.8   0.5
12. palo-b24-link.ip.twelve99.net  4.9%   267   21.1  21.5  
21.0  58.4   3.1
13. sjo-b23-link.ip.twelve99.net   0.0%   266   21.4  22.7  
21.3  86.2   6.5
14. nyk-bb1-link.ip.twelve99.net  58.1%   266  432.7 422.7 
407.2 438.5   6.5
15. ldn-bb2-link.ip.twelve99.net  98.1%   266  485.6 485.4 
481.6 491.1   3.9
16. hbg-bb2-link.ip.twelve99.net  92.5%   266  504.1 499.8 
489.8 510.1   5.9
17. nug-b1-link.ip.twelve99.net   55.5%   266  523.5 519.6 
504.4 561.7   7.6
18. hetzner-ic-340780.ip.twelve99-cust.net53.6%   266  524.4 519.2 
506.0 545.5   6.9
19. core22.fsn1.hetzner.com   70.2%   266  521.7 519.2 
498.5 531.7   6.6
20. static.213-239-254-150.clients.your-server.de 33.2%   266  382.4 375.4 
364.9 396.5   4.1
21. static.145.26.63.178.clients.your-server.de   62.0%   266  529.9 518.4 
506.9 531.3   6.1


Thanks
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] AS37468 (Angola Cables) - Route Leak?

2023-05-25 Thread Phil Lavin via Outages 
Return path is via NTT and looks OK:

My traceroute  [v0.94]
http-lb-01 (88.99.88.69) -> 216.147.4.201 
2023-05-25T12:34:28+
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
  Packets   
Pings
 Host   Loss%   Snt   Last  
 Avg  Best  Wrst StDev
 1. fe-fw-01.lavin.me.uk 0.0%190.2  
 0.1   0.1   0.2   0.0
 2. 10.69.69.1   0.0%180.3  
 0.2   0.2   0.3   0.0
 3. static.225.8.4.46.clients.your-server.de 0.0%180.5  
 0.8   0.4   5.3   1.1
 4. core23.fsn1.hetzner.com  0.0%180.7  
 1.7   0.5   9.7   2.6
 5. core0.fra.hetzner.com0.0%185.2  
 5.1   5.1   5.2   0.0
 6. 213.198.82.129   0.0%188.2  
 5.8   5.5   8.2   0.6
 7. ae-3.r20.frnkge13.de.bb.gin.ntt.net  0.0%185.5  
 8.5   5.2  48.7  10.1
 8. ae-4.r20.vienat02.at.bb.gin.ntt.net  0.0%18   22.0  
18.1  16.6  22.0   1.7
 9. ae-0.r21.vienat02.at.bb.gin.ntt.net  0.0%18   26.8  
21.8  17.1  29.9   3.4
10. ae-10.r23.sngpsi07.sg.bb.gin.ntt.net94.1%18  162.1 
162.1 162.1 162.1   0.0
11. ae-1.r00.sngpsi07.sg.bb.gin.ntt.net  0.0%18  156.9 
157.1 156.9 157.2   0.1
12. ae-0.amazon.sngpsi07.sg.bb.gin.ntt.net   0.0%18  158.7 
159.6 158.3 164.3   2.0
13. (waiting for reply)
14. (waiting for reply)
15. (waiting for reply)
16. (waiting for reply)
17. (waiting for reply)
18. (waiting for reply)
19. (waiting for reply)
20. (waiting for reply)
21. (waiting for reply)
22. (waiting for reply)
23. 216.147.4.201   70.6%18  508.8 
515.5 504.3 523.0   8.4


___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

[outages] AS37468 (Angola Cables) - Route Leak?

2023-05-25 Thread Phil Lavin via Outages 
Hey Folks,

Seeing massive packet loss on routes from AWS to Hetzner today. First was AWS 
USW2 -> Hetzner (e.g. 88.99.88.69).

Traffic was transiting via AS37468 (Angola Cables) in Coresite IX.

Now got loss from AWS apse1/apse2. Traffic transiting via AS37468 on Equinix IX.

I e-mailed Hetzner NOC but they don’t seem entirely bothered, currently.

   My traceroute  [v0.94]
jcasc-rtc01 (10.36.21.252) -> phil.lavin.me.uk  2023-05-25T11:50:13+
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
Packets   Pings
 Host Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. ip-10-36-17-199.ap-southeast-  0.0%180.1   0.6   0.1   7.7   1.8
 2. ec2-18-141-171-15.ap-southeas  0.0%184.3  17.5   0.9  95.7  24.0
ec2-18-141-171-1.ap-southeast-1.compute.amazonaws.com
 3. (waiting for reply)
 4. (waiting for reply)
 5. (waiting for reply)
 6. (waiting for reply)
 7. (waiting for reply)
 8. 100.65.10.161  0.0%170.6   1.4   0.3   9.6   2.4
100.65.11.65
 9. 150.222.108.75 0.0%172.1   3.0   1.0  13.1   3.3
52.93.10.74
10. 150.222.108.82 0.0%172.2   2.4   1.3  10.2   2.1
11. 52.93.11.115   0.0%175.8   2.4   1.2   9.7   2.5
52.93.10.185
12. 37468-sg1-ix.equinix.com  68.8%17  268.6 279.0 262.4 312.8  19.8
13. 102.219.127.3 93.8%17  420.0 420.0 420.0 420.0   0.0
14. (waiting for reply)
15. 195.66.227.20962.5%17  467.9 456.9 440.3 488.2  18.5
16. core6.par.hetzner.com 75.0%17  455.6 464.1 455.6 486.3  14.8
17. core11.nbg1.hetzner.com   75.0%17  459.5 467.5 445.9 497.3  21.8
18. core23.fsn1.hetzner.com   68.8%17  478.4 441.0 390.0 478.4  32.0
19. ex9k1.dc1.fsn1.hetzner.com87.5%17  460.4 454.2 448.1 460.4   8.7
20. vmh02.lavin.me.uk 75.0%17  433.3 424.2 382.7 441.9  27.9
21. (waiting for reply)
22. http-lb-01.lavin.me.uk75.0%17  436.8 438.6 385.0 493.3  44.2

I’ve been out of the BGP game for a few years now. Anybody have visibility of 
the extent of the leaks?


Phil___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] anyone from charter ?

2022-06-23 Thread Phil Lavin via Outages 
That was raised by me, if I recall, in job—. It was related to an ACL change 
they did which caused fragmented UDP packets (the fragment not containing UDP 
headers) to get dropped.

Does the issue sound similar?


-- 
Phil Lavin | Engineering Director, Voice APIs
T: +44 2033 710587
phil.la...@vonage.com
15 Bonhill Street  •  London, EC2A 4DN • UK


 
Communications
 APIs  |  Unified Communications  |  Contact Centers 

NOTE: The information contained in this email message is considered 
confidential and proprietary to the sender and is intended solely 
for review and use by the named recipient.  Any unauthorized review, use or 
distribution is strictly prohibited. If you have received this 
message in error, please advise the sender by reply email and delete the 
message.

> On 23 Jun 2022, at 22:44, Josh Luthman via Outages  
> wrote:
> 
> Wasn't there a post here or NANOG about voip being manipulated or dropped by 
> Spectrum?  I may have seen it on Reddit.
> 
> On Thu, Jun 23, 2022, 5:39 PM Izzy Goldstein - TeleGo via Outages 
> mailto:outages@outages.org>> wrote:
> Anyone from charter that can reach out to me? off list is ok 
> 
> i am facing an issue with VoIP/SIP
> 
> pockets from my datacenter to a specific IP are not making it to the 
> destination, 
> 1 HOP before the Default gateway sends the packets to another destination 
> perhaps ?
> 
> -- 
> Izzy Goldstein
> Chief Technology Officer - DevOps Master
> Main: (212) 477-1000 x 2085  
> Direct: (929) 477-2085 
> Website: www.telego.com  
> 
> 
> 
> Confidentiality Notice: This e-mail may contain confidential and/or 
> privileged information. If you are not the intended recipient or have 
> received this e-mail in error please notify us immediately by email reply and 
> destroy this e-mail. Any unauthorized copying, disclosure or distribution of 
> the material in this e-mail is strictly forbidden. Any views or opinions 
> presented in this email are solely those of the author and do not necessarily 
> represent those of TeleGo (T). Employees of TeleGo are expressly required not 
> to make defamatory statements and not to infringe or authorize any 
> infringement of copyright or any other legal right by email communications. 
> Any such communication is contrary to TeleGo policy and outside the scope of 
> the employment of the individual concerned. TeleGo will not accept any 
> liability in respect of such communication, and the employee responsible will 
> be personally liable for any damages or other liability arising.
> 
> TeleGo Hosted PBX 
> ___
> Outages mailing list
> Outages@outages.org 
> https://puck.nether.net/mailman/listinfo/outages 
> 
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages

___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] More AWS Trouble 12/15?

2021-12-15 Thread Phil Lavin via Outages 
> Did anyone else see some AWS-hosted services go wonky

Yeh. AWS have confirmed "Internet Connectivity” issues. It looks to have 
stabilised somewhat but still seeing some unusual errors


Phil

___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Major Fiber cut Baltimore area

2019-06-18 Thread Phil Lavin via Outages 
> Major fiber outage in Baltimore area, level3 confirmed field techs on site 
> investigating.

Approximately what time did it happen? We saw high RTT and some packet loss on 
an AWS link from Boston to Virginia starting at approx. 15:17 UTC. RTT is still 
fractionally higher (~3ms) than normal, suggesting it's being routed around.
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] CenturyLink Outages this morning

2018-12-28 Thread Phil Lavin via Outages 
> Facebook is blowing up with 911 outages and claiming it's CenturyLink to blame

For what it's worth, here is a list of PSAPs which were reported as having 
problems, presumably due to the CenturyLink outages. Can't be sure if it's 
complete or not:

Malden Police Department, MA
Seekonk Police Department, MA
Sharon Police Department, MA
Amesbury Police Department, MA
Georgetown Police Department, MA
Freetown Police Department, MA
Nantucket Police Department, MA
North Attleboro Police Department, MA
Cambridge Communications, MA
McKinney Police Department, TX – 2106 MT
Cleburne Police Department, TX – 2113 MT
Blaine County Sheriff, MT
Colstrip Police Department, MT
Liberty County 9-1-1, MT
Phillips County Sheriff’s Office, MT
Powder River County Sheriff, MT
Troy Area Dispatch, MT
Valley County Sheriff’s Department, MT
Montgomery County Sheriff’s Office, IA
Des Moines Police Department, IA
Clearlake Police Department, IA
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

[outages] AWS eu-west-1b issues?

2018-09-26 Thread Phil Lavin via Outages 
We lost connectivity to eu-west-1b over direct connect circuits around 20 mins 
ago. Is anybody else seeing issues?
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] AWS East

2018-08-07 Thread Phil Lavin via Outages 
> At 12:38 EDT we experienced severe routing issues within AWS East. Can anyone 
> else confirm?

US East (Virginia)? If so, nothing seen here
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Comcast outage in the midwest?

2018-06-29 Thread Phil Lavin via Outages 
BGP session to Comcast has dropped for us on the East Coast. We were unaffected 
until that happened. I suspect other East Coast providers have seen similar, 
which is the cause of the routing change.

From: Outages  On Behalf Of Dovid Bender via 
Outages
Sent: 29 June 2018 19:16
To: Rob Repp 
Cc: outages@outages.org
Subject: Re: [outages] Comcast outage in the midwest?

We are seeing a routing change. We are in NY and both NTT and HE were sending 
the traffic to their NY routers. The traffic is now going:
HE is sending the traffic to ATL and peering with Comcast there. From there 
Comcast is sending it to Chicago.
NTT is sending it on their own network to Chicago and handing it off to Comcast 
there.



On Fri, Jun 29, 2018 at 2:10 PM, Rob Repp via Outages 
mailto:outages@outages.org>> wrote:
We are getting indications of recovery in the Chicago area.
R.
Sent from my iPhone, sorry for any typos, grammar errors, cryptic 
abbreviations, etc.

On Jun 29, 2018, at 1:04 PM, Terry Hardie via Outages 
mailto:outages@outages.org>> wrote:
We're back up in CA as of about 90 seconds ago.

On Fri, Jun 29, 2018 at 10:55 AM, Zach Bare via Outages 
mailto:outages@outages.org>> wrote:
Areas throughout central Pennsylvania are reporting some sites loading, and 
others not. Seems to be a routing issue as others have already suggested.

[photo]


Zach Bare
Network Engineer at KINBER

[https://s3.amazonaws.com/images.wisestamp.com/social_icons/square/facebook.png]

[https://s3.amazonaws.com/images.wisestamp.com/social_icons/square/twitter.png]

[https://s3.amazonaws.com/images.wisestamp.com/social_icons/square/linkedin.png]



Address 5775 Allentown Blvd., Suite 101, Harrisburg, PA 17112
Phone  717-963-7490 | PennREN NOC 833-736-6736 (833-PENNREN)  

 Mobile  717-469-5461 

 Email  zb...@kinber.org 





On Fri, Jun 29, 2018 at 1:45 PM, Howard Leadmon via Outages 
mailto:outages@outages.org>> wrote:
 Our Roseville MN location is down hard, well from here in MD.  Also my fiber 
EDI to Comcast here in MD is running horrible, with spotty connectivity at 
best.   So we are feeling the effects in various locations.   Like others I 
tried calling Comcast, they call center is also down..


---
Howard Leadmon - how...@leadmon.net
PBW Communications, LLC
http://www.pbwcomm.com



___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages


___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Comcast data issues

2018-06-07 Thread Phil Lavin via Outages 
We saw a BGP session to them in Boston MA flap


> On 7 Jun 2018, at 20:03, Chuck Anderson via Outages  
> wrote:
> 
> Has anyone noticed any Comcast data issues?  I could't ping 8.8.8.8 a few 
> minutes ago although that came back.  Also issues with Google Docs.  My IPv6 
> connectivity was also down.  Things are slowly recovering.  Perhaps there was 
> another core link flap in NYC.
> ___
> Outages mailing list
> Outages@outages.org
> https://puck.nether.net/mailman/listinfo/outages
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

2018-04-24 Thread Phil Lavin via Outages 
Those prefixes had been withdrawn now – traffic is flowing correctly again for 
us. If that was the cause, I suspect things are back to rights for everyone now?
One wonders why HE doesn’t apply filters on a peer with 20 legit prefixes…

From: Outages <outages-boun...@outages.org> On Behalf Of Joseph B via Outages
Sent: 24 April 2018 13:56
To: outages@outages.org
Subject: Re: [outages] Google 8.8.8.8 Resolution of Route53 domains


Tue Apr 24 11:05:41 UTC onwards one of Hurricane Electric's peers AS10297 
started advertising the following subnets via HE.

205.251.192.0
205.251.193.0
205.251.195.0
205.251.197.0
205.251.199.0

These are all Amazon subnets, usually originated as part of /23s and seemingly 
host a fair bit of AWS Route53.

If you (or your DNS resolver) are a HE transit customer you will be impacted 
the most.

Cheers,

Joseph


On Tue, Apr 24, 2018, at 9:50 PM, Phil Lavin via Outages wrote:

This doesn’t feel right, though I’ll admit I’ve never checked before. Our only 
route to ns-163.awsdns-20.com (205.251.192.163) is through HE:

inet.0: 757581 destinations, 2107440 routes (757301 active, 0 holddown, 522 
hidden)

+ = Active Route, - = Last Active, * = Both

205.251.192.0/24   *[BGP/170] 01:12:08, localpref 70

  AS path: 6939 10297 I, validation-state: unverified

> to 216.66.90.21 via ge-1/0/5.0

AS10297 is eNET inc. Is this expected?



From: Outages <outages-boun...@outages.org<mailto:outages-boun...@outages.org>> 
On Behalf Of Phil Lavin via Outages
Sent: 24 April 2018 13:04
To: outages@outages.org<mailto:outages@outages.org>
Subject: Re: [outages] Google 8.8.8.8 Resolution of Route53 domains



Looks more specific to AWS than it does to Google+AWS. Can’t resolve against 
some of AWS’s NS directly:

phil@phil-debian:~$ dig cloudcall.com IN A @ns-163.awsdns-20.com

; <<>> DiG 9.10.3-P4-Debian <<>> cloudcall.com IN A @ns-163.awsdns-20.com

;; global options: +cmd

;; connection timed out; no servers could be reached



From: Outages <outages-boun...@outages.org<mailto:outages-boun...@outages.org>> 
On Behalf Of Phil Lavin via Outages
Sent: 24 April 2018 12:56
To: outages@outages.org<mailto:outages@outages.org>
Subject: Re: [outages] Google 8.8.8.8 Resolution of Route53 domains



Yeh. Still digging into it.



From: Outages <outages-boun...@outages.org<mailto:outages-boun...@outages.org>> 
On Behalf Of Zach Hanna via Outages
Sent: 24 April 2018 12:54
To: outages@outages.org<mailto:outages@outages.org>
Subject: [outages] Google 8.8.8.8 Resolution of Route53 domains



Anyone else seeing SERVFAIL for route53-hosted domains trying to resolve with 
Google DNS?
___
Outages mailing list
Outages@outages.org<mailto:Outages@outages.org>
https://puck.nether.net/mailman/listinfo/outages

___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

2018-04-24 Thread Phil Lavin via Outages 
Thanks for confirming. I’ve raised a ticket with HE on our circuit. I presume 
nobody has a contact at 10297?

From: Outages <outages-boun...@outages.org> On Behalf Of Joseph B via Outages
Sent: 24 April 2018 13:56
To: outages@outages.org
Subject: Re: [outages] Google 8.8.8.8 Resolution of Route53 domains


Tue Apr 24 11:05:41 UTC onwards one of Hurricane Electric's peers AS10297 
started advertising the following subnets via HE.

205.251.192.0
205.251.193.0
205.251.195.0
205.251.197.0
205.251.199.0

These are all Amazon subnets, usually originated as part of /23s and seemingly 
host a fair bit of AWS Route53.

If you (or your DNS resolver) are a HE transit customer you will be impacted 
the most.

Cheers,

Joseph


On Tue, Apr 24, 2018, at 9:50 PM, Phil Lavin via Outages wrote:

This doesn’t feel right, though I’ll admit I’ve never checked before. Our only 
route to ns-163.awsdns-20.com (205.251.192.163) is through HE:

inet.0: 757581 destinations, 2107440 routes (757301 active, 0 holddown, 522 
hidden)

+ = Active Route, - = Last Active, * = Both

205.251.192.0/24   *[BGP/170] 01:12:08, localpref 70

  AS path: 6939 10297 I, validation-state: unverified

> to 216.66.90.21 via ge-1/0/5.0

AS10297 is eNET inc. Is this expected?



From: Outages <outages-boun...@outages.org<mailto:outages-boun...@outages.org>> 
On Behalf Of Phil Lavin via Outages
Sent: 24 April 2018 13:04
To: outages@outages.org<mailto:outages@outages.org>
Subject: Re: [outages] Google 8.8.8.8 Resolution of Route53 domains



Looks more specific to AWS than it does to Google+AWS. Can’t resolve against 
some of AWS’s NS directly:

phil@phil-debian:~$ dig cloudcall.com IN A @ns-163.awsdns-20.com

; <<>> DiG 9.10.3-P4-Debian <<>> cloudcall.com IN A @ns-163.awsdns-20.com

;; global options: +cmd

;; connection timed out; no servers could be reached



From: Outages <outages-boun...@outages.org<mailto:outages-boun...@outages.org>> 
On Behalf Of Phil Lavin via Outages
Sent: 24 April 2018 12:56
To: outages@outages.org<mailto:outages@outages.org>
Subject: Re: [outages] Google 8.8.8.8 Resolution of Route53 domains



Yeh. Still digging into it.



From: Outages <outages-boun...@outages.org<mailto:outages-boun...@outages.org>> 
On Behalf Of Zach Hanna via Outages
Sent: 24 April 2018 12:54
To: outages@outages.org<mailto:outages@outages.org>
Subject: [outages] Google 8.8.8.8 Resolution of Route53 domains



Anyone else seeing SERVFAIL for route53-hosted domains trying to resolve with 
Google DNS?
___
Outages mailing list
Outages@outages.org<mailto:Outages@outages.org>
https://puck.nether.net/mailman/listinfo/outages

___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

2018-04-24 Thread Phil Lavin via Outages 
In fact, 3 of 4 nameservers on our main domain are advertised as different /24s 
by AS 10297. None of these can be queried. The other is advertised by AS 16509 
(AWS) – this works.

From: Outages <outages-boun...@outages.org> On Behalf Of Phil Lavin via Outages
Sent: 24 April 2018 13:20
To: outages@outages.org
Subject: Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

This doesn’t feel right, though I’ll admit I’ve never checked before. Our only 
route to ns-163.awsdns-20.com (205.251.192.163) is through HE:
inet.0: 757581 destinations, 2107440 routes (757301 active, 0 holddown, 522 
hidden)
+ = Active Route, - = Last Active, * = Both
205.251.192.0/24   *[BGP/170] 01:12:08, localpref 70
  AS path: 6939 10297 I, validation-state: unverified
> to 216.66.90.21 via ge-1/0/5.0
AS10297 is eNET inc. Is this expected?

From: Outages <outages-boun...@outages.org<mailto:outages-boun...@outages.org>> 
On Behalf Of Phil Lavin via Outages
Sent: 24 April 2018 13:04
To: outages@outages.org<mailto:outages@outages.org>
Subject: Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

Looks more specific to AWS than it does to Google+AWS. Can’t resolve against 
some of AWS’s NS directly:
phil@phil-debian:~$ dig cloudcall.com IN A @ns-163.awsdns-20.com
; <<>> DiG 9.10.3-P4-Debian <<>> cloudcall.com IN A @ns-163.awsdns-20.com
;; global options: +cmd
;; connection timed out; no servers could be reached

From: Outages <outages-boun...@outages.org<mailto:outages-boun...@outages.org>> 
On Behalf Of Phil Lavin via Outages
Sent: 24 April 2018 12:56
To: outages@outages.org<mailto:outages@outages.org>
Subject: Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

Yeh. Still digging into it.

From: Outages <outages-boun...@outages.org<mailto:outages-boun...@outages.org>> 
On Behalf Of Zach Hanna via Outages
Sent: 24 April 2018 12:54
To: outages@outages.org<mailto:outages@outages.org>
Subject: [outages] Google 8.8.8.8 Resolution of Route53 domains

Anyone else seeing SERVFAIL for route53-hosted domains trying to resolve with 
Google DNS?
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

2018-04-24 Thread Phil Lavin via Outages 
Looks more specific to AWS than it does to Google+AWS. Can’t resolve against 
some of AWS’s NS directly:
phil@phil-debian:~$ dig cloudcall.com IN A @ns-163.awsdns-20.com
; <<>> DiG 9.10.3-P4-Debian <<>> cloudcall.com IN A @ns-163.awsdns-20.com
;; global options: +cmd
;; connection timed out; no servers could be reached

From: Outages <outages-boun...@outages.org> On Behalf Of Phil Lavin via Outages
Sent: 24 April 2018 12:56
To: outages@outages.org
Subject: Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

Yeh. Still digging into it.

From: Outages <outages-boun...@outages.org<mailto:outages-boun...@outages.org>> 
On Behalf Of Zach Hanna via Outages
Sent: 24 April 2018 12:54
To: outages@outages.org<mailto:outages@outages.org>
Subject: [outages] Google 8.8.8.8 Resolution of Route53 domains

Anyone else seeing SERVFAIL for route53-hosted domains trying to resolve with 
Google DNS?
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Google 8.8.8.8 Resolution of Route53 domains

2018-04-24 Thread Phil Lavin via Outages 
Yeh. Still digging into it.

From: Outages  On Behalf Of Zach Hanna via Outages
Sent: 24 April 2018 12:54
To: outages@outages.org
Subject: [outages] Google 8.8.8.8 Resolution of Route53 domains

Anyone else seeing SERVFAIL for route53-hosted domains trying to resolve with 
Google DNS?
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

[outages] Telehouse Vodafone Circuit

2018-02-23 Thread Phil Lavin via Outages 
Just had a BGP session pop on a Vodafone transit circuit in Telehouse North. 
Session came back but routes are coming through at a rate of about 100 per 
minute. Get dead air when calling the CSC Helpdesk.

Anyone else seeing issues?
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Slack outage

2018-01-09 Thread Phil Lavin via Outages 
I think it’s clear by now that it’s having an outage. Not sure we need any more 
“me too” responses.

From: Outages [mailto:outages-boun...@outages.org] On Behalf Of Ivan Kovacevic 
via Outages
Sent: 09 January 2018 19:22
To: Josh Luthman 
Cc: outages@outages.org
Subject: Re: [outages] Slack outage


Ditto – Naples, FL.


Best Regards,

Ivan Kovacevic
Vice President, Client Services
Star Telecom | 
www.startelecom.ca
 | SIP Based Services for Contact Centers | 
LinkedIn

From: Outages 
[mailto:outages-boun...@outages.org] On 
Behalf Of Josh Luthman via Outages
Sent: January 9, 2018 2:19 PM
To: outages@outages.org
Subject: [outages] Slack outage

The community says "Server Error" and links the status page, which doesn't 
report anything at this time.

https://status.slack.com

Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Bandwidth Voice Issues?

2017-12-04 Thread Phil Lavin via Outages 
Which POPs are you connected into? Not seeing any issues to New York or Atlanta 
POPs.

___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Vodafone Outage?

2017-11-01 Thread Phil Lavin via Outages 
Transit and VoIP OK here from London Docklands


From: Outages [mailto:outages-boun...@outages.org] On Behalf Of support via 
Outages
Sent: 01 November 2017 17:04
To: outages@outages.org
Subject: [outages] Vodafone Outage?

Is anyone experiencing issues with Vodafone? We have multiple services down in 
the London area

___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] NTT Down - London Docklands

2017-10-31 Thread Phil Lavin via Outages 
Just lost light again. I suspect the issues are ongoing…


From: Edward Dore [mailto:edward.d...@freethought-internet.co.uk]
Sent: 31 October 2017 10:54
To: Phil Lavin <phil.la...@cloudcall.com>; outages@outages.org
Subject: Re: [outages] NTT Down - London Docklands

I read their announcement as it being power to the specific device that we’re 
connected to rather than a more general issue.

Others with 10G services in THN seem to be unaffected, so presumably it was an 
issue with power to a single device or maybe a handful of particular devices.

Edward Dore
Freethought Internet

From: Phil Lavin <phil.la...@cloudcall.com<mailto:phil.la...@cloudcall.com>>
Date: Tuesday, 31 October 2017 at 10:51
To: Edward Dore 
<edward.d...@freethought-internet.co.uk<mailto:edward.d...@freethought-internet.co.uk>>,
 "outages@outages.org<mailto:outages@outages.org>" 
<outages@outages.org<mailto:outages@outages.org>>
Subject: RE: [outages] NTT Down - London Docklands

Likewise. NTT are claiming power outage. I presume this is isolated to them, 
rather than more widely in THN as happened some time ago?


From: Edward Dore [mailto:edward.d...@freethought-internet.co.uk]
Sent: 31 October 2017 10:48
To: Phil Lavin <phil.la...@cloudcall.com<mailto:phil.la...@cloudcall.com>>; 
outages@outages.org<mailto:outages@outages.org>
Subject: Re: [outages] NTT Down - London Docklands

Our ports have just come back up again.

Edward Dore
Freethought Internet

From: Phil Lavin <phil.la...@cloudcall.com<mailto:phil.la...@cloudcall.com>>
Date: Tuesday, 31 October 2017 at 09:58
To: Edward Dore 
<edward.d...@freethought-internet.co.uk<mailto:edward.d...@freethought-internet.co.uk>>,
 "outages@outages.org<mailto:outages@outages.org>" 
<outages@outages.org<mailto:outages@outages.org>>
Subject: RE: [outages] NTT Down - London Docklands

Thanks for confirming. Seems NTT have acknowledged the issue and are working on 
it.

Best

From: Edward Dore [mailto:edward.d...@freethought-internet.co.uk]
Sent: 31 October 2017 09:47
To: Phil Lavin <phil.la...@cloudcall.com<mailto:phil.la...@cloudcall.com>>; 
outages@outages.org<mailto:outages@outages.org>
Subject: Re: [outages] NTT Down - London Docklands

Yup, just seen our IP transit ports in THN go physically down.

Last time this happened, ISTR it was a problem with the fibre feeding the ASR 
9000 nV satellite exetender things that they use for aggregating 1G services.

Edward Dore
Freethought Internet

From: Outages <outages-boun...@outages.org<mailto:outages-boun...@outages.org>> 
on behalf of Phil Lavin via Outages 
<outages@outages.org<mailto:outages@outages.org>>
Reply-To: Phil Lavin <phil.la...@cloudcall.com<mailto:phil.la...@cloudcall.com>>
Date: Tuesday, 31 October 2017 at 09:40
To: "outages@outages.org<mailto:outages@outages.org>" 
<outages@outages.org<mailto:outages@outages.org>>
Subject: [outages] NTT Down - London Docklands

We’ve just lost light from NTT on circuits in London Docklands. Anyone else 
seen issues?


Cheers

Phil
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] NTT Down - London Docklands

2017-10-31 Thread Phil Lavin via Outages 
Likewise. NTT are claiming power outage. I presume this is isolated to them, 
rather than more widely in THN as happened some time ago?


From: Edward Dore [mailto:edward.d...@freethought-internet.co.uk]
Sent: 31 October 2017 10:48
To: Phil Lavin <phil.la...@cloudcall.com>; outages@outages.org
Subject: Re: [outages] NTT Down - London Docklands

Our ports have just come back up again.

Edward Dore
Freethought Internet

From: Phil Lavin <phil.la...@cloudcall.com<mailto:phil.la...@cloudcall.com>>
Date: Tuesday, 31 October 2017 at 09:58
To: Edward Dore 
<edward.d...@freethought-internet.co.uk<mailto:edward.d...@freethought-internet.co.uk>>,
 "outages@outages.org<mailto:outages@outages.org>" 
<outages@outages.org<mailto:outages@outages.org>>
Subject: RE: [outages] NTT Down - London Docklands

Thanks for confirming. Seems NTT have acknowledged the issue and are working on 
it.

Best

From: Edward Dore [mailto:edward.d...@freethought-internet.co.uk]
Sent: 31 October 2017 09:47
To: Phil Lavin <phil.la...@cloudcall.com<mailto:phil.la...@cloudcall.com>>; 
outages@outages.org<mailto:outages@outages.org>
Subject: Re: [outages] NTT Down - London Docklands

Yup, just seen our IP transit ports in THN go physically down.

Last time this happened, ISTR it was a problem with the fibre feeding the ASR 
9000 nV satellite exetender things that they use for aggregating 1G services.

Edward Dore
Freethought Internet

From: Outages <outages-boun...@outages.org<mailto:outages-boun...@outages.org>> 
on behalf of Phil Lavin via Outages 
<outages@outages.org<mailto:outages@outages.org>>
Reply-To: Phil Lavin <phil.la...@cloudcall.com<mailto:phil.la...@cloudcall.com>>
Date: Tuesday, 31 October 2017 at 09:40
To: "outages@outages.org<mailto:outages@outages.org>" 
<outages@outages.org<mailto:outages@outages.org>>
Subject: [outages] NTT Down - London Docklands

We’ve just lost light from NTT on circuits in London Docklands. Anyone else 
seen issues?


Cheers

Phil
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

[outages] NTT Down - London Docklands

2017-10-31 Thread Phil Lavin via Outages 
We've just lost light from NTT on circuits in London Docklands. Anyone else 
seen issues?


Cheers

Phil
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

[outages] Godaddy

2017-07-24 Thread Phil Lavin via Outages 
Hello all,

Sorry for off topic. Does anyone have a tech contact at Godaddy? Getting 
nowhere with 1st line support.


Phil
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] XO SIP call quality poor in Chicago

2017-06-01 Thread Phil Lavin via Outages 
SIP calls over XO seem OK out of Boston.


Phil
From: Outages [mailto:outages-boun...@outages.org] On Behalf Of Judah Sameth 
via Outages
Sent: 01 June 2017 15:59
To: outages@outages.org
Subject: [outages] XO SIP call quality poor in Chicago

Having issues starting at 8:31AM CST with call quality on XO SIP.

Inbound calls goes from the number is not available message, to calls 
completing but very choppy voice quality.

Outbound calls seems to work but voice quality is poor.

Opened a ticket with XO no call back or engineer picked up the ticket.

Anyone else having issues with XO SIP?


Judah Sameth | Director of Information Technology
judah.sam...@xsportfitness.com
p:  630.318.3470



___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Level3 voice outage?

2017-05-16 Thread Phil Lavin via Outages 
Looks OK here. Is this SIP? Which destinations are failing what response code 
are you getting on the failed calls?


-Original Message-
From: Outages [mailto:outages-boun...@outages.org] On Behalf Of Julian Y Koh 
via Outages
Sent: 16 May 2017 16:47
To: outages@outages.org
Subject: [outages] Level3 voice outage?

Anyone seeing issues with Level3’s voice network?  We use them for long 
distance/international calling, and long distance at least is failing for us 
starting around 9:45am Central Time today.

--
Julian Y. Koh
Associate Director, Telecommunications and Network Services Northwestern 
Information Technology

2001 Sheridan Road #G-166
Evanston, IL 60208
+1-847-467-5780
Northwestern IT Web Site:  PGP Public Key: 


___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

Re: [outages] Amazon S3 down

2017-02-28 Thread Phil Lavin via Outages 
Also seeing issues with EC2 Auto Scaling Groups and Lambda functions. Getting 
fun errors like "Status Reason: Insufficient capacity. Launching EC2 instance 
failed".


From: Outages [mailto:outages-boun...@outages.org] On Behalf Of Peter 
Kristolaitis via Outages
Sent: 28 February 2017 18:23
To: outages@outages.org
Subject: Re: [outages] Amazon S3 down


Also confirmed.  I'm unable to load the S3 management console for at least one 
of my accounts.   I just get:

{

  "errorCode" : "InternalError"

}
Amazon has updated their status page to read "We've identified the issue as 
high error rates with S3 in US-EAST-1, which is also impacting applications and 
services dependent on S3. We are actively working on remediating the issue."

On 2/28/2017 1:07 PM, Byron Ellis via Outages wrote:
Confirmed. We are experiencing a complete S3 outage and have confirmed with 
several other companies as well that their buckets are also unavailable. At 
last check S3 status pages were showing green on AWS, but it isn't even 
available through the AWS console.

On Tue, Feb 28, 2017 at 9:55 AM, Carlos Alvarez via Outages 
> wrote:
We are unable to reach it from Cox cable, Highwinds, or Cogent from the Phoenix 
area.  Also several of the outage testing sites say it's down.


--
Carlos Alvarez
602-368-6403


___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages



--
Byron Ellis (byron.el...@gmail.com)
"Oook" -- The Librarian




___

Outages mailing list

Outages@outages.org

https://puck.nether.net/mailman/listinfo/outages

___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

[outages] Level 3 Packet Loss - Boston Area

2017-01-27 Thread Phil Lavin via Outages 
Is anybody else experiencing issues in this area? Seeing loss between us and a 
couple of customers. MTR on both sides shows loss around Boston inside Level3.


Phil
___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

[outages] Bandwidth - Packet Loss

2016-10-24 Thread Phil Lavin via Outages 
Hi all,

Between 15:07 and 15:58 UTC we observed high packet loss on all inbound calls 
from the Bandwidth SBC at 67.231.13.113. We did not see loss from other 
carriers/customers, nor from other Bandwidth SBCs.

Did anybody else see packet loss? Bandwidth say they are not aware of any 
problems, during that time period.


Thanks

Phil Lavin

___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages

[outages] Telehouse North - Major Problems

2016-07-21 Thread Phil Lavin via Outages 
We've just had 3 links drop simultaneously to (different) equipment in 
Telehouse North.

Fibre link to Vodafone - port is down
BGP peering to GTT is dropped
Copper link to BT - port is down

Anyone else seeing anything? We spoke to BT and they have confirmed a "major 
national problem".


Phil Lavin
Telecoms Systems Manager
CloudCall
www.cloudcall.com

___
Outages mailing list
Outages@outages.org
https://puck.nether.net/mailman/listinfo/outages