Due to a routing issue with our infrastructure, some requests to our playingnow., aircheck. and managedstreaming. services were not served properly and received a 502 timeout error. The issue was automatically mitigated and recovered after just a few minutes.

aircheck. frontend recovered.

aircheck. frontend went down.

managedstreaming. edge service recovered.

managedstreaming. edge service went down and playingnow. APIs recovered.

playingnow. APIs went down.