How to Prevent Overnight Die-Offs on Your Cricket Farm

Temperature drops below 60°F at night account for 52% of reported overnight die-offs. The other causes, ammonia buildup, dehydration, disease, aren't mysterious either. They're predictable, they're detectable, and most of them are preventable once you know what you're watching for.

TL;DR

• Temperature drops below 60°F at night account for 52% of reported overnight die-offs
• Young nymphs have almost no thermal buffer, a drop from 88°F to 60°F in a poorly heated room can kill an entire bin of instars 1–3 in a single night
• Adult crickets can survive lower temperatures longer but still suffer significant mortality below 65°F
• Sub-lethal exposure (above 25 ppm) causes stress and reduces growth rates
• It tends to produce elevated overnight mortality, 50–200 dead per bin per night, without an obvious single cause
• The practical solution to overnight die-offs is a pre-departure checklist that takes 10 minutes and eliminates the most common causes
• This takes 5–10 minutes across a 30-bin operation

The Three Primary Overnight Die-Off Causes

1.

• Temperature Crash (52% of events)

Crickets are cold-blooded.

• Young nymphs have almost no thermal buffer, a drop from 88°F to 60°F in a poorly heated room can kill an entire bin of instars 1–3 in a single night.
• Adult crickets can survive lower temperatures longer but still suffer significant mortality below 65°F.
• Ammonia Buildup (28% of events)

Cricket frass decomposes continuously.

• Sub-lethal exposure (above 25 ppm) causes stress and reduces growth rates.

The Three Primary Overnight Die-Off Causes

1. Temperature Crash (52% of events)

Crickets are cold-blooded. Young nymphs have almost no thermal buffer, a drop from 88°F to 60°F in a poorly heated room can kill an entire bin of instars 1–3 in a single night. Adult crickets can survive lower temperatures longer but still suffer significant mortality below 65°F.

The mechanism: at cold temperatures, crickets become immobile. They can't access water or food. Metabolic processes slow. Young crickets don't have the mass to survive extended cold exposure.

How to prevent it:

• Install a WiFi temperature sensor at bin level with a push alert set to 78°F (giving you a 15°F buffer before mortality zone)
• Add a backup heat source set 5°F below your primary thermostat setting
• Check your room's actual overnight low with a data-logging sensor before trusting your setup

2. Ammonia Buildup (28% of events)

Cricket frass decomposes continuously. In a poorly ventilated bin or room, ammonia levels climb. Sub-lethal exposure (above 25 ppm) causes stress and reduces growth rates. At higher concentrations, especially combined with warmth and humidity, it becomes lethal, sometimes overnight when a bin's frass load tips past a threshold.

Ammonia buildup doesn't cause the dramatic mass die-offs that temperature crashes do. It tends to produce elevated overnight mortality, 50–200 dead per bin per night, without an obvious single cause.

How to prevent it:

• Ensure your bin lids have adequate ventilation (mesh panels or cut-outs)
• Maintain at least 6 air changes per hour in your grow-out room
• Clean bins between batches, don't let frass accumulate beyond the grow-out cycle
• Don't overstock bins (overcrowding increases frass load per unit of space)

3. Dehydration (12% of events)

Overnight dehydration die-offs happen most often in low-humidity environments, in bins where the hydration source has run out, or in bins relying on fresh vegetables that dried out before morning.

Crickets can dehydrate relatively quickly at low humidity and high temperature, the combination most farms maintain for good FCR. A water gel container that ran dry in the afternoon can mean a bin of stressed crickets by morning.

How to prevent it:

• Check hydration sources during your last evening rounds before you leave
• Use water gel rather than fresh vegetables for bins you won't check overnight
• Monitor humidity at bin level, if it drops below 40% in your grow-out room, your hydration frequency needs to increase

Building Your Overnight Checklist

The practical solution to overnight die-offs is a pre-departure checklist that takes 10 minutes and eliminates the most common causes.

Before you leave each night:

1. Temperature sensor reading is within target range
2. Backup heat source is operational
3. Push alerts are enabled on your phone
4. All bin hydration sources are full (water gel topped up, fresh vegetables replaced)
5. Ventilation is unobstructed (check that bin lids haven't shifted, closing off ventilation cut-outs)
6. Any bins flagged with recent elevated mortality have been checked more thoroughly

This takes 5–10 minutes across a 30-bin operation. Compare that cost to the cost of discovering a temperature-crashed bin in the morning.

Step-by-Step: Setting Up Overnight Monitoring

Step 1: Install a WiFi temperature sensor at bin level. Not at ceiling. Not at the thermostat. At the height your bins sit. Place it in the coolest part of the room, usually near an exterior wall or floor vent.

Step 2: Set a low-temperature alert at 78°F. This gives you a response window before mortality risk increases.

Step 3: Test the alert system. Move the sensor to a cooler location (outside the room) and confirm you receive the alert on your phone. Do this before you rely on it for real overnight protection.

Step 4: Add a backup heat source. A second space heater set to 80°F (5°F below your primary at 85°F) won't interfere with your primary heating but will catch the primary system failure before it drops below danger territory.

Step 5: Configure a humidity alert. Set your low humidity alert at 40% RH. Below that, dehydration risk increases in adult and juvenile bins.

Step 6: Log overnight events. When an alert fires, log what happened: time, temperature reading, which bins were affected, what corrective action you took. This data over time reveals your room's thermal pattern and lets you anticipate problems before they happen.

How to Monitor Your Cricket Farm at Night Without Being There

CricketOps integrates with IoT sensors and sends push notifications to your phone when temperature or humidity goes outside your configured thresholds. You don't need to be physically present, you need a phone on your nightstand with notifications enabled.

The alert tells you: which sensor fired, what the reading was, and which bins are in that zone. You can check the live feed remotely and decide whether to go in or whether the backup heat source has already corrected the problem.

For multi-employee farms: configure alerts to go to multiple phones. A 2 a.m. problem shouldn't depend on a single person being awake.

FAQ

Why do my crickets keep dying overnight?

The three most likely causes are overnight temperature drops (responsible for 52% of events), ammonia buildup from poor ventilation, and dehydration from empty hydration sources. Install a WiFi temperature sensor with push alerts to diagnose temperature crashes. Check ammonia by ensuring your room has adequate air exchange and bins have ventilated lids. Check hydration sources every evening before leaving.

What temperature causes crickets to die?

Acheta domesticus mortality increases significantly below 65°F. A sustained drop below 60°F for more than 2–3 hours can kill young nymphs (instars 1–3) at rates above 80%. Adult crickets are more resilient but still suffer elevated mortality below 65°F sustained overnight. Set your low-temperature alert at 78°F to give yourself a response window before mortality risk becomes critical.

How can I monitor my cricket farm at night without being there?

Install WiFi-connected temperature and humidity sensors at bin level in each grow-out zone. Connect them to a platform with push notification capability. In CricketOps, sensor data is linked to bin records and alerts are sent to your phone (and your team's phones) when conditions go outside your configured thresholds. 85% of CricketOps users access the platform via mobile at least once daily, most of those interactions are alert responses.

How does CricketOps help track the metrics described in this article?

CricketOps provides bin-level logging for the variables that drive production outcomes -- feed inputs, environmental conditions, mortality events, and harvest results. Rather than maintaining these records in separate spreadsheets, you can view performance trends across bins and over time to identify which operational variables correlate with better outcomes in your specific facility.

Where can I find industry benchmarks to compare my operation's performance?

The North American Coalition for Insect Agriculture (NACIA) publishes periodic industry reports with production benchmarks. University extension programs in agricultural states, including the University of Georgia and University of Florida IFAS, occasionally publish insect farming production data. Industry conferences hosted by the Entomological Society of America and the Insects to Feed the World symposium series are additional sources of peer benchmarking data.

What is the biggest operational mistake cricket farmers make in their first year?

Expanding bin count before achieving consistent FCR and mortality targets in existing bins is the most common and costly first-year mistake. At 5-10 bins, problems are manageable. At 30-50 bins, the same proportional problems represent much larger financial losses. Most experienced cricket farmers recommend holding expansion until you have three consecutive production cycles hitting your FCR and mortality targets.

Sources

• Food and Agriculture Organization of the United Nations (FAO) -- Edible Insects: Future Prospects for Food and Feed Security
• North American Coalition for Insect Agriculture (NACIA)
• Entomological Society of America
• University of Georgia Cooperative Extension
• Journal of Insects as Food and Feed (Wageningen Academic Publishers)

Get Started with CricketOps

The practices covered in this article are easier to apply consistently when they are supported by organized production data. CricketOps gives cricket farmers the tools to track what matters -- by bin, by batch, and over time. Start your next production cycle in CricketOps and see how organized data changes the way you manage your operation.