Faultline

What happens when authentication fails?

When your authentication provider goes down, every service that validates tokens or manages sessions stops working. In a simulated Auth0 outage across 18 interconnected services, 4 services failed completely and 2 degraded, with an estimated revenue impact of $280,000+ over 2 hours. The cascade starts at Auth0, propagates through the Core API Gateway, then takes down User Account Service, Fraud Detection, Admin Dashboard, and Payment Processing.

Users can't log in, APIs reject requests, and internal tools become inaccessible. Use the interactive simulator below to trigger the outage and watch the cascade unfold in real time.

[Interactive simulator loads here — requires JavaScript]

Expected Impact Summary

When this scenario is triggered, the cascade engine traces every dependency path and calculates the full blast radius. Here's what happens to the 18-service infrastructure over 2 hours:

Cascade order: Auth0 → Core API Gateway → User Account Service → Fraud Detection → Admin Dashboard → Payment Processing

This simulation is powered by Faultline's dependency mapping and cascade analysis engine — the same engine you can use on your own infrastructure. Get early access to map your services, run your own simulations, and identify single points of failure before they cause real outages.

Frequently Asked Questions

What happens when Auth0 goes down?

When Auth0 goes down, any service that relies on it for token validation, login, or session management stops working. APIs return 401 errors, users can't sign in, and admin panels become inaccessible.

How do I build resilience against auth provider outages?

Cache validated tokens locally, implement token refresh fallbacks, consider a secondary auth provider, and ensure your critical paths can degrade gracefully when auth is unavailable.

Try Other Scenarios