Firestore: 4 DEADLINE_EXCEEDED: Deadline exceeded / 14 UNAVAILABLE: The service is currently unavailable
A Firestore request timed out or could not reach the service — contention, hot documents, large operations or network issues.
4 DEADLINE_EXCEEDED: Deadline exceeded14 UNAVAILABLE: The service is currently unavailableFirestore DEADLINE_EXCEEDED10 ABORTED: Too much contention on these documentsCould not reach Cloud Firestore backend. Backend didn't respond within 10 seconds Meaning
Retry with exponential backoff (client SDKs do for some calls). Reduce write contention (one document updated more than ~1/second sustained), batch large writes in chunks of 500, avoid unbounded queries, and check connectivity (offline persistence on mobile). ABORTED indicates transaction contention.
Common causes
- Hot document updated too often (1 write/sec guideline)
- Large batch/transaction or large queries
- Network blocked/unstable
- Cloud Functions timeouts hitting Firestore
- Service transient issue
⚡ Quick fix
- Retry with backoff and jitter
- Shard counters; spread writes across documents
- Paginate queries and chunk batches
Detailed fix by platform
Firebase
- Use
limit()and cursors; for counters use distributed counters orFieldValue.incrementacross shards
How to diagnose
- Code — DEADLINE_EXCEEDED, UNAVAILABLE, ABORTED?
- Hotspot — Single doc?
- Size — Batch/query large?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- auth/network-request-failed Firebase Auth: auth/network-request-failed — A network AuthError (such as timeout, interrupted connection or unreachable host) has occurred
- Error 403: API has not been used in project (Terraform) Terraform: Error: Error creating Network: googleapi: Error 403: Compute Engine API has not been used in project 123 before or it is disabled
- Firebase CLI: Authentication Error: Your credentials are no longer valid Firebase CLI: Error: Authentication Error: Your credentials are no longer valid. Please run firebase login --reauth
Most viewed in Google Cloud / Firebase
- Container failed to start Cloud Run: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable
- Could not load the default credentials Google Cloud: Error: Could not load the default credentials. Browse to https://cloud.google.com/docs/authentication/getting-started
- 409: The resource already exists Compute Engine: ERROR: (gcloud.compute.instances.create) Could not fetch resource: The resource 'projects/p/zones/z/instances/vm-1' already exists
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 4 Nov 2026