Fixed Notifications not showing - Can't bump trades on profile

Device: PC
Browser: Chrome
OS: Windows 10

Steps to reproduce:
Refresh

Anything else to add:
Cleared browser cache and didn't resolve
So the notification button if you get a comment on a trade just doesn't show up.
Went to profile to bump all trades and the tooltip comes up over the button -> can't click the button
Can navigate around the site no issue

Same, no Bell here

+1

Autolink seems to be broken in general.
For example, when I try to hover names here I see nothing: no trust amount, no pop-up AT ALL.
Also, I dont see the icons (ladder, HC, region, etc.) below everyone names.

Edit: here is what I see, icons seems to be visible for some user, although not all of them: Edit2: attached image do not show either...

Looks like maybe a CDN outage at whatever your endpoint is. CDN serves the scripts so if it's down no script gets served = stuff appears broken. Should resolve itself in a few hours, can't really do anything about this at the moment as I'm travelling.

If someone wants to open their browser console - you can see which URL is responsible (probably unpackagd or something like that). I really need to move these scripts locally...

Here you are, Teebling, sorry it's in French but I think you have most info in it:

La ressource à l’adresse « styles/zulu/theme/Formal436BT.ttf » préchargée avec le préchargement de lien n’a pas été utilisée après quelques secondes. Assurez-vous que tous les attributs de la balise de préchargement sont définis correctement. notifications-not-showing-can-t-bump-trades-on-profile-t1175658.html
Erreur dans les liens source : Error: request failed with status 520
URL de la ressource : https://unpkg.com/tippy.js@6
URL du lien source : tippy-bundle.umd.min.js.map

Yeah, so looks like problems with either Unpkg, their CDN provider, or NPM itself. Thanks Nec. These things usually get resolved fairly quickly.

Again, not much I can do right now. If you're reading this, I would recommend NOT clearing your cache (so that your browser falls back to the cached version of the script that unpackg is failing to deliver to you).

And now it's working again

Edit: and now it's not?...

Edit2: and now it's working again? :

Confuse:

Edit3: as I edit this post, the bell is still playing hide and seek.