Pathify experienced a major incident on February 12, 2025 affecting Pathify Flow, lasting 3h 6m. The incident has been resolved; the full update timeline is below.
Affected components
Pathify Flow
Update timeline
- identified Feb 12, 2025, 10:35 PM UTC
Flow has received a bad cluster definition in continuous integration and has released a node definition which cannot start. We have identified the root cause of this bad cluster definition and are replacing the cluster now.
- identified Feb 12, 2025, 10:40 PM UTC
The cluster is being rerolled. At worst, the last node on the last customer will be replaced within 50 minutes.
- identified Feb 12, 2025, 11:05 PM UTC
The cluster definitions are now fully reissued. All service will be resumed within five minutes.
- identified Feb 12, 2025, 11:15 PM UTC
All clusters are now restored and operational.
- resolved Feb 13, 2025, 01:42 AM UTC
This incident has been resolved.