It really depends on what app you're running. Let's look at this from the point of view of the user of your app. Your user sees a 2Mbps (assuming you meant Mbp

It really depends on what app you're running. Let's look at this from the point of view of the user of your app. Your user sees a 2Mbps (assuming you meant Mbps not MB/s) connection. That's a very narrow band for a Web server. Typically, Web servers push much more data to the users than they receive (GET vs POST ratio). The 16Mbps upload (again from the users' pov) matters little unless your users upload much more than they download from your app. Think of it this way: most content from your Web server is served out to your users using the 2Mbps (GET). This is why cable/DSL is not well suited for running Web servers. But if you still insist on hosting this yourself ask Comcast for an increase of the upload band (to least 10Mbps). Let's do some rough math: 640kb (~80KB average size) * 10000 (reqs) / 3600 (1hr) = 1.7Mb/s or 2.0Mbps including protocol overhead Let's say your app goes viral and assume you get 10000 hits in a period of 10 minutes: 640kb (~80KB average size) * 10000 (reqs) / 600 (10mns) = 10Mb/s or ~11Mbps including protocol overhead You might be able get away with this if you offload all static files to a CDN. Regards Joe