Hey Chaskins - you're right, and I'm sorry. A redeployment would get things all right.

I want to get eyes on your specific services so if you can put a link for that. (Also if this is genuinely for Rippling, you folks should have a direct line in Slack with us.)

To everyone else following along — "resolved" on our end meant the root cause (the bad rule) was rolled back. But we understand that doesn't mean every affected service recovered cleanly, and we should have been clearer about that distinction.

If your services are still down or degraded, please reach out - we are actively working with everyone.

Post mortem here: https://blog.railway.com/p/incident-report-february-11-2026