You can now better protect your upstream services from attacks, abuse attempts, and cascading error conditions with ngrok's new circuit-breaker Traffic Policy action. A circuit breaker helps improve the reliability of your systems by rejecting requests when your services respond with 500-level error codes, then re-evaluating the health of your upstream service before resuming normal traffic flows. This feature is available with every ngrok account and can be easily customized to suit your specific needs. You can add a circuit breaker in front of your APIs and apps with a single Traffic Policy rule, which also allows you to chain rate limiting and circuit breaking for enhanced protection. The circuit breaker action is designed to work seamlessly with other Traffic Policy actions, such as rate limiting, forward-internal, and mTLS. By implementing a circuit breaker, you can prevent cascading failures across services, reduce CPU cycles wasted on failed tasks, and provide better user experiences with informative error messages.