MongoDB Atlas Free Tier (M0) Limits and Throttling

How to fix it

Try these in order — the most common fix is first.

1. 1. Free up storage

   Copy steps
   1. Drop unused collections and indexes
   2. Check size in Database > Browse Collections
   3. Delete old test data
   Did this fix it? Yes No

2. 2. Reduce operations and connections

   Copy steps
   1. Batch writes and add indexes to cut read load
   2. Reuse one MongoClient and set maxPoolSize
   Did this fix it? Yes No

3. 3. Upgrade when needed

   Copy steps
   1. Open the cluster and click Edit Configuration
   2. Choose Flex (about $8 to $30/month) or Dedicated M10 (about $57/month)
   Did this fix it? Yes No

4. 4. Export before you leave

   1. Use mongodump on your data (not the admin database) before deleting or abandoning an M0
   Did this fix it? Yes No

Symptoms

Queries slow down or hang, 'you are over your space quota', connection errors at 500, or features such as Performance Advisor missing.

Why it happens

• 512 MB storage cap including indexes
• 100 operations per second cap
• 10 GB in and 10 GB out per 7 days
• 500 connections maximum
• Unsupported features on shared tier

This guide also covers

• mongodb atlas free tier limits
• mongodb atlas m0 limits
• mongodb atlas 512mb limit
• mongodb atlas free tier throttled

The same problem in other apps

All plan limits, paywalls & watermarks guides →

• Supabase Edge Function 546 WORKER_LIMIT Error (Supabase)

Other MongoDB Atlas errors

• MongoDB Atlas Connection Timed Out (IP Not Whitelisted)
• MongoServerSelectionError: Fix for MongoDB Atlas
• MongoDB Atlas Authentication Failed (bad auth)
• MongoDB querySrv ENOTFOUND / ECONNREFUSED Error
• MongoDB Atlas Cluster Paused (Resume or Auto-Pause)
• MongoDB Atlas Unexpected Bill: Why It's So High
• MongoDB Atlas Too Many Connections Error
• MongoDB Atlas AWS VPC Peering Not Connecting