Thank you all for continuing to engage here. I know this thread has gotten tense, and I want to acknowledge the frustration some of you are feeling about both the changes and our communication around them. You’re running real businesses on top of our platform, and you’re right to push for clarity.
Several of you have also raised concerns about the timeline between the announcement in December and the original enforcement date. While we conducted extensive internal due diligence to ensure these changes would not cause widespread breakage, it’s clear that the timeframe we provided hasn’t been sufficient for you to fully digest the changes, ask questions, and, where necessary, speak with us directly.
To support a smoother rollout and give you additional time to prepare, we are moving the start date of the phased enforcement for the new point-based rate limits to Mar 2, 2026.
Our goal in doing this is not to reopen the core design or to suggest that we lack confidence in the underlying approach. It’s to:
-
Give you more space to understand what this means for your specific apps
-
Allow time for 1:1 conversations where a public thread isn’t the right place to go into detail
-
Help ensure the transition is as smooth and predictable as possible for you and your customers
Several questions in this thread have requested very specific details about the data, models, and thresholds underlying the new rate limits and tiering. I want to be upfront about the tension we’re working within:
-
We do want to give you enough information to operate and plan with confidence.
-
We are constrained in what we can publish in a public forum about our internal modeling, data sets, and the way we allocate shared capacity.
Because of that second point, there are some things we’re not able to do in this thread, given security, abuse, and fairness constraints:
-
We’re not going to publish the full underlying data sets or models used to set tiers and limits.
-
We’re not going to share exact internal thresholds or “guarantees” around how other apps will behave under specific scenarios.
-
We’re not going to turn those internals into public, customer-facing SLAs.
That said, we are committed to partnering with you one‑on‑one: we can walk through how these limits apply to your specific app, review your traffic patterns, and discuss options or adjustments through the support and engagement channels we’ve outlined.
What we have done, and will continue to do:
-
Ensure that these changes are guided by clear governance principles, including:
-
Protecting customers from “noisy neighbor” patterns, where one customer can degrade another customer’s experience
-
Providing enough headroom in Tier 1’s global pool for normal organic growth for the vast majority of apps, including free apps
-
Proactively moving apps whose traffic profiles indicate they and their customers are better served by per-tenant limits into Tier 2
-
-
Offer qualitative guidance about usage patterns that are likely to work well within each tier
-
Engage directly about your specific app:
-
If you’re concerned that your app’s limits or tiering aren’t appropriate given your real traffic, please raise a ticket here: Increase Marketplace App Rate limits.
-
Our team will review your actual profile, and in more complex cases, we’re happy to schedule a call to walk through your situation in more detail than is possible here.
-
The move to Mar 2, 2026 is intended to provide sufficient time for these conversations to occur and, where applicable, to make targeted adjustments based on your actual usage patterns.
We acknowledge that we could have done better in the amount of detail we provided upfront and the time available for you to respond. We’ll apply this feedback to improve how we design and communicate future changes, particularly in areas such as earlier examples, concrete guidance, and giving you greater confidence and predictability as changes roll out.
To make sure we can give you the depth you’re asking for, we’ll handle app‑specific questions via support tickets and reserve this thread for net-new, broadly applicable themes. I’ll keep monitoring for new themes we haven’t addressed, but:
-
For questions about specific apps, please open a support ticket so we can investigate your case in more detail.
-
For requests for internal models, datasets, or exact thresholds, the answer will remain that we will not publish those.
We do appreciate the time and thought you’ve put into this feedback, even when it’s uncomfortable to read, and we’re committed to making this transition as smooth as possible for you and your customers.
— Alan