This log covers the panels whose catalogues we have actually read, not the whole index. 67 of 150 tracked panels contributed a change in this window. A panel that has never been synced produces no events at all, which is a fact about our coverage rather than about that panel’s prices.
Which SMM panel prices moved most in the last 7 days?
Ranked by the size of the percentage move. Only re-pricings above the 2% threshold appear here, and a rise is shown as a warning because this index is written for the buyer.
Data captured from 67 panelsCatalogue diff log
The 25 largest SMM panel price moves recorded in the last 7 days, ranked by percentage change
#
Service
Panel
Old rate
New rate
Change / 1k
Change
Recorded
1
Instagram Broadcast Channel MembersInstagram - Channel Members | 🇦🇿 Azerbaijan 🇦🇿 | 👤 Real Profiles | 💧 Non Drop | 🚀 Speed 1M Per Day | ⛔ No Refill
The same window ranked by dollars per 1,000 rather than by percentage. Rates in this market span four orders of magnitude, so the two rankings are usually about entirely different services: a 60% move on a $0.0008 view is a rounding error on an invoice, and a 4% move on a $24 geo-targeted follower row is not.
The 10 largest SMM panel price moves recorded in the last 7 days, ranked by absolute change per 1,000
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 rather than a change, so it is left out here and reported in the summary above as coverage.
SMM panel offerings recorded for the first time in the last 7 days, newest first
Service
Panel
Platform
First rate seen
Recorded
Instagram LikesInstagram Likes [ 🇧🇷 Brazil ] [ Max 10K ] | 100% Brazilian Accounts With Posts | Cancel Enable | Low Drop | 30 Days ♻️ | Insant Start | Day 10K 🚀
Showing 25 of 24,086. The full set is in the CSV and JSON exports.
What is no longer listed?
Offerings we held that a panel stopped returning. The row is deactivated rather than deleted, because the price history hanging off it is still true — the rate shown is the last one we ever saw.
SMM panel offerings withdrawn in the last 7 days, newest first
Service
Panel
Platform
Last rate held
Recorded
Instagram CommentsInstagram Random Positive Emoji Comment 💎💪🔥🤲😘💞💐🏵️😍🤎💜💙💓💋🫂🤩🥰😘😚🤯❤️ (Real, Start Instant, Speed: 10-20K/Day, No Refill)
Showing 25 of 3,230. The full set is in the CSV and JSON exports above.
Which platforms saw the most change?
Changes attributed to a canonical service, so a platform's count is what its own change page renders. 27 of 29 have enough recorded to be worth a page of their own; the rest are shown here and left unlinked until they do.
The same window, day by day. Days with nothing recorded are absent rather than shown as zero: a zero row would claim we looked and found nothing, and a sync schedule this lumpy does not support that claim.
SMM panel catalogue changes by day over the last 7 days
Day (UTC)
Changes
Price moves
First recorded
No longer listed
Share of the window
2,401
2,339
17
45
1,967
1,281
219
467
2,132
1,271
417
444
14,615
14,081
278
256
2,483
1,749
312
422
26,189
3,708
21,960
521
15,376
14,233
521
622
1,721
906
362
453
How to read this change log
Where do these changes come from?
From a diff. Each time we sync a panel we compare the catalogue it returns against the one we already held for it, offering by offering, and write a row for every difference: a rate that moved, an offering we had never seen before, and one we held that the panel stopped returning. Nothing on this page is estimated, modelled or backfilled — if a change is listed here, two catalogue reads of the same panel disagreed, and the date shown is the date of the second one.
Why does a price move have to clear a threshold?
A rate that moves by less than 2% is recorded as the new price but not as an event. Panels re-derive their rates from upstream providers constantly and fractions of a cent per 1,000 wander on their own, so logging every one of them would bury the moves that matter under noise a buyer can never act on. The 2% floor is in the sync code, not in an editor’s judgement, and it applies identically to rises and to falls.
What does "first recorded" mean — did the panel just add it?
Not necessarily, and the wording is deliberate. An addition here is an offering that appeared in a panel’s catalogue after we had already read that catalogue at least once. A panel’s very first read is a baseline rather than a change — every offering in it is new to us, not to the market — so first reads are left out of every count and table on this page and reported separately, as coverage. That is why the numbers here are small next to the size of the catalogues we hold.
Why is a price rise coloured as a warning and a cut as good?
Because this index is written for the buyer, not the seller. A cut is a lower price for the same thing and a rise is not, so the colour follows the reader’s interest. It is worth adding the caveat the colour cannot carry: on the cheapest tier of any service, a price cut is quite often a change in what is being delivered rather than a discount on the same delivery.
Can I reuse this data?
Yes, under CC BY 4.0, with attribution to PanelCompare and a link. The full change log for this window is downloadable as CSV and as JSON at the top of this page, and both carry the licence in an HTTP Link header so a downloaded file arrives with its terms attached. We would rather the movements in this market were checkable than proprietary.
The export covers the last 5 days of the log. Every day of the log is also its own file, /data/price-changes/YYYY-MM-DD.csv. Prices themselves, with the daily median and quartile spread for every service, are on the price index; the scoring behind the panel rankings is set out term by term on methodology.