Incidents and maintenance reported on status page for MentraTrack https://status.mentratrack.com/ https://d1lppblt9t2x15.cloudfront.net/logos/237af8ebdef81b9c6a3ed3fd79776659.png https://status.mentratrack.com/ en https://status.mentratrack.com/incident/1094123 Mon, 30 Mar 2026 22:42:00 -0000 https://status.mentratrack.com/incident/1094123#05d8794f14e00c84fe3eae5e9d202d6beef7b15c5a9067dcade1add38a78f24d Incident Resolved: Brief Data Exposure via Railway CDN Misconfiguration Timeline: • Investigating: We received reports of unexpected data exposure where users were occasionally served pages or dashboard views belonging to other active sessions. • Identified: The root cause was an upstream incident at our hosting provider, Railway. A configuration change on their platform accidentally enabled CDN caching on domains where it was explicitly disabled. As a result, the edge network cached HTTP GET responses that lacked strict cache headers, causing some authenticated sessions to be briefly visible to other traffic. • Resolved: Railway reverted the deployment and performed a full, global purge of their CDN cache. All systems are back to normal operating status. Next Steps: While the fault occurred at the infrastructure level, we are actively deploying application-wide overrides to force strict Cache-Control: no-store, no-cache, must-revalidate headers on all authenticated endpoints. This ensures that even if a provider misconfigures their edge routing in the future, your private data remains protected.