Only changes we could attribute to a canonical X (Twitter) service appear here. An offering whose name did not map onto the catalogue confidently enough is still in the combined log on the main change page, because a wrong mapping would put a rate under the wrong platform, which is worse than leaving it unattributed.
Which X (Twitter) prices moved most in the last 7 days?
Ranked by the size of the percentage move. Only re-pricings above the 2% threshold are recorded as events.
Data captured from 53 panelsCatalogue diff log
The 25 largest X (Twitter) price moves recorded in the last 7 days, ranked by percentage change
#
Service
Panel
Old rate
New rate
Change / 1k
Change
Recorded
1
X (Twitter) RepostsTwitter Real Retweets ›› { Start : Instant } | { speed : 50K/D} | {30 Days Refill } | 🏵 ♻️
What X (Twitter) services are new to the catalogue?
Offerings that appeared in a panel’s catalogue after we had already read it at least once. A panel’s first read is a baseline, not a change, and is left out.
X (Twitter) offerings recorded for the first time in the last 7 days
Service
Panel
Platform
First rate seen
Recorded
X (Twitter) Likes🔥💎 Twitter Likes [Real - Premium Verified Accounts]
How many X (Twitter) prices have changed recently?
4,820 changes to X (Twitter) offerings in the last 7 days: 2,741 re-pricings above the 2% threshold, 1,736 recorded for the first time and 343 no longer listed. Those counts come from the diff between consecutive catalogue reads of the same panels, so they cover the panels we have synced rather than the whole market.
Does a cheaper X (Twitter) rate mean a better deal?
Not on its own. Delivery geography moves X (Twitter) prices far more than any quality label does, and a rate that drops sharply is quite often a change in what is being delivered rather than a discount on the same delivery. The change log tells you a number moved and by how much; the service page tells you what the number is for, including whether the offering carries a refill guarantee and which geography it targets.
Why is this page separate from the main change log?
Because a buyer working on X (Twitter) has no use for a re-pricing on an unrelated platform, and a single undifferentiated log makes the X (Twitter) rows harder to find the more panels we sync. The rows here are the same rows, filtered to services that map onto the X (Twitter) catalogue; the combined log and the downloadable dataset both live on the main change page.