
Anyone have an opinion either way on whether this is at Microsoft's end? User logs into Outlook.com for their hosted domain, using Chrome (for which they have a bookmark-bar link, so I assume it's what they usually use), and after several seconds of delay (5-15), they get this: === UTC Date: 2024-10-14T16:04:31.323Z Client Id: E6FE5F2C16B7401FA8BBAED29635B969 Session Id: 9edcbe8e-dffb-4ba2-a03d-3231d2c178ee Client Version: 20240927008.13 BootResult: network Back Filled Errors: Unhandled Rejection: TypeError: Failed to fetch:undefined|Unhandled Rejection: TypeError: Failed to fetch:undefined|Unhandled Rejection: TypeError: StartupData:StartupData:Failed to fetch:undefined|Unhandled Rejection: TypeError: StartupData:StartupData:Failed to fetch:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined err: TypeError: StartupData:StartupData:Failed to fetch esrc: StartupData et: ServerError estack: TypeError: Failed to fetch at https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mai... at new Promise (<anonymous>) at a (https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mai...) at https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mai... at async https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mai... === That sure feels server-end to me, but I'm not seeing any other reports about it so far. Most of their office uses Windows-Outlook, and appears to be fine. We're tracking a couple other windows-domain-login problems there, but I don't believe those could apply to OWA, right? Cheers, -- jra -- Jay R. Ashworth Baylink jra@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274 _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages