Pathify had 8 outages in the last 2 years totaling 36h 49m of downtime — averaging 0.3 incidents per month.
There were 8 Pathify outages since February 12, 2025 totaling 36h 49m of downtime. Each is summarised below — incident details, duration, and resolution information.
We have observed intermittent access issues on the Pathify Service Desk and are working directly with the service provider. For critical service issues, please contact [email protected] directly.
Pathify service desk is fully restored.
A network issue at our cloud provider is causing occasional errors in the Pathify CXP, including email and calendar syncing. The platform remains available and we are monitoring while the provider works to resolve the issue.
Our cloud provider has resolved the underlying network issue. The platform remained available throughout, though some users may have seen intermittent errors when loading individual integrations.
We're aware of reported Instructure outage that is affecting Canvas widgets on the Pathify CXP. All other Pathify systems are functioning as expected. We are monitoring and will update here as more information is available.
All Pathify systems remain operational. Outside of specific widget degradation (Canvas), we are unaffected by the Instructure outage. We will continue to monitor the situation closely and will provide updates as new information becomes available.
Instructure reports that the Canvas outage has concluded. Spot testing of widgets presents no apparent disorder. Pathify is closing this upstream outage based incident.
We are currently investigating reports about course widgets failing to refresh data.
We are continuing to investigate this issue.
Resolved - Investigation complete. Issues were isolated to individual cases with different root causes. All affected customers are being addressed independently.
We are investigating issues on reported slow downs in Portal. Our team is evaluating and will report back within the hour.
We have deployed additional resources to Portals to improve system performance and are now working working to identify and resolve the underlying issues. We will have another update by 1PM ET / 11AM MT.
Issues relating to application latency are resolved, Portals responding as expected.
The Flow cluster is presently offline. We are rehoming it and expect full recovery within 30 minutes. No action is necessary on your side.
We are continuing to investigate this issue.
All Australian Flow servers are now back online. This issue has been determined to be due to a misconfigured terraform structure.
This incident has been resolved.
We are investigating observed high database loads. No user impact has been observed at this stage.
No user impact has been detected.
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.
The cluster is being rerolled. At worst, the last node on the last customer will be replaced within 50 minutes.
The cluster definitions are now fully reissued. All service will be resumed within five minutes.
All clusters are now restored and operational.
This incident has been resolved.