Gumloop Outage History

17 incidents recorded over the last 365 days, 17 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Gumloop status100.00% uptime history

Every Recorded Gumloop Incident

Gumloop incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Jun 4, 2026Tool calls via Gumloop SDK not working on agent sandboxesSystem is stable.1h 50mResolved
Jun 3, 2026Slow or unresponsive tool callsWe have deployed a fix.26 minResolved
Apr 7, 2026Slack Agents + Triggers Delayed processingAll triggers and Slack agents have been responded to and delays are gone59 minResolved
Mar 28, 2026Triggers are seeing elevated error rates We have identified the root cause of this issue and resolved it. New triggers should be working normally. If your flows were affected by this outage, you will be notified.1h 39mResolved
Mar 5, 2026Unresponsive Agents in SlackSlack Agents now appear to be completely recovered4h 19mResolved
Mar 4, 2026Flows stuck in "Running" stateAll flows should be functioning normally now-73 minResolved
Feb 24, 2026Automation runs stuck in "Running" stateAll automations are running successfully now0 minResolved
Feb 23, 2026Some automation runs appear to be hangingAll issues should be resolved, and no automations should be in hanging going forward.54 minResolved
Jan 14, 2026Degraded performance for agents All latency issues should be resolved2h 4mResolved
Jan 14, 2026Errors With Custom Nodes and MCP NodesDownstream provider has resolved issues23 minResolved
Jan 13, 2026Issues with accessing flows and workspacesAll systems functioning correctly3h 4mResolved
Jan 6, 2026Delayed processingWe have monitored our systems for recovery and all services remain fully operational since 2026-01-06 21:22:00+00.21h 27mResolved
Jan 5, 2026Slack Agents + Triggers DelayedIncident has been resolved59 minResolved
Dec 23, 2025Triggers ImpactedAll impact has been resolved47 minResolved
Dec 12, 2025SSO MigrationMigration completed successfully.1h 44mResolved
Nov 21, 2025Increase in Timeouts with MCP NodesError rates returned to normal. MCP Nodes are functioning correctly.31 minResolved
Nov 10, 2025Credit Deduction Not Functioning CorrectlyThe issue is fully resolved59 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Gumloop incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Gumloop Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Gumloop acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Gumloop outage in this window ran 21h 27m, against a mean recovery of 2h 38m. If you depend on Gumloop in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.