All Systems Operational
Community Operational
Backtesting Operational
Live Trading Operational
Research Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
Error Rate
Fetching
Web Response Time
Fetching
Past Incidents
Sep 28, 2016

No incidents reported today.

Sep 27, 2016

No incidents reported.

Sep 26, 2016
Resolved - This incident has been resolved.
Sep 26, 15:21 EDT
Monitoring - We believe we have resolved the issue with an infrastructure change. Error rates are back down. We are continuing to monitor the front-end infrastructure.
Sep 26, 13:52 EDT
Identified - We've clarified that the problem exists only with the live algorithm dashboard querying the live trading database. No algorithms fell behind, no orders were interrupted, etc. However, some live trading dashboards aren't loading fully. We are continuing to investigate and evaluate solutions.
Sep 26, 12:36 EDT
Investigating - We are seeing an increase in database errors. Some live algorithm dashboards are loading slowly or with errors. We are investigating.
Sep 26, 12:14 EDT
Sep 25, 2016

No incidents reported.

Sep 24, 2016

No incidents reported.

Sep 23, 2016
Resolved - This incident has been resolved.
Sep 23, 21:28 EDT
Identified - 3rd party datasets are currently unavailable in the the research environment. We are actively working on a solution, and will post further updates here.
Sep 23, 20:23 EDT
Sep 22, 2016

No incidents reported.

Sep 21, 2016

No incidents reported.

Sep 20, 2016

No incidents reported.

Sep 19, 2016

No incidents reported.

Sep 18, 2016

No incidents reported.

Sep 17, 2016
Resolved - The expired certificate has been replaced, and research is accessible again.
Sep 17, 10:47 EDT
Identified - The issue has been identified and a fix is being implemented.
Sep 17, 09:52 EDT
Sep 16, 2016
Resolved - This incident has been resolved.
Sep 16, 16:32 EDT
Monitoring - The upstream issue at Robinhood appears to be resolved, and Robinhood live algorithms will be able to place and cancel trades again. We will continue to monitor the issue, and post an update if we see problems resurface.
Sep 16, 14:58 EDT
Identified - Our integration with Robinhood is down due to a problem at Robinhood. In the meantime, Robinhood live algorithms on Quantopian will not be able to place or cancel trades. We will update this incident as soon as we have more information.
Sep 16, 14:46 EDT
Sep 15, 2016
Resolved - The bad pricing data has now been repaired in backtesting, research, and live trading.
Sep 15, 23:15 EDT
Monitoring - Shortly before the close of trading on September 15, one of our members reported to us that he was seeing invalid pricing data for a stock in live trading.

We immediately assigned a team of engineers to investigate. They determined that the root cause was human error while recovering from bad data provided by one of our vendors on September 9 (http://status.quantopian.com/incidents/q21n3s726m40), coupled with a bug in our data ingestion code. The human error and bug caused us to improperly roll back the bad data before re-ingesting the corrected data from our vendor.

We are in the process of correcting the bad data, and we expect to be finished in time for live trading on September 16.

The impact of this incident is as follows:

1) Between September 12 and today, "history()" and pipeline returned incorrect data in backtesting, live trading, and the research environment for dates prior to September 12 for the following list of stocks: BATS, DG, DHF, DMF, DSM, EAD, EE, EOD, ERC, ERH, FICO, HPQ, HRB, IIM, IQI, LEO, MER_PRK, MER_PRP, NEE_PRC, NNA, OIA, PSA, PSA_PRA, PSA_PRC, PSA_PRD, PSA_PRS, PSA_PRT, PSA_PRU, PSA_PRV, PSA_PRW, PSA_PRX, PSA_PRY, PSA_PRZ, PSB, PSB_PRS, PSB_PRT, PSB_PRU, PSB_PRV, SCE_PRF, SCE_PRG, SCE_PRH, SCE_PRJ, SGA, VKI.

2) In addition, a large number of NYSE stocks had incorrect historical pricing data for the day of September 9 in the research environment.

Our experiences recovering from the bad data provided by our vendor on September 9 revealed a number of issues with our ability to recover from such bad data. We have carefully documented all of these issues, and we have already addressed more than half of them. We intend to fully address all of them in the near future, so that the next time we receive bad data from our vendor, we will be able to recover from it reliably, quickly, and correctly.
Sep 15, 20:15 EDT
Sep 14, 2016

No incidents reported.