Is Flxbl Toolkit down?
Last checked 7m agoNo incidents right now.
Flxbl Toolkit is operational right now. Last checked 7m ago; the most recent incident resolved 34d ago.
Real-time Flxbl Toolkit status, recent outages, and incident history: pulled directly from Flxbl Toolkit's official status page at status.flxbl.io every 5 minutes. Pingoru tracks 4 Flxbl Toolkit services and has captured 6 incidents in the last 90 days (98.06% uptime). Get email, Slack, Discord, or webhook alerts the moment Flxbl Toolkit reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days-
Timeline · 2 updates
- investigating · Sep 17, 2026, 01:33 PM UTC
Status: Investigating A tenant is currently experiencing an outage We are currently investigating
- resolved · Sep 17, 2026, 01:49 PM UTC
Status: Resolved Issue has been resolved
Latest: Status: Resolved Issue has been resolved
-
-
Timeline · 4 updates
- investigating · Sep 17, 2026, 03:43 AM UTC
Status: Investigating Our daily backup job is not functioning We are currently looking into the issue Affected components sfp server (flxbl managed instances) (Degraded performance)
- identified · Sep 17, 2026, 04:07 AM UTC
Status: Identified Root cause found, we're rolling out a fix Affected components sfp server (flxbl managed instances) (Degraded performance)
- resolved · Sep 17, 2026, 05:48 AM UTC
Status: Resolved All instances are patched, and backup is now executed Affected components sfp server (flxbl managed instances) (Operational)
- resolved · Sep 17, 2026, 05:49 AM UTC
Status: Resolved Third Party Provider's deprecation to artifact repository was not observed by us, which resulted in scripts to fetch the required tools. We have corrected the same and strenthened our monitoring of notifications Affected components sfp server (flxbl managed instances) (Operational)
Latest: Status: Resolved Third Party Provider's deprecation to artifact repository was not observed by us, which resulted in scripts to fetch the required tools. We have corrected the same…
-
- sfp cli
Timeline · 3 updates
- identified · Sep 14, 2026, 08:55 PM UTC
Status: Identified Installing a source package that applies layout assignments or search layouts from mutators/*.yml can switch off unrelated settings on the target object, such as Allow Activities, Allow Reports and Allow in Chatter Groups, and clear the object description. sfp cli 51.6.0 and later are affected, including deployments run through codev. Profile-only assignments and unlocked package installs are not. We have identified the cause and a fix is in review. Until it ships, review those objects after each install and re-enable any settings that were switched off. We will post here when the fix is released. Affected components sfp server (flxbl managed instances) (Degraded performance) sfp cli (Degraded performance)
- monitoring · Sep 15, 2026, 06:33 AM UTC
Status: Monitoring We are applying the fix to tenants, We will update when the rollout is completed Affected components sfp cli (Degraded performance) sfp server (flxbl managed instances) (Degraded performance)
- resolved · Sep 15, 2026, 09:41 AM UTC
Status: Resolved All instances are patched Affected components sfp server (flxbl managed instances) (Operational) sfp cli (Operational)
Latest: Status: Resolved All instances are patched Affected components sfp server (flxbl managed instances) (Operational) sfp cli (Operational)
-
-
Timeline · 2 updates
- identified · Aug 26, 2026, 12:58 PM UTC
Status: Identified When a Salesforce org loses access — for example if its stored refresh token expires, or the connection is revoked — a stale lock can be left on the corresponding environment. Releases and other jobs targeting that environment then queue behind that lock instead of failing, and can stay blocked for up to two hours. If you see jobs waiting on an environment lock, deactivate the affected environment. That stops new work being dispatched to it and clears the blockage. Reactivate it once the org has been re-authenticated. A fix is in progress: the lock will be released when the step after acquisition fails, and the wait will be bounded so jobs fail fast rather than queueing indefinitely.
- resolved · Aug 27, 2026, 05:07 AM UTC
Status: Resolved Fix is now rolling out to all tenants
Latest: Status: Resolved Fix is now rolling out to all tenants
-
- codev desktop app
Timeline · 2 updates
- identified · Jul 27, 2026, 11:44 AM UTC
Status: Identified Users will be unable to sync or deploy using desktop app Affected components codev desktop app (Degraded performance)
- resolved · Jul 27, 2026, 01:41 PM UTC
Status: Resolved Please update to the latest version of the app Affected components codev desktop app (Operational)
Latest: Status: Resolved Please update to the latest version of the app Affected components codev desktop app (Operational)
-
See the full Flxbl Toolkit outage history
1 more incident in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Flxbl Toolkit outage history →Or sign up free to get alerts when Flxbl Toolkit breaks · 10 free monitors · No credit card
- A tenant is experiencing an outage ResolvedStarted Sep 17, 2026, 01:33 PM UTC · Resolved Sep 17, 2026, 01:49 PM UTC · 16m
- Started Sep 17, 2026, 03:43 AM UTC · Resolved Sep 17, 2026, 05:49 AM UTC · 2h 6m
- Started Sep 14, 2026, 08:55 PM UTC · Resolved Sep 15, 2026, 09:41 AM UTC · 12h 45m
- Started Aug 26, 2026, 12:58 PM UTC · Resolved Aug 27, 2026, 05:07 AM UTC · 16h 8m
- Started Jul 27, 2026, 11:44 AM UTC · Resolved Jul 27, 2026, 01:41 PM UTC · 1h 56m
- Started Jul 25, 2026, 01:33 AM UTC · Resolved Jul 25, 2026, 02:48 AM UTC · 1h 15m