Help Center

Yes. Mining Rig Rentals supports large mining farms, including farms with many ASICs, GPU rigs, or other mining devices.

However, large farms require more planning than a single miner or small rig. How you group your miners affects rental reliability, worker visibility, hashrate reporting, reconnect behavior, troubleshooting, and support review.

For large farms, we usually recommend splitting miners across multiple rig listings instead of placing every miner into one very large rig.

Should I list miners individually or group them?

You can list mining devices in several ways:

For most large farms, the best approach is to create multiple grouped rigs instead of one huge rig.

Why not use one massive rig?

A single very large rig may look simple, but it creates operational problems.

Large single-rig listings can make it harder to:

• identify which miner is failing,
• isolate rejected or stale shares,
• troubleshoot disconnects,
• maintain accurate advertised hashrate,
• handle partial hardware failures,
• take part of the farm offline for maintenance,
• avoid large rental-impacting outages,
• keep worker data readable,
• manage pool reconnect events cleanly.

If one miner fails inside a 20-miner rig, the impact is small and easier to understand. If several miners fail inside a 500-miner rig, the problem is harder to isolate and may affect a much larger rental.

Recommended farm layout

For large farms, we recommend splitting miners into practical groups.

A good grouping strategy depends on your hardware, network, and management system, but common options include grouping by:

• physical rack,
• electrical circuit,
• network switch,
• ASIC model,
• algorithm,
• hashrate size,
• cooling zone,
• management controller,
• physical location,
• operational reliability.

Try to group miners in a way that makes troubleshooting obvious.

For example, if a switch, PDU, or cooling zone fails, you should be able to quickly identify which rig listings are affected.

Suggested rig sizing

There is no single perfect rig size for every farm, but smaller grouped rigs are usually easier to operate than one massive rig.

As a practical guideline:

• avoid placing an entire large farm into one rig listing,
• keep rig groups small enough that worker issues are easy to identify,
• avoid grouping unstable miners with stable miners,
• keep similar hardware together when possible,
• keep advertised hashrate realistic for each group,
• leave operational margin for miner restarts, maintenance, and normal variance.

For very large farms, contact support before connecting a large number of miners.

Connection limits

Mining Rig Rentals has connection limits to protect platform stability and rental routing.

Large farms may be subject to limits based on:

• number of connections per rig,
• number of connections per IP address,
• number of connections per server,
• server capacity,
• reconnect behavior,
• active rentals,
• worker count,
• mining protocol behavior.

As a general rule, avoid connecting more than 250 miners to a single rig or single IP address per server unless support has reviewed the setup.

There may be a hard upper limit of approximately 500 connections per rig, per IP, per server, but farms should not plan around the hard limit as the normal operating target. The practical recommended limit is lower because reconnects, pool switches, and temporary connection states can briefly increase load or prevent new connections from opening cleanly.

If you need capacity beyond that, split the farm across multiple rigs and servers, or contact support.

Use multiple Mining Rig Rentals servers when needed

Large farms may need to spread connections across more than one Mining Rig Rentals server.

This can help with:

• connection capacity,
• geographic routing,
• redundancy,
• lower server-side concentration,
• smoother reconnect behavior,
• avoiding too many miners behind one endpoint.

When selecting servers, use locations that make sense for your farm’s network path and the renters you expect to serve.

Do not randomly spread miners across distant servers without testing latency and stale share rates.

Reconnect behavior with large farms

When a rental changes pools or a rig is switched, miners may need to reconnect or update their mining target.

With a small rig, this is usually straightforward. With hundreds of miners, reconnect behavior matters much more.

Large farms should verify that miners:

• reconnect cleanly,
• do not enter reconnect loops,
• do not fail over away from Mining Rig Rentals during rentals,
• do not overload a single server during reconnect events,
• return to the correct Mining Rig Rentals endpoint after restart,
• submit accepted shares after reconnecting.

Some ASIC firmware does not handle stratum reconnect behavior correctly. If that happens, you may need to use the assigned or direct rig port shown in the rig connection information.

Worker visibility

Worker visibility is important for large farms.

Before listing a large grouped rig, confirm that the Workers tab shows useful worker information.

You should be able to identify:

• which miners are online,
• which miners are offline,
• which miners have low hashrate,
• which miners are submitting rejected shares,
• which miners are submitting stale shares,
• which miners are reconnecting,
• which miners are using unexpected difficulty.

If your farm uses a proxy or aggregator that hides many physical miners behind one worker connection, troubleshooting may become harder. That setup may still work, but you are responsible for monitoring the underlying miners.

Avoid hiding unstable miners inside a large listing

Do not combine unreliable miners with stable miners just to increase the displayed hashrate.

If some miners are unstable, keep them out of rental listings until they are fixed.

Common instability signs include:

• frequent disconnects,
• high rejected shares,
• high stale shares,
• overheating,
• hashboard errors,
• PSU instability,
• firmware crashes,
• network drops,
• repeated failover events.

A large listing should represent stable, deliverable hashrate.

Advertised hashrate for large farms

Set the advertised hashrate based on the stable average hashrate delivered through Mining Rig Rentals.

Do not advertise the theoretical total hashrate from manufacturer specifications unless the farm actually delivers that value under normal operating conditions.

For large farms, account for:

• normal miner variance,
• dev fees where applicable,
• offline maintenance,
• thermal throttling,
• unstable hashboards,
• rejected shares,
• stale shares,
• firmware restarts,
• network interruptions,
• pool difficulty behavior.

It is better to advertise a realistic value that the farm can consistently deliver than to overstate performance and create rental disputes.

Testing before listing

Before making a large farm available for rent:

1. Connect a small group of miners first.
2. Confirm they appear correctly in Mining Rig Rentals.
3. Confirm accepted shares are increasing.
4. Confirm rejected and stale shares are low.
5. Confirm reconnect behavior works.
6. Add additional miners in controlled groups.
7. Watch server, IP, rig, and worker counts.
8. Confirm the Workers tab remains usable.
9. Test pool switching or rental behavior where appropriate.
10. Set advertised hashrate based on sustained performance.

Do not connect hundreds of miners for the first time and immediately list the farm for rent without testing.

When to contact support before listing

Contact Mining Rig Rentals support before listing if:

• you plan to connect hundreds of miners,
• you expect more than 250 miners from one IP to one server,
• you need to split a farm across multiple servers,
• your farm uses a proxy or aggregator,
• your ASIC firmware does not support normal reconnect behavior,
• you need help planning rig grouping,
• you want to discuss a private or dedicated rig server,
• you are listing resold or third-party hashrate,
• you are unsure how connection limits apply to your setup.

Support can help review the connection plan before it creates rental or routing issues.

Private rig servers

For very large farms, Mining Rig Rentals may be able to provide a private or dedicated rig server.

This is generally intended for farms with a large number of miners, such as 500 or more devices, or farms with special routing or connection requirements.

Private server availability may depend on capacity, location, and operational requirements. Contact support before assuming that a private server is available.

Information to provide support

When contacting support about a large farm, include:

• estimated number of miners,
• ASIC or GPU models,
• algorithm or algorithms,
• expected total hashrate,
• number of public IP addresses,
• farm location or region,
• preferred Mining Rig Rentals server region,
• whether miners support client.reconnect,
• whether you use a proxy or aggregator,
• expected number of rig listings,
• desired grouping plan,
• whether you need a private rig server.

The more detail you provide, the easier it is to recommend a stable setup.

Summary

Large mining farms are allowed on Mining Rig Rentals, but they should be planned carefully.

For most farms, multiple grouped rig listings are better than one massive rig. Keep groups manageable, test the setup before listing, monitor worker health, use realistic advertised hashrate, and contact support before connecting hundreds of miners.

A well-organized farm is easier to rent, easier to troubleshoot, and more reliable for renters.