Monitoring - One of Quantopian's third-party service providers, Cloudflare, announced a security incident last night. It is highly unlikely that this incident adversely impacted Quantopian, but we are taking some precautionary steps out of an abundance of caution. Our response to this incident is documented in detail on our blog at https://blog.quantopian.com/cloudbleed-bug.
Feb 24, 15:49 EST
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
Feb 26, 2017

No incidents reported today.

Feb 25, 2017

No incidents reported.

Feb 23, 2017

No incidents reported.

Feb 22, 2017
Resolved - This incident has been resolved.
Feb 22, 16:49 EST
Monitoring - For a period of time this morning the Robinhood integration replied with a variety of failure errors. Some algorithms had their orders rejected/cancelled but recovered to keep trading. Many algorithms were unable to handle these failure replies and are unable to place any orders for the rest of the day. Authors of algorithms that did not recover will be receiving emails shortly.

If your algorithm is down for the day, and you need your algorithm to trade today, you need to stop and restart it. Please note that, as always, this still depends on Robinhood's service status.

If you do nothing, your algorithm will resume trading tomorrow as-normal.
Feb 22, 11:36 EST
Investigating - We are seeing a very high error rate with our Robinhood integration. Some orders are being rejected/cancelled, and some algorithms are not able to connect successfully to Robinhood.
Feb 22, 10:43 EST
Feb 21, 2017

No incidents reported.

Feb 20, 2017

No incidents reported.

Feb 19, 2017

No incidents reported.

Feb 18, 2017

No incidents reported.

Feb 17, 2017

No incidents reported.

Feb 16, 2017

No incidents reported.

Feb 15, 2017

No incidents reported.

Feb 14, 2017

No incidents reported.

Feb 13, 2017

No incidents reported.

Feb 12, 2017

No incidents reported.