HE issue this afternoon
During this afternoon's HE hiccup (https://puck.nether.net/pipermail/outages/2016-April/008962.html) there was a flood of outbound traffic on the Main Switch's ge-1/0/10, 12, 16, 22, and 23. Here's an example: [cid:image001.png@01D19FD0.2A25A860] Anyone know what that's about? Frank
According to our ticket, HE had a router failure at around that time. s *Shaun Carlson*Director of Information Technology | Arvig ph: (218) 346-8673 | em: shaun.carlson@arvig.com On Tue, Apr 26, 2016 at 4:30 PM, Frank Bulk <fbulk@mypremieronline.com> wrote:
During this afternoon’s HE hiccup ( https://puck.nether.net/pipermail/outages/2016-April/008962.html) there was a flood of outbound traffic on the Main Switch’s ge-1/0/10, 12, 16, 22, and 23. Here’s an example:
Anyone know what that’s about?
Frank
------------------------------
To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
And, of course, if I actually read your original email, I would know that you already mentioned the "hiccup" and wouldn't repeat the fact. During the event, were others trying to route through the cluster to get to HE? s *Shaun Carlson*Director of Information Technology | Arvig ph: (218) 346-8673 | em: shaun.carlson@arvig.com On Tue, Apr 26, 2016 at 4:35 PM, Shaun Carlson <shaun.carlson@arvig.com> wrote:
According to our ticket, HE had a router failure at around that time.
s
*Shaun Carlson*Director of Information Technology | Arvig ph: (218) 346-8673 | em: shaun.carlson@arvig.com
On Tue, Apr 26, 2016 at 4:30 PM, Frank Bulk <fbulk@mypremieronline.com> wrote:
During this afternoon’s HE hiccup ( https://puck.nether.net/pipermail/outages/2016-April/008962.html) there was a flood of outbound traffic on the Main Switch’s ge-1/0/10, 12, 16, 22, and 23. Here’s an example:
Anyone know what that’s about?
Frank
------------------------------
To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
Given the rate, it looks like a 10Mbit/sec storm-control policer. Dale Thus spake Frank Bulk (fbulk@MYPREMIERONLINE.COM) on Tue, Apr 26, 2016 at 08:30:07PM +0000:
During this afternoon's HE hiccup (https://puck.nether.net/pipermail/outages/2016-April/008962.html) there was a flood of outbound traffic on the Main Switch's ge-1/0/10, 12, 16, 22, and 23. Here's an example:
[cid:image001.png@01D19FD0.2A25A860]
Anyone know what that's about?
Frank
Dale -- good point. But why did it kick in? Why would an issue with a peer cause/result in a flood of outbound traffic on other ports? Frank -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Dale W. Carder Sent: Tuesday, April 26, 2016 3:40 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] HE issue this afternoon Given the rate, it looks like a 10Mbit/sec storm-control policer. Dale Thus spake Frank Bulk (fbulk@MYPREMIERONLINE.COM) on Tue, Apr 26, 2016 at 08:30:07PM +0000:
During this afternoon's HE hiccup (https://puck.nether.net/pipermail/outages/2016-April/008962.html) there was a flood of outbound traffic on the Main Switch's ge-1/0/10, 12, 16, 22, and 23. Here's an example:
[cid:image001.png@01D19FD0.2A25A860]
Anyone know what that's about?
Frank
Are there packet counters / graphs to determine where the flood came in from? Also maybe not related, but on the naix-discuss list recently there was mention of an arp flooding issue w/ mikrotik that has been recently resolved. Dale Thus spake Frank Bulk (fbulk@MYPREMIERONLINE.COM) on Wed, Apr 27, 2016 at 01:40:50PM +0000:
Dale -- good point. But why did it kick in? Why would an issue with a peer cause/result in a flood of outbound traffic on other ports?
Frank
-----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Dale W. Carder Sent: Tuesday, April 26, 2016 3:40 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] HE issue this afternoon
Given the rate, it looks like a 10Mbit/sec storm-control policer.
Dale
Thus spake Frank Bulk (fbulk@MYPREMIERONLINE.COM) on Tue, Apr 26, 2016 at 08:30:07PM +0000:
During this afternoon's HE hiccup (https://puck.nether.net/pipermail/outages/2016-April/008962.html) there was a flood of outbound traffic on the Main Switch's ge-1/0/10, 12, 16, 22, and 23. Here's an example:
[cid:image001.png@01D19FD0.2A25A860]
Anyone know what that's about?
Frank
On Tue, Apr 26, 2016 at 08:30:07PM +0000, Frank Bulk wrote:
During this afternoon's HE hiccup (https://puck.nether.net/pipermail/outages/2016-April/008962.html) there was a flood of outbound traffic on the Main Switch's ge-1/0/10, 12, 16, 22, and 23. Here's an example:
Anyone know what that's about?
I'd think it is just a monitoring glitch. Monitoring of the devices happens to route through ipHouse (rather than direct across the exchange) due to old timing of onboarding. And we at ipHouse were definately impacted by HE's route engine failover event. We shut down HE pretty quickly, but I could see some packets going awry while that was happening. -- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
HE reported to me their issue was in Chicago. ________________________________________ From: MICE Discuss [MICE-DISCUSS@LISTS.IPHOUSE.NET] on behalf of Doug McIntyre [merlyn@IPHOUSE.NET] Sent: Tuesday, April 26, 2016 3:41 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] HE issue this afternoon On Tue, Apr 26, 2016 at 08:30:07PM +0000, Frank Bulk wrote:
During this afternoon's HE hiccup (https://puck.nether.net/pipermail/outages/2016-April/008962.html) there was a flood of outbound traffic on the Main Switch's ge-1/0/10, 12, 16, 22, and 23. Here's an example:
Anyone know what that's about?
I'd think it is just a monitoring glitch. Monitoring of the devices happens to route through ipHouse (rather than direct across the exchange) due to old timing of onboarding. And we at ipHouse were definately impacted by HE's route engine failover event. We shut down HE pretty quickly, but I could see some packets going awry while that was happening. -- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
There's no gaps in the graph, so no indication it was a polling issue. There's every reason to believe it really did happen -- I'm just trying to understand why. =) Frank -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Doug McIntyre Sent: Tuesday, April 26, 2016 3:42 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] HE issue this afternoon On Tue, Apr 26, 2016 at 08:30:07PM +0000, Frank Bulk wrote:
During this afternoon's HE hiccup (https://puck.nether.net/pipermail/outages/2016-April/008962.html) there was a flood of outbound traffic on the Main Switch's ge-1/0/10, 12, 16, 22, and 23. Here's an example:
Anyone know what that's about?
I'd think it is just a monitoring glitch. Monitoring of the devices happens to route through ipHouse (rather than direct across the exchange) due to old timing of onboarding. And we at ipHouse were definately impacted by HE's route engine failover event. We shut down HE pretty quickly, but I could see some packets going awry while that was happening. -- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
I know they had something with their Chicago router today. We opened a ticket with them when we lost routes through our separate transit link with them for about 5 minutes earlier today. On Apr 26, 2016 3:30 PM, "Frank Bulk" <fbulk@mypremieronline.com> wrote:
During this afternoon’s HE hiccup ( https://puck.nether.net/pipermail/outages/2016-April/008962.html) there was a flood of outbound traffic on the Main Switch’s ge-1/0/10, 12, 16, 22, and 23. Here’s an example:
Anyone know what that’s about?
Frank
------------------------------
To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
Greetings everyone. And Reid. :-) Our implementation is proceeding and we’re projecting that we’ll be moving bits back to the exchange in the next few weeks. Unfortunately, we’re dropping our route server sessions permanently. Everyone who is now route server only will need to established bi lateral peering. Send your peering request to peering@akamai.com<mailto:peering@akamai.com> with the requisite details (ASN, peer addresses). If you had a direct session previously, we have not forgotten it and there’s no need to restate. Traffic will return slowly, first with our SSL bits and then full on edge a few weeks after that. Thanks for your patience and for helping to build a better Internet in MSP. Best, Martin Hannigan // AS 20940 // AS 32787
Thanks Marty, If someone with appropriate permissions could copy Marty's email to the announce list, I feel it should reach more of the membership since not everyone monitors the discuss list. From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Hannigan, Martin Sent: Tuesday, April 26, 2016 9:34 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Update for Akamai (AS 20940) < > MICE Greetings everyone. And Reid. :-) Our implementation is proceeding and we’re projecting that we’ll be moving bits back to the exchange in the next few weeks. Unfortunately, we’re dropping our route server sessions permanently. Everyone who is now route server only will need to established bi lateral peering. Send your peering request to peering@akamai.com with the requisite details (ASN, peer addresses). If you had a direct session previously, we have not forgotten it and there’s no need to restate. Traffic will return slowly, first with our SSL bits and then full on edge a few weeks after that. Thanks for your patience and for helping to build a better Internet in MSP. Best, Martin Hannigan // AS 20940 // AS 32787 To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
I haven't seen this approach to an administrative operational message before. Isnt this the right list? This is routine stuff. *shrug* Best, -M< On Apr 27, 2016, at 08:07, Jeremy Lumby <jlumby@MNVOIP.COM<mailto:jlumby@mnvoip.com>> wrote: Thanks Marty, If someone with appropriate permissions could copy Marty's email to the announce list, I feel it should reach more of the membership since not everyone monitors the discuss list. From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Hannigan, Martin Sent: Tuesday, April 26, 2016 9:34 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@lists.iphouse.net> Subject: [MICE-DISCUSS] Update for Akamai (AS 20940) < > MICE Greetings everyone. And Reid. :-) Our implementation is proceeding and we're projecting that we'll be moving bits back to the exchange in the next few weeks. Unfortunately, we're dropping our route server sessions permanently. Everyone who is now route server only will need to established bi lateral peering. Send your peering request to peering@akamai.com<mailto:peering@akamai.com> with the requisite details (ASN, peer addresses). If you had a direct session previously, we have not forgotten it and there's no need to restate. Traffic will return slowly, first with our SSL bits and then full on edge a few weeks after that. Thanks for your patience and for helping to build a better Internet in MSP. Best, Martin Hannigan // AS 20940 // AS 32787 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.iphouse.net_cgi-2Dbin_wa-3FSUBED1-3DMICE-2DDISCUSS-26A-3D1&d=CwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=XDN_BIPGnpb6V0w5M9FADw&m=rJpXMdJamxoU8AOC0gQU85xMJnmr9CIC6bbSPV1oWa0&s=LHQhnMsKOLKFM631rt8zd9iIYG-gj-96vjXMOBrczfA&e=> ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.iphouse.net_cgi-2Dbin_wa-3FSUBED1-3DMICE-2DDISCUSS-26A-3D1&d=CwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=XDN_BIPGnpb6V0w5M9FADw&m=rJpXMdJamxoU8AOC0gQU85xMJnmr9CIC6bbSPV1oWa0&s=LHQhnMsKOLKFM631rt8zd9iIYG-gj-96vjXMOBrczfA&e=>
This is the right list. Not everyone follows it. On Apr 27, 2016 7:17 AM, "Hannigan, Martin" <marty@akamai.com> wrote:
I haven't seen this approach to an administrative operational message before. Isnt this the right list? This is routine stuff. *shrug*
Best,
-M<
On Apr 27, 2016, at 08:07, Jeremy Lumby <jlumby@MNVOIP.COM <jlumby@mnvoip.com>> wrote:
Thanks Marty, If someone with appropriate permissions could copy Marty's email to the announce list, I feel it should reach more of the membership since not everyone monitors the discuss list.
*From:* MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET <MICE-DISCUSS@LISTS.IPHOUSE.NET>] *On Behalf Of *Hannigan, Martin *Sent:* Tuesday, April 26, 2016 9:34 PM *To:* MICE-DISCUSS@LISTS.IPHOUSE.NET <MICE-DISCUSS@lists.iphouse.net> *Subject:* [MICE-DISCUSS] Update for Akamai (AS 20940) < > MICE
Greetings everyone. And Reid. :-)
Our implementation is proceeding and we’re projecting that we’ll be moving bits back to the exchange in the next few weeks.
Unfortunately, we’re dropping our route server sessions permanently. Everyone who is now route server only will need to established bi lateral peering. Send your peering request to peering@akamai.com with the requisite details (ASN, peer addresses). If you had a direct session previously, we have not forgotten it and there’s no need to restate. Traffic will return slowly, first with our SSL bits and then full on edge a few weeks after that.
Thanks for your patience and for helping to build a better Internet in MSP.
Best,
Martin Hannigan // AS 20940 // AS 32787
------------------------------
To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.iphouse.net_cgi-2Dbin_wa-3FSUBED1-3DMICE-2DDISCUSS-26A-3D1&d=CwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=XDN_BIPGnpb6V0w5M9FADw&m=rJpXMdJamxoU8AOC0gQU85xMJnmr9CIC6bbSPV1oWa0&s=LHQhnMsKOLKFM631rt8zd9iIYG-gj-96vjXMOBrczfA&e=>
------------------------------
To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.iphouse.net_cgi-2Dbin_wa-3FSUBED1-3DMICE-2DDISCUSS-26A-3D1&d=CwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=XDN_BIPGnpb6V0w5M9FADw&m=rJpXMdJamxoU8AOC0gQU85xMJnmr9CIC6bbSPV1oWa0&s=LHQhnMsKOLKFM631rt8zd9iIYG-gj-96vjXMOBrczfA&e=>
------------------------------
To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
Posting to announce list now Shaun Carlson Director of Information Technology | Arvig ph: (218) 346.8673 | em: shaun.carlson@arvig.com On Wed, Apr 27, 2016 at 5:24 AM -0700, "Jason Hanke" <jayhanke@neutralpath.net> wrote: This is the right list. Not everyone follows it. On Apr 27, 2016 7:17 AM, "Hannigan, Martin" <marty@akamai.com> wrote: I haven't seen this approach to an administrative operational message before. Isnt this the right list? This is routine stuff. *shrug* Best, -M< On Apr 27, 2016, at 08:07, Jeremy Lumby <jlumby@MNVOIP.COM> wrote: Thanks Marty, If someone with appropriate permissions could copy Marty's email to the announce list, I feel it should reach more of the membership since not everyone monitors the discuss list. From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Hannigan, Martin Sent: Tuesday, April 26, 2016 9:34 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Update for Akamai (AS 20940) < > MICE Greetings everyone. And Reid. :-) Our implementation is proceeding and we’re projecting that we’ll be moving bits back to the exchange in the next few weeks. Unfortunately, we’re dropping our route server sessions permanently. Everyone who is now route server only will need to established bi lateral peering. Send your peering request to peering@akamai.com with the requisite details (ASN, peer addresses). If you had a direct session previously, we have not forgotten it and there’s no need to restate. Traffic will return slowly, first with our SSL bits and then full on edge a few weeks after that. Thanks for your patience and for helping to build a better Internet in MSP. Best, Martin Hannigan // AS 20940 // AS 32787 To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
NM, beat to the punch by someone with faster Internet access (service sucks out here in Delaware). S Shaun Carlson Director of Information Technology | Arvig ph: (218) 346.8673 | em: shaun.carlson@arvig.com On Wed, Apr 27, 2016 at 5:29 AM -0700, "Mike Horwath" <drechsau@geeks.org> wrote: On Wed, Apr 27, 2016 at 12:29:25PM +0000, Shaun Carlson wrote:
Posting to announce list now
Ha, I already did. -- Mike Horwath, reachable via drechsau@Geeks.ORG
Has anyone heard back from peering@akamai.com ? It has been almost 2 weeks, my bi-lateral peering request has gone unanswered, and the session I built for them is not established. I know Marty mentioned they were working on some things, however I have not even gotten a reply acknowledging my emails. Jeremy From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Hannigan, Martin Sent: Tuesday, April 26, 2016 9:34 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Update for Akamai (AS 20940) < > MICE Greetings everyone. And Reid. :-) Our implementation is proceeding and we’re projecting that we’ll be moving bits back to the exchange in the next few weeks. Unfortunately, we’re dropping our route server sessions permanently. Everyone who is now route server only will need to established bi lateral peering. Send your peering request to peering@akamai.com with the requisite details (ASN, peer addresses). If you had a direct session previously, we have not forgotten it and there’s no need to restate. Traffic will return slowly, first with our SSL bits and then full on edge a few weeks after that. Thanks for your patience and for helping to build a better Internet in MSP. Best, Martin Hannigan // AS 20940 // AS 32787 ________________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
Likewise here, crickets……
On May 9, 2016, at 9:05 PM, Jeremy Lumby <jlumby@mnvoip.com> wrote:
Has anyone heard back from peering@akamai.com ? It has been almost 2 weeks, my bi-lateral peering request has gone unanswered, and the session I built for them is not established. I know Marty mentioned they were working on some things, however I have not even gotten a reply acknowledging my emails.
Jeremy
From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Hannigan, Martin Sent: Tuesday, April 26, 2016 9:34 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Update for Akamai (AS 20940) < > MICE
Greetings everyone. And Reid. :-)
Our implementation is proceeding and we’re projecting that we’ll be moving bits back to the exchange in the next few weeks.
Unfortunately, we’re dropping our route server sessions permanently. Everyone who is now route server only will need to established bi lateral peering. Send your peering request to peering@akamai.com with the requisite details (ASN, peer addresses). If you had a direct session previously, we have not forgotten it and there’s no need to restate. Traffic will return slowly, first with our SSL bits and then full on edge a few weeks after that.
Thanks for your patience and for helping to build a better Internet in MSP.
Best,
Martin Hannigan // AS 20940 // AS 32787
________________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
Ill take a look in the queue. Thanks
On May 9, 2016, at 21:09, Andrew Hoyos <hoyosa@GMAIL.COM> wrote:
Likewise here, crickets……
On May 9, 2016, at 9:05 PM, Jeremy Lumby <jlumby@mnvoip.com> wrote:
Has anyone heard back from peering@akamai.com ? It has been almost 2 weeks, my bi-lateral peering request has gone unanswered, and the session I built for them is not established. I know Marty mentioned they were working on some things, however I have not even gotten a reply acknowledging my emails.
Jeremy
From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Hannigan, Martin Sent: Tuesday, April 26, 2016 9:34 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Update for Akamai (AS 20940) < > MICE
Greetings everyone. And Reid. :-)
Our implementation is proceeding and we’re projecting that we’ll be moving bits back to the exchange in the next few weeks.
Unfortunately, we’re dropping our route server sessions permanently. Everyone who is now route server only will need to established bi lateral peering. Send your peering request to peering@akamai.com with the requisite details (ASN, peer addresses). If you had a direct session previously, we have not forgotten it and there’s no need to restate. Traffic will return slowly, first with our SSL bits and then full on edge a few weeks after that.
Thanks for your patience and for helping to build a better Internet in MSP.
Best,
Martin Hannigan // AS 20940 // AS 32787
________________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
All, I did look and we have received your requests. They will be taken care of shortly. Apologies for the delay. Best,, Marty
On May 9, 2016, at 21:38, Hannigan, Martin <marty@akamai.com> wrote:
Ill take a look in the queue.
Thanks
On May 9, 2016, at 21:09, Andrew Hoyos <hoyosa@GMAIL.COM> wrote:
Likewise here, crickets……
On May 9, 2016, at 9:05 PM, Jeremy Lumby <jlumby@mnvoip.com> wrote:
Has anyone heard back from peering@akamai.com ? It has been almost 2 weeks, my bi-lateral peering request has gone unanswered, and the session I built for them is not established. I know Marty mentioned they were working on some things, however I have not even gotten a reply acknowledging my emails.
Jeremy
From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Hannigan, Martin Sent: Tuesday, April 26, 2016 9:34 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Update for Akamai (AS 20940) < > MICE
Greetings everyone. And Reid. :-)
Our implementation is proceeding and we’re projecting that we’ll be moving bits back to the exchange in the next few weeks.
Unfortunately, we’re dropping our route server sessions permanently. Everyone who is now route server only will need to established bi lateral peering. Send your peering request to peering@akamai.com with the requisite details (ASN, peer addresses). If you had a direct session previously, we have not forgotten it and there’s no need to restate. Traffic will return slowly, first with our SSL bits and then full on edge a few weeks after that.
Thanks for your patience and for helping to build a better Internet in MSP.
Best,
Martin Hannigan // AS 20940 // AS 32787
________________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
Same boat here as well. Jeff Anderson jeffa@implex.net 612.799.7277 Cell 612.339.8255 x200 Office 612.339.3310 Fax -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Jeremy Lumby Sent: Monday, May 9, 2016 9:05 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Update for Akamai (AS 20940) < > MICE Has anyone heard back from peering@akamai.com ? It has been almost 2 weeks, my bi-lateral peering request has gone unanswered, and the session I built for them is not established. I know Marty mentioned they were working on some things, however I have not even gotten a reply acknowledging my emails. Jeremy From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Hannigan, Martin Sent: Tuesday, April 26, 2016 9:34 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Update for Akamai (AS 20940) < > MICE Greetings everyone. And Reid. :-) Our implementation is proceeding and we’re projecting that we’ll be moving bits back to the exchange in the next few weeks. Unfortunately, we’re dropping our route server sessions permanently. Everyone who is now route server only will need to established bi lateral peering. Send your peering request to peering@akamai.com with the requisite details (ASN, peer addresses). If you had a direct session previously, we have not forgotten it and there’s no need to restate. Traffic will return slowly, first with our SSL bits and then full on edge a few weeks after that. Thanks for your patience and for helping to build a better Internet in MSP. Best, Martin Hannigan // AS 20940 // AS 32787 ________________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
participants (12)
-
Andrew Hoyos -
Brady Kittel -
Dale W. Carder -
Doug McIntyre -
Frank Bulk -
Hannigan, Martin -
Jason Hanke -
Jeff Anderson -
Jeremy Lumby -
Justin Krejci -
Mike Horwath -
Shaun Carlson