Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
News
Security News
Firebase Outage Today: What Happened & What You Need to Know 🚨
Message
<blockquote data-quote="Fan-of-spyshelter" data-source="post: 1129452" data-attributes="member: 96367"><p><h3><img class="smilie smilie--emoji" loading="lazy" alt="🔍" title="Magnifying glass tilted left :mag:" src="https://cdn.jsdelivr.net/joypixels/assets/6.6/png/unicode/64/1f50d.png" data-shortname=":mag:" /> Overview of the Incident</h3><p></p><p><strong>Date of incident:</strong> June 12, 2025</p><p><strong>Start time (PDT):</strong> around 11:00 (≈ 19:00 UTC)</p><p><strong>Last dashboard update:</strong> 11:42 PDT (≈ 19:42 UTC)</p><p></p><p></p><p>Earlier today, Firebase experienced a widespread service disruption impacting several key services across multiple regions:</p><p></p><ul> <li data-xf-list-type="ul"><strong>Realtime Database:</strong> authentication issues and access errors</li> <li data-xf-list-type="ul"><strong>Hosting API:</strong> failures when deploying or accessing hosted sites</li> <li data-xf-list-type="ul"><strong>Data Connect:</strong> offline due to an underlying Google Cloud outage</li> <li data-xf-list-type="ul"><strong>App Check:</strong> higher error rates and failures</li> <li data-xf-list-type="ul"><strong>Console UI:</strong> reduced availability</li> <li data-xf-list-type="ul"><strong>Cloud Messaging:</strong> increased latency and message errors</li> <li data-xf-list-type="ul"><strong>Test Lab:</strong> blocked tests</li> <li data-xf-list-type="ul"><strong>App Hosting:</strong> origin/API outages</li> </ul><p></p><p>In short, essential Firebase components—from backend systems to developer tools—were affected simultaneously.</p><p></p><h3><img class="smilie smilie--emoji" loading="lazy" alt="🧭" title="Compass :compass:" src="https://cdn.jsdelivr.net/joypixels/assets/6.6/png/unicode/64/1f9ed.png" data-shortname=":compass:" /> Why It Matters</h3><p></p><p>Firebase powers countless mobile and web apps with real-time data, hosting, authentication, messaging, and CI/CD workflows. An outage like this can lead to:</p><ul> <li data-xf-list-type="ul">App crashes or frozen interfaces</li> <li data-xf-list-type="ul">Broken deployments and updates</li> <li data-xf-list-type="ul">Message delivery failures (push notifications)</li> <li data-xf-list-type="ul">Development delays and blocked testing</li> </ul><p></p><p>If you're running production apps, </p><p>this could translate into major user-facing issues and revenue losses.</p><p></p><h3><img class="smilie smilie--emoji" loading="lazy" alt="📊" title="Bar chart :bar_chart:" src="https://cdn.jsdelivr.net/joypixels/assets/6.6/png/unicode/64/1f4ca.png" data-shortname=":bar_chart:" /> What Developers Should Do</h3> <ol> <li data-xf-list-type="ol"><strong>Check the status dashboard.</strong> Firebase actively monitors and updates the status page at <a href="https://status.firebase.google.com" target="_blank">Firebase Status Dashboard</a>.</li> <li data-xf-list-type="ol"><strong>Use SDK fallbacks.</strong> Implement offline modes for Realtime Database and handle Hosted URL failures gracefully.</li> <li data-xf-list-type="ol"><strong>Delay non-critical operations.</strong> Postpone deployments, testing, or messaging if possible.</li> <li data-xf-list-type="ol"><strong>Monitor Google Cloud Health.</strong> Since this likely stems from a broader GCP disruption, code resilience against upstream failures is key.</li> <li data-xf-list-type="ol"><strong>Plan for redundancy.</strong> Consider multi-region setup or mesh across alternatives for critical services.</li> </ol></blockquote><p></p>
[QUOTE="Fan-of-spyshelter, post: 1129452, member: 96367"] [HEADING=2]🔍 Overview of the Incident[/HEADING] [B]Date of incident:[/B] June 12, 2025 [B]Start time (PDT):[/B] around 11:00 (≈ 19:00 UTC) [B]Last dashboard update:[/B] 11:42 PDT (≈ 19:42 UTC) Earlier today, Firebase experienced a widespread service disruption impacting several key services across multiple regions: [LIST] [*][B]Realtime Database:[/B] authentication issues and access errors [*][B]Hosting API:[/B] failures when deploying or accessing hosted sites [*][B]Data Connect:[/B] offline due to an underlying Google Cloud outage [*][B]App Check:[/B] higher error rates and failures [*][B]Console UI:[/B] reduced availability [*][B]Cloud Messaging:[/B] increased latency and message errors [*][B]Test Lab:[/B] blocked tests [*][B]App Hosting:[/B] origin/API outages [/LIST] In short, essential Firebase components—from backend systems to developer tools—were affected simultaneously. [HEADING=2]🧭 Why It Matters[/HEADING] Firebase powers countless mobile and web apps with real-time data, hosting, authentication, messaging, and CI/CD workflows. An outage like this can lead to: [LIST] [*]App crashes or frozen interfaces [*]Broken deployments and updates [*]Message delivery failures (push notifications) [*]Development delays and blocked testing [/LIST] If you're running production apps, this could translate into major user-facing issues and revenue losses. [HEADING=2]📊 What Developers Should Do[/HEADING] [LIST=1] [*][B]Check the status dashboard.[/B] Firebase actively monitors and updates the status page at [URL="https://status.firebase.google.com"]Firebase Status Dashboard[/URL]. [*][B]Use SDK fallbacks.[/B] Implement offline modes for Realtime Database and handle Hosted URL failures gracefully. [*][B]Delay non-critical operations.[/B] Postpone deployments, testing, or messaging if possible. [*][B]Monitor Google Cloud Health.[/B] Since this likely stems from a broader GCP disruption, code resilience against upstream failures is key. [*][B]Plan for redundancy.[/B] Consider multi-region setup or mesh across alternatives for critical services. [/LIST] [/QUOTE]
Insert quotes…
Verification
Post reply
Top
