Technically this problem is already solved but it was so severe that it's going to take several days to collect enough sample runs.  Right now Component Readiness is flagging the following test as regressed:

• [OLM][invariant] alert/KubePodNotReady should not be at or above info in ns/openshift-marketplace

Please mark the OLM / Akamai cache problem as triaged.  This test runs at a high frequency and has not failed once in over 48 hours since the problem was addressed.  You can find more on the backstory of this situation in this jira:

• https://issues.redhat.com/browse/OCPBUGS-33052

Most importantly, you can use this link in sippy to see the test has dramatically improved across all platforms since the Akamai issue was resolved.

https://sippy.dptools.openshift.org/sippy-ng/tests/4.16/analysis?filters=%257B%2522items%2522%253A%255B%257B%2522columnField%2522%253A%2522name%2522%252C%2522operatorValue%2522%253A%2522equals%2522%252C%2522value%2522%253A%2522%255BOLM%255D%255Binvariant%255D%2520alert%252FKubePodNotReady%2520should%2520not%2520be%2520at%2520or%2520above%2520info%2520in%2520ns%252Fopenshift-marketplace%2522%257D%252C%257B%2522columnField%2522%253A%2522variants%2522%252C%2522not%2522%253Atrue%252C%2522operatorValue%2522%253A%2522contains%2522%252C%2522value%2522%253A%2522never-stable%2522%257D%252C%257B%2522columnField%2522%253A%2522variants%2522%252C%2522not%2522%253Atrue%252C%2522operatorValue%2522%253A%2522contains%2522%252C%2522value%2522%253A%2522aggregated%2522%257D%255D%252C%2522linkOperator%2522%253A%2522and%2522%257D&test=%5BOLM%5D%5Binvariant%5D%20alert%2FKubePodNotReady%20should%20not%20be%20at%20or%20above%20info%20in%20ns%2Fopenshift-marketplace