
So what to do as a user of the sites? We're not associated with these sites at all but end users call our help desk blaming us. Both examples are common sites to go to, and today they decide to act up. Thoughts on why today is the day? Sent from Yahoo Mail on Android From:"Jordan Michaels via Outages" <outages@outages.org> Date:Wed, Sep 30, 2015 at 6:59 PM Subject:Re: [outages] Akamai Cert Issues today Nice to know. I noticed this recently on the Vimeo API as well, so it's not just Gov sites. Thank you for taking the time to share the info. Kind regards, Jordan Michaels ----- Original Message ----- From: "Sean Donelan via Outages" <outages@outages.org> To: Outages@outages.org Sent: Wednesday, September 30, 2015 3:29:04 PM Subject: Re: [outages] Akamai Cert Issues today On Wed, 30 Sep 2015, Jim Witherell via Outages wrote:
e noticed SSL warnings based around Akamai's "a248.e.akamai.net" certificate today. NET::ERR_CERT_COMMON_NAME_INVALID is the most common error we're seeing. Can anyone comment on what may be going on? Looks like the cert was renewed or issued on 8/27/2015. Wonder why we are noticing the errors from multiple points on the internet now?
This is how Akamai has handled non-SSL customers for the last 15 years. It is the same error message, and the same action. You just noticed it. If you use https for a non-SSL customer on Akamai, you will connect to a Akamai server using a "default" SSL certificate for all customers on port 443. If you use https for a SSL customer on Akamai, you connect to different IP addresses listening for specific customers which return a customer specific SSL certificate. _______________________________________________ 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