Yeah, noticed this as well. A lot of badges seem to be displaying unknown on them.
Screenshot from doc site:

Yep, guess it's related to this https://twitter.com/zeit_status/status/1089961390624755714
Created a new deployment to refresh caches, should be fine by now.
Yeah this looks resolved to me 馃憤
Close #229
this error is back 馃槙
although it's impacting the GitHub ones disproportionately.
Maybe it's on the API side?

Looks like we are hitting rate limit 馃
It's not rate limited, only half quota used. And the api works fine now, I'm not sure what caused that 馃槙
@amio You might try adding the s-maxage cache control header.
@styfle The s-maxage header is added:
cache-control: public, max-age=60, stale-while-revalidate=604800, stale-if-error=604800, s-maxage=360
Most helpful comment
Looks like that fixed most of them
https://screenshot-v2.now.sh/badgen.net?fullPage=true