Votekampagne
Votekampagne
Request an order

Buy Hacker News Upvotes

Buy Hacker News Upvotes. Real participants, unique IPs, pacing that matches the contest window.

Hacker News isn't built like a contest page with a vote button bolted onto a form; it's a ranking site where every submission competes against a formula that weighs raw points against how much time has passed since posting, read by a small, highly attentive community that finds new submissions within minutes of them going up. Anyone who wants to buy hacker news upvotes should know upfront that this is the least forgiving corner of any platform on this site: nothing about it works quietly.

Moderation here isn't a hidden backend process. Users flag submissions they find suspicious directly and in public, sometimes right in the comment thread itself, and the site's own moderators can intervene by hand — sinking a story's rank or pulling it from the front page entirely, often without explaining why. A cluster of upvotes landing in an unusual pattern is exactly the kind of thing that gets noticed and discussed here, not the kind of thing that slips past unremarked the way it might on a larger platform.

A single account can cast one upvote per submission and nothing more — there's no weighting by follower count, no way to vote twice by revisiting the page, and no downvote available on stories at all, only on comments, and only for accounts with enough history on the site to unlock it. What happens after that vote is cast, and how the ranking formula treats it, is what the next section covers.

Request an order

Contest link, number of votes, deadline. We reply with price and timing.

Start request

How Hacker News Actually Ranks a Submission

The front page isn't a raw leaderboard of vote counts. It's ordered by a formula that weighs a story's points against its age, so a submission loses ranking power steadily as it gets older even if nobody has flagged or downvoted it at all. A story with fewer points but far less time on the site can outrank an older one sitting on a higher total, purely because of how that decay works.

Flags subtract from that calculation, and enough of them can push a submission off the front page or gray it out entirely, regardless of how many upvotes it's accumulated. New accounts and brand-new domains get treated more cautiously by the system than an account with a long, ordinary history posting a link from a source that's shown up before, which means the exact same vote pattern can land very differently depending on who's submitting and what they're submitting.

None of this is published as an exact formula anyone can plug numbers into — the site deliberately doesn't spell out its own ranking mechanics in detail, partly so the calculation stays harder to game precisely. What's publicly known comes from the community's own observation over years of watching submissions rise and fall, not from any official specification.

How many flags it takes to sink a submission scales with the points it has already earned, so a story sitting high on the front page needs proportionally more flags to fall than a fresh submission with only a handful of points behind it. A moderator can still act by hand regardless of that ratio, but the automatic side of flagging weighs a story's own score before deciding how much a single flag should count against it.

The ranking formula also tracks which domain a submission's link comes from, and it throttles multiple simultaneously rising submissions that share the same source rather than letting a single site occupy several top slots at once. A submission from a domain that's shown up on the front page before behaves differently in that throttle than the first-ever link from a brand-new domain, even when both carry an identical vote pattern.

A submission that gets almost no attention on its first pass through isn't necessarily finished. Hacker News keeps a separate pool of overlooked stories and resurfaces individual ones to new readers well after the original submission has faded off the front page, independent of whatever points it originally collected. A second run through that pool has nothing to do with the votes gathered the first time around.

The site's own software also looks for voting rings: clusters of accounts that consistently upvote each other's submissions and comments in a pattern distinct from ordinary reading behavior. Accounts caught in that pattern can have their votes discounted automatically, separate from anything a human moderator does by hand and separate from the flag count a story has publicly received. This runs quietly in the background rather than through any visible flag a reader can see on the page.

How Delivery Is Paced on a Platform That Watches Closely

Delivery here means real accounts with an ordinary posting and commenting history, each casting one upvote on the submission, spread out rather than arriving in a tight cluster. A submission that jumps by a large amount within a few minutes is the single most visible pattern on this platform, because regular users refresh new submissions constantly and the jump shows up against a backdrop they already know well.

Pacing also has to account for the age-based decay built into the ranking formula itself — votes that arrive too late relative to a submission's age don't move its position the way the same votes would have earlier, so delivery is planned around the story's actual age on the site rather than sent as a flat, unconditional batch regardless of timing.

Because throttling applies per domain rather than per submission, an order tied to a link whose domain already has other rising stories competing for the front page gets paced with that shared limit in mind, not treated as if the domain slot were unlimited. Timing also has to account for which side of the front-page cutoff a submission is likely to sit on relative to its current age, not just its raw point total at the moment the order goes out.

Where This Service Has to Stop

We can't stop a moderator from sinking a submission by hand, and we won't try to work around a flag or a manual review the site's own team puts in place — that's the exact mechanism the platform relies on, and it exists specifically to catch coordinated activity. If a submission gets flagged or killed, that decision belongs to Hacker News, not to anyone who voted on it.

This also doesn't extend to submissions from political campaigns or government accounts, and it won't touch a discussion the community has already flagged as off-topic for the site. Hacker News is smaller and more self-policing than most platforms on this list, and that's the honest reason this particular service comes with more limits attached than most.

We can't influence which submissions the second-chance pool picks to resurface, since that selection runs independently of any vote count or order placed against a story. We also don't attempt to build the kind of coordinated pattern the site's own ring detection is built to catch; asking for that means asking us to work against the exact mechanism this service depends on staying credible.

The organiser's rules decide

Most public voting contests publish rules that limit votes per account, per person or per IP address, and many prohibit automated or fraudulent voting outright. Some organisers state that votes identified as manipulative are excluded from the count without notice, and that a participant who orders paid votes for a contest can be disqualified. Read the rules before you buy votes for any poll or contest, because the organiser can remove an entry and nobody can prevent that.

promosis.com ifann.net kadi.com beastgames.com

Why ordinary pacing holds up

Contest platforms watch for clusters: hundreds of votes from one IP address in minutes, or a spike that no real audience would produce. Many organisers also hide live totals until voting closes, which makes a sudden spike easier to spot afterwards. Votes for a contest or poll that arrive at a steady pace, from varied sources, across the whole voting window look like the rest of the traffic the platform already receives.

promosis.com brakto.com ecommercefastlane.com reddit.com producthunt.com

Where the law actually stands

In the United States, legal summaries describe buying votes for a commercial online contest as not inherently illegal, while noting that bots or fake accounts can cross into deceptive-practice territory. In Australia, no specific criminal offence is described for buying contest votes, though the organiser's terms still decide. In the United Kingdom, the Advertising Standards Authority warns promoters about prize contests under the Gambling Act 2005, and in Canada the Competition Act sets disclosure duties for promotional contests. We refuse orders for any public ballot or election.

legitell.com asa.org.uk competition-bureau.canada.ca

What the refund covers

If we cannot deliver the votes you ordered for your poll or contest, the order is refunded in full. If delivery misses the deadline you set, you can claim a refund instead of the order. The guarantee never covers a result: if the organiser disqualifies your entry or excludes votes from the count, that decision is theirs and no refund or replacement changes it.

broadcastlift.com smmlaboratory.com

Questions

A voting ring is a cluster of accounts that consistently upvote the same people's submissions and comments back and forth. Hacker News runs automatic detection for that exact pattern and can discount the votes involved, separate from any manual flag or moderator action on the story itself.

Sometimes, yes. A sudden jump in points relative to a submission's age is visible on the site itself, and regular users who track new submissions closely do occasionally comment on it directly in the thread. This is a far more public and attentive community than most platforms handle contests through.

Only on comments, and only from accounts that have built up enough history on the site to unlock that option — stories themselves can't be downvoted at all, only flagged. A flagged story is handled through a completely separate mechanism from the vote count.

Yes, at any time and without needing to explain the reasoning. A high point total doesn't protect a submission from being sunk or removed if a moderator decides it should be, and that decision sits entirely with the site's team.

No. Accounts with little or no history are generally treated more cautiously by the ranking system than an account with a long, ordinary posting record, which means the same vote pattern can affect a new account's submission differently than an established one's.

Because the ranking formula weighs a submission's points against its age, not just the raw count. Votes that land early in a submission's life move its position more than the same number arriving after it's already lost most of its ranking power to time.

Last reviewed: