Smart Provider Failover

# Smart Provider Failover

NotifySetu utilizes active circuit breaking and latency budgets to route around transient upstream carrier degradations.

Resilience4j Circuit Breakers

When a primary provider (e.g. Twilio or SendGrid) exceeds 5% error rates or latency thresholds over a rolling 60-second window, the circuit breaker enters the **OPEN** state and requests are automatically re-routed to secondary providers (such as Amazon SES or Plivo).

Client Request -> NotifySetu Gateway
                    |
                    +-> Primary: SendGrid (Degraded) -> [REROUTE]
                    |
                    +-> Secondary: AWS SES [DELIVERED - 84ms]