--- title: Increasing the Realtime Database concurrency limits description: Firebase raised the concurrent connections limit on Realtime Database for Flame and Blaze plan users from 10,000 to 100,000, thanks to infrastructure... canonical: https://daily.dev/posts/increasing-the-realtime-database-concurrency-limits-ocb23bzci twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Increasing the Realtime Database concurrency limits | daily.dev og:description: Firebase raised the concurrent connections limit on Realtime Database for Flame and Blaze plan users from 10,000 to 100,000, thanks to infrastructure... og:url: https://daily.dev/posts/increasing-the-realtime-database-concurrency-limits-ocb23bzci og:image: https://api.daily.dev/og/posts/OcB23BZCI.png og:image:alt: Increasing the Realtime Database concurrency limits og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Increasing the Realtime Database concurrency limits **[Firebase](https://daily.dev/sources/firebase-blog)** · 2 min read · 0 upvotes · 0 comments ## Summary Firebase raised the concurrent connections limit on Realtime Database for Flame and Blaze plan users from 10,000 to 100,000, thanks to infrastructure improvements. Previously developers had to contact Firebase to request an increase above 10,000 so the team could verify app health (checking for unindexed queries or heavy reads). Developers needing more than 100,000 concurrent connections should still contact Firebase directly. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is the concurrent connection limit for Firebase Realtime Database on the Flame and Blaze plans? The concurrent connection limit for Firebase Realtime Database on Flame and Blaze plans is 100,000, increased from a prior limit of 10,000. This increase was made possible by infrastructure improvements. Developers needing to support more than 100,000 concurrent connections need to contact Firebase directly, and queries should still be indexed and listeners should never be added to the root path. _Track platform limit changes like this Firebase update on daily.dev as you plan for scale._ ### Do I need Firebase's approval to exceed 10,000 concurrent connections on Realtime Database? No, approval is no longer required up to 100,000 concurrent connections. Previously, Firebase required developers to reach out so the team could verify app health, checking for unindexed queries or heavy reads, before raising the limit above 10,000. That manual verification step was removed as part of the increase to 100,000. _Developers scaling Firebase apps can follow database limit updates on daily.dev._ ## Similar posts on daily.dev - [NEW: Bursty Concurrency—Coverage for Spikes](https://daily.dev/posts/new-bursty-concurrency-coverage-for-spikes-oywvtwix8) · Inngest Blog · 0 upvotes · 0 comments - [Optimize your Firebase Remote Config usage](https://daily.dev/posts/optimize-your-firebase-remote-config-usage-woddfd7ym) · Firebase · 1 upvotes · 1 comments - [Medium](https://daily.dev/posts/medium-jvobby0wg) · Medium · 0 upvotes · 0 comments --- Tags: [#infrastructure](https://daily.dev/tags/infrastructure), [#backend](https://daily.dev/tags/backend), [#firebase](https://daily.dev/tags/firebase) [View this post on daily.dev](https://daily.dev/posts/increasing-the-realtime-database-concurrency-limits-ocb23bzci) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Increasing the Realtime Database concurrency limits","url":"https://daily.dev/posts/increasing-the-realtime-database-concurrency-limits-ocb23bzci","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/increasing-the-realtime-database-concurrency-limits-ocb23bzci"},"datePublished":"2026-08-23T12:20:52.179Z","dateModified":"2026-08-23T12:51:00.614Z","description":"Firebase raised the concurrent connections limit on Realtime Database for Flame and Blaze plan users from 10,000 to 100,000, thanks to infrastructure...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ed721de96163685d26ab7e314be3ebc?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ed721de96163685d26ab7e314be3ebc?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Firebase","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Firebase","logo":"https://media.daily.dev/image/upload/s--i395oqZH--/f_auto,q_auto/v1787487448/logos/firebase-blog?_a=BAMAMicg0","url":"https://daily.dev/sources/firebase-blog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/increasing-the-realtime-database-concurrency-limits-ocb23bzci","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"infrastructure,backend,firebase","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Firebase","item":"https://daily.dev/sources/firebase-blog"},{"@type":"ListItem","position":3,"name":"Increasing the Realtime Database concurrency limits"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/increasing-the-realtime-database-concurrency-limits-ocb23bzci#faq","mainEntity":[{"@type":"Question","name":"What is the concurrent connection limit for Firebase Realtime Database on the Flame and Blaze plans?","acceptedAnswer":{"@type":"Answer","text":"The concurrent connection limit for Firebase Realtime Database on Flame and Blaze plans is 100,000, increased from a prior limit of 10,000. This increase was made possible by infrastructure improvements. Developers needing to support more than 100,000 concurrent connections need to contact Firebase directly, and queries should still be indexed and listeners should never be added to the root path. Track platform limit changes like this Firebase update on daily.dev as you plan for scale."}},{"@type":"Question","name":"Do I need Firebase's approval to exceed 10,000 concurrent connections on Realtime Database?","acceptedAnswer":{"@type":"Answer","text":"No, approval is no longer required up to 100,000 concurrent connections. Previously, Firebase required developers to reach out so the team could verify app health, checking for unindexed queries or heavy reads, before raising the limit above 10,000. That manual verification step was removed as part of the increase to 100,000. Developers scaling Firebase apps can follow database limit updates on daily.dev."}}]} ```