Incorrect MIME Type Headers for JavaScript SDK Plugin Artifacts

What to do

• Check whether your product depends on RudderStack. Check your stack

  Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2024-12-17 09:45 UTC and 2024-12-17 09:45 UTC may need a replay.

• Subscribe to RudderStack's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=rudderstack works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Root cause

Impact: The issue did not affect all customers uniformly due to the nature of content distribution via the CDN.

Updates from RudderStack 1

1. resolvedDec 17, 2024, 9:45 AM UTC

   Incident Summary: RudderStack encountered an issue where JavaScript SDK plugin artifacts were served with incorrect MIME type headers (binary/octet-stream) from our CDN. This caused modern browsers to reject the scripts, resulting in plugin loading failures and a loss of instrumented events to RudderStack and device mode destinations. Impact: The issue did not affect all customers uniformly due to the nature of content distribution via the CDN. Some customers experienced the issue earlier as their regions picked up the changes, while others saw delayed or minimal impact. Resolution: The incorrect MIME type was promptly corrected to application/javascript, and normal functionality was restored. We sincerely apologize for any inconvenience caused and thank you for your understanding. If you have further questions or concerns, please contact our support team.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.