You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since sometime recently, various websites frequently cause 6-hour stalls. It's unclear when this started exactly, but it became very noticeable (i.e. multiple jobs hanging every few hours) in October, I think. They have in common that they're all fronted by Akamai's CDN, i.e. they're all CNAME something.edgekey.net.. Some examples:
www.ea.com, help.ea.com, and more (including outside of ea.com itself)
www.adobe.com
www.microsoft.com
www.amd.com, support.amd.com
olympics.com
investors.biontech.de
media.ford.com
www.health.gov.au
www.nokia.com
www.tesla.com
ir.gitlab.com
investors.bentley.com
www.climateactive.org.au
www.ups.com
www.businesswire.com
Not all requests on all Akamai-using websites or even all of these listed domains are stalling. Sometimes, connections time out after a long time (15-20 minutes) instead. There may be some relation to the request headers; in one case (investors.biontech.de), it appeared that not including a Connection header would cause the stalls when using HTTP/1.1, but that may not be the whole explanation.
The text was updated successfully, but these errors were encountered:
Since sometime recently, various websites frequently cause 6-hour stalls. It's unclear when this started exactly, but it became very noticeable (i.e. multiple jobs hanging every few hours) in October, I think. They have in common that they're all fronted by Akamai's CDN, i.e. they're all
CNAME something.edgekey.net.. Some examples:www.ea.com,help.ea.com, and more (including outside of ea.com itself)www.adobe.comwww.microsoft.comwww.amd.com,support.amd.comolympics.cominvestors.biontech.demedia.ford.comwww.health.gov.auwww.nokia.comwww.tesla.comir.gitlab.cominvestors.bentley.comwww.climateactive.org.auwww.ups.comwww.businesswire.comNot all requests on all Akamai-using websites or even all of these listed domains are stalling. Sometimes, connections time out after a long time (15-20 minutes) instead. There may be some relation to the request headers; in one case (
investors.biontech.de), it appeared that not including aConnectionheader would cause the stalls when using HTTP/1.1, but that may not be the whole explanation.The text was updated successfully, but these errors were encountered: