Chrome bug affecting web fonts
Chrome 33 has been released on 20 February 2014, which includes a fix for the disappearing web font bug. We highly recommend upgrading to Chrome 33 (or higher) as soon as possible.
If you are still seeing issues with fonts loading in Chrome, you may be affected by a different bug in Chrome 33.
We’ve been getting reports from Typekit customers about web fonts disappearing and being replaced with fallback fonts. We believe this to be caused by this bug in Chrome, which can affect any web font (not just those served from Typekit).
The bug is most apparent in Chrome 32 and affects all platforms. It causes fonts to randomly fall back to the last-resort font, which is normally used when Chrome can’t find any of the fonts in the CSS
font-family stack. The last-resort font is platform specific; on OS X a serif font is used, while other platforms might use a sans-serif font.
The Chrome team is aware of the problem and has already fixed the bug. The bug fix will be in Chrome 33, which is planned for release in late February. Please let us know at email@example.com if you have any questions.
Update, 08 April: Chrome 34 was released on 08 April 2014 and includes a fix for the disappearing web font bugs in Chrome 33. If you continue to see issues with Typekit fonts after upgrading to v34, email firstname.lastname@example.org and we will look into it.