Skip to main content
Circuit breakers temporarily exclude failing upstream transports and admit recovery attempts before returning them to ordinary routing. HTTP and WebSocket health are tracked separately. Connection state, rate-limit cooldowns, lag, method restrictions and request parameters can exclude a provider even when its circuit is closed.

Rate limits and shared providers

Rate-limit backoff is a separate signal from circuit failure. A provider can be temporarily rate limited while its circuit remains closed. Identical upstreams shared across profiles share runtime signals; creating another profile does not bypass the provider’s real quota. Inspect the affected transport and region. An aggregate warning may represent only part of the deployment. Do not interpret a regional problem as proof that every region is unavailable.

Configuration

Circuit Breaker Defaults

Circuit settings take effect when provider instances start; restart Lasso after changing application configuration. YAML reload does not restart existing circuit breakers. See Profiles for sharing behavior and Provider capabilities for error rules.