My Varroa Treatment Did Not Work: What to Do Next

Treatment failures reported to state apiarists help build the national resistance surveillance network with actionable geographic data. If your post-treatment count remains high after a properly applied treatment, you're not just facing a beekeeping problem -- you're potentially holding information that matters to your region's resistance picture.

But first: you need to figure out what actually happened, because not every elevated post-treatment count is a resistance failure. There are several causes of post-treatment high counts, and the response differs depending on which one applies to you.

TL;DR

Treatment decisions should always be triggered by a mite count result, not a fixed calendar date
Different treatments have different temperature requirements, PHI restrictions, and brood penetration capabilities
Always run a post-treatment count 2-4 weeks after treatment ends to calculate efficacy
Efficacy below 80% warrants investigation -- possible resistance, application error, or reinfestation
Rotate treatment chemistry to prevent resistance buildup across successive cycles
VarroaVault logs treatment events, calculates efficacy, and flags when rotation is recommended

Step 1: Confirm You Have a Real Failure

Before concluding that your treatment failed, verify the count timing and method.

When did you count? A post-treatment count taken less than 21 days after an OA dribble application or less than 42 days after Apivar strip application may simply reflect the normal time lag before the full treatment effect is visible. Phoretic mites die quickly on contact with most treatments, but newly emerged mites from capped brood cells are not immediately exposed. Counting too soon produces a falsely elevated result.

Did you count from the right location? Brood nest bees carry more mites than foragers. Your sample should always come from frames in the brood nest area, not from outer frames or the entrance. A sample skewed toward forager-heavy areas will undercount.

Was the count method accurate? An alcohol wash of 300 bees provides roughly 95% confidence in your result. A sugar roll of the same sample provides only about 70% confidence. If your post-treatment count used a less accurate method, the elevated number may reflect method variability.

If you've ruled out these factors and your count remains above 1% at the appropriate post-treatment timepoint, you have a genuine treatment failure to investigate.

Step 2: Identify the Most Likely Cause

There are three primary causes of post-treatment elevated counts:

Application Error

Did the treatment get applied according to label directions?

For OA dribble: Was 50ml applied directly to the bee cluster? Was the colony confirmed broodless before dribbling? Dribbling onto a colony with significant capped brood dramatically reduces efficacy, because phoretic mites on adult bees are killed but mites in capped cells survive to re-emerge.

For Apivar: Were strips placed in the brood nest between frames of capped brood where bees contact the strips frequently? Were they left in for the full 42-56 days? Strips placed on the outer edges of the box where bee contact is minimal produce lower efficacy.

For MAQS or Formic Pro: Was temperature in the 50-79°F range throughout the treatment period? A heat event above the product's temperature maximum during treatment compromises efficacy.

Application errors are correctable. Identify what went wrong and reapply correctly before concluding you have a resistance problem.

Reinfestation

Reinfestation from neighboring untreated colonies is one of the most frequently overlooked causes of post-treatment elevated counts. Bees drift and rob between colonies. A heavily mite-infested hive in a neighboring apiary within 1-2 miles can rebuild mite loads in your treated colonies within weeks.

Signs of reinfestation rather than treatment failure:

Your post-treatment count dropped significantly right after treatment, then climbed back
Your colonies closest to the property boundary or nearest apiaries have the highest post-treatment counts
Multiple colonies that had different pre-treatment starting points all converge to a similar elevated post-treatment count

Reinfestation doesn't mean treatment failure -- it means your environment is actively contributing to mite reintroduction. The solution is more frequent post-treatment monitoring and possibly additional fall treatments.

Resistance

True resistance -- reduced susceptibility of the mite population to a specific active ingredient class -- is confirmed by:

Low treatment efficacy (below 80%) despite correct application
The pattern repeating across multiple treatment cycles with the same product
No evidence of reinfestation explaining the elevated counts
Other beekeepers in your area reporting similar efficacy loss with the same product

Resistance tends to develop when one product class is used repeatedly without rotation. Amitraz resistance and tau-fluvalinate resistance have been documented in US mite populations. OA resistance has not been confirmed in field populations, though lab studies suggest its potential.

Step 3: Choose Your Response

Based on your cause identification:

If application error: Correct the application method and retreat with the same product class if you're still within the labeled use window, or switch to a different product and retreat.

If reinfestation: Increase monitoring frequency. Consider a second fall treatment with a product class different from your first. If you know the neighboring operation and the relationship allows, communicate about coordinated treatment timing.

If resistance suspected: Switch product classes immediately. Do not retreat with the same active ingredient that produced the low-efficacy result. Move to a different class -- if you used amitraz, switch to formic acid or OA. Document the failure and consider reporting it to your state apiarist.

Step 4: The Second Treatment

After identifying the cause, you need to retreat. The retreatment product selection depends on the cause:

Application error: Same or different product based on your assessment and the current temperature and honey super conditions
Reinfestation: Second treatment with the same class is acceptable if the first worked initially; consider a class switch if you're also seeing resistance signals
Resistance: Different active ingredient class from the one that failed

For retreatment timing, if you're in September or October, an OA dribble on a confirmed broodless colony is often the most practical option -- it doesn't require warm temperatures (unlike formic acid), has 0-day PHI, and achieves high efficacy on broodless colonies.

The mite resistance management guide covers product rotation planning after a suspected resistance event. The how to evaluate varroa treatment efficacy guide covers the full efficacy calculation methodology.

Step 5: Document and Report

If you suspect resistance, document your failure carefully:

Pre-treatment count with date and method
Treatment product, application date, application method
Post-treatment count with date and method
Calculated efficacy percentage

Report this data to your state apiarist. Many state programs are actively tracking resistance patterns, and your data contributes to the geographic picture. Beekeepers who document and report failures help state programs identify regions where resistance is emerging -- which eventually benefits you through updated treatment guidance for your area.

VarroaVault's treatment failure response workflow triggers automatically when post-treatment efficacy falls below 90%. It prompts you through the cause identification steps, logs your response, and generates a resistance report document formatted for state apiarist submission if you determine reporting is warranted.

Frequently Asked Questions

What should I do if my varroa treatment did not reduce mite levels?

First, verify that your count was taken at the right time (at least 21-45 days after treatment depending on the product) and from the right location (brood nest bees). If timing and method were correct, investigate three causes in order: application error (did the treatment get applied per label?), reinfestation from neighboring operations (did counts drop then rise back?), and resistance (has the same product underperformed across multiple seasons?). Retreat with a different product class if resistance is suspected. Document your pre- and post-treatment counts and calculate efficacy before concluding anything.

How do I know if my treatment failure is resistance?

Resistance is indicated by below-80% efficacy despite correct application, the same product showing declining efficacy across 2-3 consecutive seasons, and no clear reinfestation pattern explaining the elevated counts. A single low-efficacy result is not sufficient evidence of resistance -- application error and reinfestation are more common causes. Resistance becomes the likely explanation when the same product fails repeatedly with correct application across multiple treatment cycles. Contact your state apiarist if you suspect resistance -- they can help confirm the pattern and may have regional resistance data.

Does VarroaVault guide me through a treatment failure response?

Yes. When you log a post-treatment count that calculates to below-90% efficacy, VarroaVault activates a treatment failure response workflow. It walks you through the cause identification questions (application timing, method, reinfestation likelihood, prior efficacy history), recommends a retreat product based on your cause assessment, and gives you the option to generate a resistance report formatted for state apiarist submission. The workflow ensures you document the failure thoroughly while the details are current.

How do I know if my varroa treatment is working?

Run a mite count 2-4 weeks after the treatment ends and compare it to your pre-treatment count. The efficacy formula is: ((pre-count - post-count) / pre-count) x 100. A result above 90% indicates effective treatment. Results below 80% should trigger investigation for possible resistance, application error, or reinfestation. Log both counts in VarroaVault to track efficacy trends across treatment cycles.

How often should I check mite levels in my hives?

At minimum, once per month (every 3-4 weeks) during the active season. Increase to every 2 weeks when counts are near threshold or after a treatment to verify it worked. In fall, monitoring frequency matters most because the window to treat before winter bees are raised is narrow. VarroaVault's monitoring reminders can be set to your preferred interval for each apiary.

What records should I keep for varroa management?

Each record should include: date of count or treatment, hive identifier, monitoring method used, number of bees sampled, mites counted, infestation percentage, treatment product name and EPA registration number, dose applied, treatment start and end dates, and PHI end date. State apiarists typically expect this level of detail during inspections. VarroaVault captures all of these fields in a single log entry.

Sources

American Beekeeping Federation (ABF)
USDA ARS Bee Research Laboratory
Honey Bee Health Coalition
Penn State Extension Apiculture Program
Project Apis m.

Get Started with VarroaVault

The information in this guide is most useful when you have your own mite count data to apply it to. VarroaVault stores every count, flags threshold crossings automatically, and builds the treatment history you need for state inspections and effective management decisions. Start your free trial at varroavault.com.