Pivotal Tracker Status
All Systems Operational
Tracker API Operational
Tracker Web Application Operational
Tracker Marketing Site and Blog Operational
Network - Seattle, WA (SEA03) Operational
Network - Ashburn, VA (IAD01) Operational
Network - Zurich, CH (ZRH01) Operational
Operational
Degraded Performance
Partial Outage
Major Outage
System Metrics Month Week Day
Tracker API V5 Uptime
Fetching
Tracker Web application uptime
Fetching
Server Response Time
Fetching
Past Incidents
Feb 10, 2016

No incidents reported today.

Feb 9, 2016

No incidents reported.

Feb 8, 2016

No incidents reported.

Feb 7, 2016

No incidents reported.

Feb 6, 2016

No incidents reported.

Feb 5, 2016

No incidents reported.

Feb 4, 2016

No incidents reported.

Feb 3, 2016

No incidents reported.

Feb 2, 2016

No incidents reported.

Feb 1, 2016

No incidents reported.

Jan 31, 2016

No incidents reported.

Jan 30, 2016

No incidents reported.

Jan 29, 2016
Resolved - We still plan to recover missing story history, but are testing extensively before doing so - so no ETA just yet. We'll create a new update for further updates in this area. Meanwhile, if you have any questions, please email us at tracker@pivotal.io.
Jan 29, 23:26 UTC
Update - We are postponing the planned brief maintenance as the project history data issues are more complex than we initially thought. We are making sure we fully understand the issues so we can correct them with minimum disruption. Until then some users may experience missing story history. We'll leave this incident open and provide updates as we have them.
Jan 29, 02:21 UTC
Update - Though a database issue was corrected earlier, we plan a brief maintenance from 9:15 - 10:15pm (MST) to resync Project Histories for a few affected projects. There will be no down-time, however the affected projects will need to be reloaded. We will also continue to analyze the earlier issue so we can prevent it in future.
Jan 28, 20:13 UTC
Monitoring - Users may have experienced error messages and possibly data loss for a few minutes starting at 11:40 Mountain time. The issue has been resolved and we are monitoring and investigating further to make sure no more incidents occur.
Jan 28, 19:06 UTC
Jan 27, 2016

No incidents reported.