Yes, I have logs showing that we are indeed getting TooManyRequests. This is specifically for the live activity broadcast API and not for the push notification. We have concurrent games happening around the same time and i believe we do not send more than one update per channel per second. Is there a recommendation on number of open connection and keep-alive settings for APNS broadcast? I will get more details on the rate limit that we are seeing on our end.

Here is some more data regarding the throttling grouped by hour: --- | day | hour | ThrottleCount | | --- | --- | --- | | 2026-05-27 00:00:00.000 | 2026-05-27 03:00:00.000 | 1 | | 2026-05-27 00:00:00.000 | 2026-05-27 02:00:00.000 | 25 | | 2026-05-27 00:00:00.000 | 2026-05-27 01:00:00.000 | 16 | | 2026-05-25 00:00:00.000 | 2026-05-25 02:00:00.000 | 26 | | 2026-05-25 00:00:00.000 | 2026-05-25 01:00:00.000 | 3 | | 2026-05-25 00:00:00.000 | 2026-05-25 00:00:00.000 | 3 | ---

I mean TLS connection with APNS. We have multiple connection with keep-alive set to 10 mins. Reg channels, we have one channel per game. We are doing max 8-9 updates per min per channel occasionally (game clock plus score updates).