The broadcast push has already been discussed above so no need to revisit this. The question now is what can cause a message to get dropped from device side? I was on wifi and i see sometimes the updates stops even though I can see that it was successfully sent to APNS from logs.

After some testing, I can confirm that APNS broadcast throttling has been zero if I keep my updates up to 4 per min. Hopefully, this is helpful to someone running into a similar issue. However, now I see another issue where a device sometimes does not get channel updates. I can confirm that battery looks good and allow frequent updates is enabled so wonder what might be causing the device to drop updates?

does sandbox and production environment have the same rate limits per channel or do they vary? This will help me determine if sandbox load testing is sufficient.

Thanks for looking into this. I understand your concern but some general guidance in public documentation will help us design solutions while keeping this limit in mind. the guideline is generally no more than one update per second per activity. This does not seem right based on my experience. Rate limiting applied per Live Activity instance Good to know that it is per channel. I have not seen many concurrent channel updates at this time so not sure about this. The APNs server itself doesn't typically hard-limit but the receiving device's OS heavily throttles silent background updates based on a dynamic budget. My concern is more on the server API side than on the device throttling which is something that is not in our control.

Based on the logs and metrics, it seems that the effective rate might be 4 updates per min per channel. Can you confirm if the rate limiting is per channel or overall at API level per app bundle id?

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).

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 | ---

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.