3 ms·
All it takes is a load balancer misconfiguration on a core service to take a large scale service down.
by alpb 5y ago
All it takes is a load balancer misconfiguration on a core service to take a large scale service down.
- jrochkind1 5y agoit indeed behaved like a routing issue of some kind (my app was still UP, and was still logging, just no traffic could get to it), and a heroku incident status line said "Engineers are recovering affected routing components," so, yup.