Incidents | Firenote Incidents reported on status page for Firenote https://status.firenote.io/ https://d1lppblt9t2x15.cloudfront.net/logos/507a64ad6af3ee01ed4316b4916cfa40.png Incidents | Firenote https://status.firenote.io/ en Firenote Production Systems recovered https://status.firenote.io/ Tue, 26 May 2026 21:34:44 +0000 https://status.firenote.io/#073d7739e9ef1725235ab143fc33d498d34c3278223fc57d9d0cf04ea854f0da Firenote Production Systems recovered Firenote Production Systems went down https://status.firenote.io/ Tue, 26 May 2026 21:01:13 +0000 https://status.firenote.io/#073d7739e9ef1725235ab143fc33d498d34c3278223fc57d9d0cf04ea854f0da Firenote Production Systems went down Firenote login availability recovered https://status.firenote.io/ Mon, 23 Mar 2026 20:30:16 +0000 https://status.firenote.io/#580622deea0f71adb6077748306a4c994ea5c73dd115affce780d55dd309f6f4 Firenote login availability recovered Firenote login availability went down https://status.firenote.io/ Mon, 23 Mar 2026 20:22:44 +0000 https://status.firenote.io/#580622deea0f71adb6077748306a4c994ea5c73dd115affce780d55dd309f6f4 Firenote login availability went down Intermittent Firenote Access Issues https://status.firenote.io/incident/813001 Tue, 27 Jan 2026 21:58:00 -0000 https://status.firenote.io/incident/813001#07da53f44c7afca4d08458140a740beb18cf2f440c10617494af1a24d4c76c17 The issue has been resolved. The disruption was caused by an external dependency experiencing instability. We’ll continue monitoring to ensure stability. Intermittent Firenote Access Issues https://status.firenote.io/incident/813001 Tue, 27 Jan 2026 20:03:00 -0000 https://status.firenote.io/incident/813001#8267512cdda4f004621b1c54762dd710f45d82ee74d47cf75aa5fb5571d91b6e We are investigating reports of intermittent issues affecting login and application access for some users. This appears to be related to an external dependency and is causing degraded performance rather than a full outage. Our team is actively working to restore normal service for those affected. We’ll share updates as more information becomes available. Scheduled kubernetes maintenance https://status.firenote.io/incident/806825 Sun, 18 Jan 2026 18:15:42 -0000 https://status.firenote.io/incident/806825#f9b550a7fc1996bed2d81723b7bfa580cb4bcf606bb0da0b5851be363b547bf7 Maintenance completed Scheduled kubernetes maintenance https://status.firenote.io/incident/806825 Sun, 18 Jan 2026 07:00:17 -0000 https://status.firenote.io/incident/806825#3c86d2e9bc1ad22c007788a4488e42509a4634b963eb3beb928cc3a30af1a564 scheduled kubernetes upgrades are complete Firenote was temporarily unavailable for some users https://status.firenote.io/incident/804508 Mon, 12 Jan 2026 14:49:00 -0000 https://status.firenote.io/incident/804508#822a2a176d506620702b8f02c172de3c3652d17e85d99b13a65c8098fd9a6983 This issue has been resolved and all Firenote services are operating normally. Firenote was temporarily unavailable for some users https://status.firenote.io/incident/804508 Mon, 12 Jan 2026 11:09:00 -0000 https://status.firenote.io/incident/804508#9a2b852f16d7e5f108928aa1c4e15edcdf538f0eeb3e4057264b25a3434fd55d During the early morning hours of January 12, 2026 (MST), some users were unable to access the Firenote application. This disruption was caused by an external infrastructure update that impacted one of our internal services. While Firenote was running, it was unable to fully load, which made the application inaccessible for affected users. Our team identified the issue shortly after it was discovered and restored full service by 7:49 AM MST. There was no impact to customer data, and all systems are now operating normally. If you continue to experience any issues, please contact Firenote Support.