{
  "$type": "site.standard.document",
  "description": "On a project involving Heroku, I was considering placing some services on Linode and accessing them from Heroku, which is hosted on AWS us-east, so I",
  "path": "/heroku-amazon-us-east-linode-latency/",
  "publishedAt": "2012-07-31T03:17:00.000Z",
  "site": "at://did:plc:bryys25pc2fnagnyxqgsglhd/site.standard.publication/3mn26bjkkmh23",
  "tags": [
    "Tools"
  ],
  "textContent": "On a project involving Heroku, I was considering placing some services on Linode and accessing them from Heroku, which is hosted on AWS us-east, so I spin up an EC2 instance in us-east as well as 1 Linode for each of their datacenters and ping each Linode from the EC2 instance. It isn't an extensive test but should give a good ballpark for anyone considering the same thing:\n\n * Newark: 9ms\n * Atlanta: 16-19ms\n * Dallas: 34-35ms\n * Fremont: 72ms",
  "title": "Latency Between Heroku (AWS us-east) and Linode"
}