<story><title>Please invest responsibly – an important message from the Coinbase team</title><url>https://blog.coinbase.com/please-invest-responsibly-an-important-message-from-the-coinbase-team-bf7f13a4b0b1</url></story><parent_chain><item><author>cgb223</author><text>&lt;i&gt;Despite the sizable and ongoing increases in our technical infrastructure and engineering staff, we wanted to remind customers that access to Coinbase services may become degraded or unavailable during times of significant volatility or volume. This could result in the inability to buy or sell for periods of time. Despite ongoing increases in our support capacity, our customer support response times may be delayed, especially for requests that do not involve immediate risks to customer account security. You can read more in our Coinbase User Agreement.&lt;/i&gt;&lt;p&gt;This is the problem they should be solving, not avoiding with blog posts</text></item></parent_chain><comment><author>kinkrtyavimoodh</author><text>Because we all know that an entire company can, at a given time, either write blog posts or solve infrastructural issues, never both.</text></comment>
<story><title>Please invest responsibly – an important message from the Coinbase team</title><url>https://blog.coinbase.com/please-invest-responsibly-an-important-message-from-the-coinbase-team-bf7f13a4b0b1</url></story><parent_chain><item><author>cgb223</author><text>&lt;i&gt;Despite the sizable and ongoing increases in our technical infrastructure and engineering staff, we wanted to remind customers that access to Coinbase services may become degraded or unavailable during times of significant volatility or volume. This could result in the inability to buy or sell for periods of time. Despite ongoing increases in our support capacity, our customer support response times may be delayed, especially for requests that do not involve immediate risks to customer account security. You can read more in our Coinbase User Agreement.&lt;/i&gt;&lt;p&gt;This is the problem they should be solving, not avoiding with blog posts</text></item></parent_chain><comment><author>linkregister</author><text>I agree they should solve the problem. It&amp;#x27;s pretty embarrassing.&lt;p&gt;Do you think it might be reasonable that they do both? The time to publish a blog post is probably about 4 employee-hours, including management review. Getting more servers, provisioning them, adding them to pools, rebalancing, and deploying code takes more time and engineers.</text></comment>