3 ms·

Same here, but on chromium PC.

• chefandy 2y ago
  Maybe a broken cache on an edge network serving up a bad asset to only some geographic areas, or something that was served broken for a moment but got cached.