This morning we had a large explosion of reports that some of our services on frame where not working.
It was effecting people in the UK pretty heavy and it sounds like some other regions where feeling it also.
Here are the console logs from one of the users experiencing the problem.
I think the short term solution will be to not use the CDN but we figured we will call this out to bring to the teams attention.
Thanks!
Definitely an urgent issue for us here on Frame, because it’s breaking our production build @Deltakosh !
also flagging @RaananW because I know he’s had his head in that decoder before.
I’ve experienced this outage for a short period of time as well. Now it’s ok.
Also the snippet servers were unreachable.
You experienced it this morning @roland ?
We are not reproducing it here 
Any link we can try to test?
It appears to maybe be regional @Deltakosh , some users are just fine and others can’t get this cdn url to work. Latest user I saw who didn’t have it work was from the UK if that helps!
Also please all keep in mind:
https://doc.babylonjs.com/setup/frameworkPackages/CDN
We have no control over that. This is Azure infrastructure. They will fix it asap
@SirFizX maybe you can articulate some of the challenges we’ve had hosting this ourselves?
The self-hosting documentation by the Babylon team is great however, the changes to our webpack settings alone will require some solid QA before a patch can get in.
Depend on where we live 
˜ 8-9 hours ago.
