Nev

Why is this occurring? Please see this public announcement [Azure CDN from Edgio retirement FAQ](https://learn.microsoft.com/en-us/azure/cdn/edgio-retirement-faq) where this domain (`az416426.vo.msecnd.net` is currently an Edgio based CDN instance) and because of the...

Correct, this issue ONLY affects users that are loading the SDK via the legacy CDN, if you are using the newer SDK Loader (snippet) which defaults to the current CDN...

Update: We have just started the process of redirecting this domain (hopefully) to avoid any possible outage, this change "should" take affect within the next couple of hours. Known Issue...

The DNS (CNAME) entry has been redirected, and we appear to be seeing successful traffic being redirected to the new CDN. However, the DNS Zone delegation still needs to be...

I've just "re-enabled" `http` access on this legacy endpoint (it had been defaulted to redirect all `http` -> `https`). It appears that referrers that had been requesting `http` versions where...

DNS Delegation has just been migrated and appears to be resolving as expected. One more final step scheduled for tomorrow (PST) to complete the migration process.

The final mitigation step is now complete, significantly reducing the risk of an outage for this domain due to the Edgio retirement. However, this domain is now entering a more...

The JS Sdk doesn't currently populate the `tracestate` header only the `traceparent` (as part of the Application Insights XMLHttpRequest and fetch hooking (if enabled))

We are currently actively prototyping how we are going to add `tracestate` support along with easier management of the `traceparent` by providing additional OpenTelemetry style "Span" support within the SDK....

As the base support will be added to Application Insights, I'm also going to move this Issue to that repo, now that I've marked as an enhancement