Hi I hate the way Outlook handles mailinglists but anyway. Just on this caching issue, what are you noticing issues with? The network is redundant so issues with a single CDN server shouldn't affect your deployments at all. Office365 only uses the CDN for webmail access and that has thousands of servers and Ip's available so it's a non issue. If it's a hybrid environment use more than one network provider. Or buy Azure Express Route and get private connectivity. That way it's not a problem. You should log an issue with Microsoft as they will need to sort any network issues. The relationship with Akamai is between Microsoft and Akamai.
Chad Kelly Manager CPK Web Services Phone 03 52730246 Web https://www.cpkws.com.au -----Original Message----- From: AusNOG <[email protected]> On Behalf Of [email protected] Sent: Monday, 6 April 2020 12:00 PM To: [email protected] Subject: AusNOG Digest, Vol 98, Issue 5 Send AusNOG mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://lists.ausnog.net/mailman/listinfo/ausnog or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of AusNOG digest..." Today's Topics: 1. Vocus Office 365 CDN corrupt again (Samuel D. Leslie) ---------------------------------------------------------------------- Message: 1 Date: Sun, 5 Apr 2020 08:17:41 +0000 From: "Samuel D. Leslie" <[email protected]> To: "[email protected]" <[email protected]> Subject: [AusNOG] Vocus Office 365 CDN corrupt again Message-ID: <me3p282mb075591280c02771dd63f4177c8...@me3p282mb0755.ausp282.prod.outlook.com> Content-Type: text/plain; charset="us-ascii" Looks like the Office 365 CDN on the Vocus network is corrupt again. This has happened before (see earlier thread from February 2020). If anyone from Vocus is on this list, or someone here has any contacts at Vocus, it'd be much appreciated if you could raise it with someone who can look into it. This has been causing some sporadic but frustrating issues on our Office 365 deployments since the start of the year. For anyone else reading this, if you're seeing Office 365 deployments running for an abnormally long time before eventually failing you may be seeing the same issue. Affected Vocus server: Name: a1737.dspw65.akamai.net Addresses: 2403:4800:3003:4::8bda:1520 2403:4800:3003:4::8bda:150a 139.218.20.194 139.218.20.187 Aliases: officecdn.microsoft.com.edgesuite.net officecdn.microsoft.com.edgesuite.net.globalredir.akadns.net Sample corrupted SHA-256 file hashes: pr/492350f6-3a01-4f97-b9c0-c7c6ddf67d60/Office/Data/16.0.12624.20382/i640.cab Vocus: 692D7A31176A0F26FB018613B4AE24CDC1E49481B95C890A0674637FFE0DA9E9 Correct: B4295DCB07D3F7753B6D939CF950FA63419DD0D85C931580777C419F5C6DD32E Cheers, Samuel Leslie ------------------------------ Subject: Digest Footer _______________________________________________ AusNOG mailing list [email protected] http://lists.ausnog.net/mailman/listinfo/ausnog ------------------------------ End of AusNOG Digest, Vol 98, Issue 5 ************************************* _______________________________________________ AusNOG mailing list [email protected] http://lists.ausnog.net/mailman/listinfo/ausnog
