Cache Collision (Now Resolved)

While working to fix some caching issues yesterday, we inadvertently introduced a bug that caused erroneous cache collisions. This issue may have affected your requests that had cache enabled.