Looks like that issue was created Jan 10th and the fix was merged 6 hours ago. Apparently, it was a regression:
> UPDATE: cause was cname adblocking, so this is a regression, not an earlier issue.
> UPDATE: cause was cname adblocking, so this is a regression, not an earlier issue.