Thanks for reporting and reproing! We have a fix in progress, but the problem occurs when we upload the file to S3; so files already uploaded will continue not to work after we deploy this fix and will need to wait for a backfill. I’ll update when we’ve deployed the fix so you can reupload the file to get it working in the meantime.
The issue is that sometimes we incorrectly set an xml content type on files that should be svg, which I believe our content security settings were then preventing from displaying.
This fix is deployed, if you reupload your SVG it should work correctly now.
We’re not going to backfill these to avoid changing behavior out from under anyone, but for anyone else experiencing this with SVG files uploaded before now downloading the file and reuploading it should give that file the correct content type.