How signals delivers Reddit upvotes (our source, timing, and anti-fuzzing protocol)
A transparent walkthrough of how Signals sources accounts, paces velocity, and survives Reddit's anti-manipulation sweeps on a paid upvote drop.
A Reddit upvote drop only matters if the votes survive Reddit's purge window, weight at full leverage through Contributor Quality Score scaling, and land inside the 12.5-hour decay envelope where the post still has rank to gain. Most paid upvote services miss on at least two of those three. Our delivery protocol is built around them, and we publish it because operators evaluating a buy Reddit upvotes order should know what they are paying for before the link goes into the dashboard - not after the post stalls.
This post is the transparent walkthrough we owe buyers: where the upvote accounts come from, how the velocity is paced against Reddit's streaming detector, what the anti-fuzzing window looks like in practice, and the refund policy when a vote gets purged. Signals runs an aged Reddit account marketplace plus an editorial network for AI brand mentions across Reddit, Quora, Product Hunt, and Threads, and we have shipped tens of thousands of upvote drops across r/SaaS, r/entrepreneur, r/CryptoCurrency, r/IndieDev, and the larger creator subs since 2017. The protocol below is what those campaigns run on.
Where do the upvote accounts come from?
The accounts on our network are aged for 6+ months minimum, run by real people, and used for normal commenting and posting in between vote orders. We do not lease browser farms, and we do not spin fresh accounts on demand for cheap drops. Account age, organic comment karma, subreddit diversity, and consistent IP residency are the four signals Reddit uses inside its Contributor Quality Score tiers (Lowest, Low, Moderate, High, Highest), and a vote from a Lowest-tier account weights so close to zero that the post sees no rank lift even on a clean drop. Our delivery network is concentrated in the Moderate-and-above tiers, with separate pools for NSFW and crypto subs because the residency and history requirements differ. The reason most cheap services fail is single-axis: they have aged accounts but no diversity, or they have diversity but no posting history. Reddit weights the composite, not any one signal.
How is the velocity protocol shaped to survive the streaming detector?
We pace votes to follow the post's natural rising curve, not a flat per-minute schedule. Reddit's anti-manipulation system runs as a streaming pipeline, not an hourly batch - Derek Hsieh's Kafka Summit 2021 talk confirmed Reddit reduced detection latency from hours to minutes by moving off Airflow and onto kSQL, and the public position has tightened further since. The pattern that gets caught is regular: 5 votes per minute, every minute, for 30 minutes. The pattern that survives is irregular and front-loaded against organic upvote distribution - heavier in the first 5 minutes, tapering through minute 60, sparse from minute 60 onward. Our protocol shapes against the curve that the post is already drawing on Rising; the orchestration layer reads the post's vote counter every 30–60 seconds and adjusts the next-window dispatch. A blast curve trips the detector inside its own latency window. A drip curve riding the natural rise is statistically indistinguishable from organic activity. The deeper mechanics are in our drip vs blast protocol.
What does the anti-fuzzing window look like in practice?
Vote fuzzing is intentional anti-bot armor on Reddit's display layer, not the ranking layer - the Reddiquette page confirms displayed scores are scrambled so observers cannot reverse-engineer vote outcomes. The internal hot-sort uses unfuzzed score weighted by voter CQS, and that is the number that decides rank. What this means for a buyer watching the post: the visible "+47, +52, +49" oscillation is noise, not a problem. The real signal is whether the post crests Rising inside minute 30 and reaches Hot inside minute 60 to 75 in a niche subreddit. We report on position, not displayed votes, because the displayed votes are deliberately broken as a measurement surface. The 12.5-hour decay constant in the open-source clux/decay reference is the second window - 45,000 seconds is the time after which a post needs 10× more votes to hold the same rank. Every retained vote inside that window applies at full leverage; outside it, the leverage has decayed by 90%+.
First-hour retention rate on our Moderate-and-above CQS tier, measured against Reddit's vote-integrity sweeps after each campaign closes.
SourceTime constant after which a post needs 10× more votes to hold the same rank. The window where every retained vote applies at full leverage.
SourceReddit's time-to-detection on coordinated voting after the kSQL streaming migration. Down from hours under the prior Airflow architecture.
SourceThe CQS classification (Lowest, Low, Moderate, High, Highest) that scales each account's vote weight inside Reddit's hot-sort.
SourceHow do you order, and what does the dashboard show?
The order flow is three steps and the post URL is the only required input. You paste the link, pick a tier and a vote count, and the dashboard shows a planned dispatch window with a per-minute distribution graph. Once delivery starts (typically within 5–15 minutes for the Moderate tier and 15–60 minutes for the High tier, longer if the queue is heavy on a launch day), the dashboard tracks Rising rank, Hot rank, displayed-vote movement, and a retention estimate that reconciles dispatched votes against post-purge displayed counts. We log the campaign's source-account distribution at the tier level (not at account-id level, for obvious operational reasons) so buyers can see the CQS profile that ran on their thread. The dashboard also surfaces the four-row scorecard from our campaign ROI template - position lift, UTM-tagged outbound traffic from the post, signup attribution, and SERP movement on the target query - because the order page is not the audit; the 30-day window after the campaign is.
How do tiers compare on price, retention, and where they fit?
Three tiers, three operator profiles. The cheap tier exists for low-stakes engagement on a small post; it is not the right purchase for a launch day or a head-term ranking play. The middle tier is the bread-and-butter SaaS launch and creator-promo tier. The premium tier is for thread targets with active moderator scrutiny or competitive head-term keywords where retention is the entire game.
| Tier | Account profile | Typical retention (first 60 min) | Effective $/vote | Best for |
|---|---|---|---|---|
| Standard | Aged 6–18 months, Moderate CQS, mixed activity | 70–85% | $0.10–$0.18 | Niche-sub launches, low-traffic posts, comment upvotes |
| Quality (drip) | Aged 1–3 years, High CQS, real comment history | 85–95% | $0.20–$0.45 | SaaS and creator launches, r/SaaS / r/entrepreneur, AMA seeding |
| Premium (slow) | Aged 3+ years, Highest CQS, organic posting | 90–97% | $0.55–$1.20 | Head-term ranking plays, contested subs, thread targets with mod vote-policing |
A campaign that mis-tiers its purchase fails on the ROI denominator: a $0.05/vote cheap order on a launch-day thread typically retains 5–15% after CQS scaling and the streaming sweep, putting true cost-per-effective-vote at $0.30–$0.80 - more expensive than the Quality tier at retention. Pricing in detail lives in our Reddit upvote cost breakdown.
What is the refund policy when a vote gets purged?
We refund the difference when first-hour retention falls below the tier's stated floor. Standard floor is 70%; Quality floor is 85%; Premium floor is 90%. We measure retention against displayed vote count one hour after dispatch close, with a tolerance band that accounts for vote fuzzing on the display layer (typically ±5% on small samples). If the post's actual displayed vote count came in below the floor adjusted for natural fuzzing, the gap is credited to the buyer's account or refunded to source. We do not refund for buyer-side errors: thread deletion, post removal by AutoMod or moderators (which is a content-side problem, not a vote-side problem), URL changes after dispatch, or an order placed against a thread that already crossed the spam-filter threshold before delivery started. We also do not refund when the post stalls because the content was wrong for the subreddit - upvote velocity does not fix a launch post that the community would have voted down on its own. The full operator framing is in our paid vs organic velocity decision tree.
What should you not order from Signals?
We turn down orders that are unlikely to land regardless of delivery quality, and orders that fall outside Reddit's stated vote manipulation policy on a face read. The honest list, by category: deletion drops on someone else's negative thread (use a comment strategy, not a vote campaign); upvotes inside r/AskReddit, r/news, and the largest defaults where mod-side vote policing is constant and CQS-weighted vote leverage is low; thread targets where the OP is already clearly losing the room at minute 10 (no velocity package fixes content fit); and brigading-style coordinated runs against a competitor. We are also cautious on creator subs in the early-week shadowban window (week 3 of a new account is a known shadowban inflection point and a paid drop in that window will land on a filtered post). The buyer who self-selects out of those orders gets a higher hit rate, and the buyer who tries to push a low-fit campaign through anyway is the one who writes a refund-request email five days later. The deeper bot upvotes vs real upvotes test covers the failure modes in detail.
Frequently asked questions
How does a Reddit upvote service actually work end to end?
The buyer submits a Reddit URL and a target vote count. The service dispatches votes from a pool of aged accounts, paced over a window that is shaped to look like organic rising velocity. Reddit weights each vote by the voting account's Contributor Quality Score and runs continuous anti-manipulation sweeps (the streaming detector Derek Hsieh described at Kafka Summit). Votes that survive the sweep and weight at full leverage move the post's hot-sort score; votes from low-CQS accounts or detected coordinated runs get devalued or purged. The right service tier is the one whose retention rate matches the contested level of the subreddit you are posting in.
What does Signals do that distinguishes it from a $0.01-per-vote bot service?
Three things. The accounts are aged 6 months minimum, run by real people, and concentrated in Moderate-and-above CQS tiers - so the votes weight at full leverage, not zero. The pacing reads the post's actual Rising curve and shapes against it - so the dispatch pattern is irregular and survives Reddit's streaming detector. The reporting tracks position movement, not displayed vote count - so the buyer is reading the same signal Reddit uses internally, not the fuzzed display number. Cheap services miss on at least two of those three; the math on retention and effective cost-per-vote is in the tier table above.
Will buying upvotes from Signals get my account banned?
We deliver to a post URL, not an account. We do not log into the buyer's account, request credentials, or run any action through it - so there is no path from a Signals order to the buyer's account being suspended for vote manipulation. The risk that exists is on the post itself: if the thread crosses Reddit's filtering thresholds during delivery, the post can be removed or the OP can be flagged. The full risk framing is in our will buying Reddit upvotes get you banned breakdown. Operators with a clean OP account and a content-fit post inside a non-default subreddit see ban risk close to zero on the buyer-account side.
Why do you report position lift instead of displayed vote count?
Because Reddit deliberately scrambles displayed vote counts. The Reddiquette page confirms vote fuzzing is intentional anti-bot armor on the display layer. The internal hot-sort uses unfuzzed CQS-weighted score, and the visible position of the post on Rising and Hot is the only buyer-readable signal that tracks that internal score. A post sitting at +49 displayed votes can be ranked higher than a post sitting at +63 displayed votes if the CQS weighting differs. Position is the honest read; displayed votes are theater.
Does the move from r/all to r/popular change how upvote campaigns work?
Slightly, on the trending-feed side. Reddit's April 2 2026 changelog deprecated r/all on apps and modern web in favor of r/popular as the default trending feed - r/all still exists on old.reddit.com but it is no longer the cross-community ceiling for most users. For an upvote campaign, this means the second target after Rising and Hot is r/popular appearance, and r/popular filters NSFW and excludes some communities entirely (per the r/popular help page). NSFW and excluded-community posts cannot crest the cross-community feed regardless of velocity.
What is the refund policy if the campaign does not perform?
We refund the gap below each tier's stated retention floor (70% Standard, 85% Quality, 90% Premium) measured one hour after dispatch close, with a fuzzing tolerance band of ±5%. We do not refund for buyer-side errors - thread deletion, AutoMod removal, URL changes mid-dispatch, or content that the subreddit was always going to reject. The clean operating principle: we are accountable for the votes landing and weighting; the buyer is accountable for the post fitting the subreddit.
:::
The honest summary: a Reddit upvote campaign is an inputs problem and a content problem. We own the inputs - account quality, velocity shape, retention through CQS scaling and the streaming sweep. The buyer owns the content - whether the post belongs in the subreddit at all. When both sides do their job, the math compounds: position lift on launch day, indexed thread on Google in 7–14 days, and AI-citation pickup over the 30 days that follow. The full operator playbook lives in our Reddit marketing guide.
