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
Braintree API Operational
GitHub Operational
AWS cloudFront Operational
AWS route53 Operational
SendGrid SMTP Operational
AWS s3-us-standard Operational
SendGrid Event Webhook 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
May 31, 2016

No incidents reported today.

May 30, 2016

No incidents reported.

May 29, 2016

No incidents reported.

May 28, 2016

No incidents reported.

May 27, 2016

No incidents reported.

May 26, 2016

No incidents reported.

May 25, 2016

No incidents reported.

May 24, 2016

No incidents reported.

May 23, 2016

No incidents reported.

May 22, 2016

No incidents reported.

May 21, 2016
Completed - The scheduled maintenance is complete a little early as all went well. As always, do email tracker@pivotal.io with any questions or issues.
May 21, 02:15 UTC
In progress - The scheduled maintenance is in progress as planned.
May 21, 02:04 UTC
Scheduled - Tracker will be down for approximately 30 mins for scheduled server maintenance.
May 20, 21:09 UTC
May 20, 2016
Resolved - Customers shouldn't have further issues accessing Analytics charts and reports or accessing related API endpoints. We're continuing to assess the issue so we can prevent similar occurrences in future. As always, please email tracker@pivotal.io if you have questions or need help.
May 20, 16:18 UTC
Monitoring - Analytics page load performance should be back to normal. We believe the underlying database issues causing the poor performance have been resolved.
May 20, 02:13 UTC
Identified - Some customers are experiencing issues with Analytics pages loading slowly or failing to load their charts and reports. We're working to resolve the issue but it may take several hours before affected customers see an improvement. Apologies for the inconvenience meanwhile.
May 19, 22:58 UTC
May 18, 2016

No incidents reported.

May 17, 2016

No incidents reported.