# Github Actions Metrics
Information on Github hosted runners like the Azure region they run on is
necessary info when optimising CD/CI pipelines(especially network latencies and
route path bandwidth). Github does not disclose it so I did it myself.

Using this info, place the resources(DB, object storage, other instances) near
the runners are usually run.

A few pieces of info I could gather online:

- Azure doesn't provide a list of VM service endpoints like AWS
- Github-hosted Actions runners are actually Azure VMs (surprisingly, not in a
  container)
- Github is hosted in the data centre somewhere in the US, probably in the same
  data centre where Azure is present

Microsoft definitely has more points of presence than any other cloud service
providers, but there's no official list of data center endpoints to ping. If you
look at the map,

<a href="https://aws.amazon.com/about-aws/global-infrastructure/regions_az/">
<img src="image.png" style="width: 500px;">
</a>
<a href="https://datacenters.microsoft.com/globe/explore">
<img src="image-1.png" style="width: 500px;">
</a>

they're close enough. For most devs, all that matters is probably how close
their S3 buckets are to the Github Actions runners. Some AWS and Azure regions
are under the same roof, but then again, no official data.

## DATA
Updated: 2024-11-19T04:14:47.992449

| AWS Region | Avg Latency | Least |
| - | - | - |
| af-south-1 | 0.915 |  |
| ap-east-1 | 0.827 |  |
| ap-northeast-1 | 0.636 |  |
| ap-northeast-2 | 0.745 |  |
| ap-south-1 | 0.871 |  |
| ap-southeast-1 | 0.899 |  |
| ap-southeast-2 | 0.783 |  |
| ca-central-1 | 0.171 | 1 |
| eu-central-1 | 0.457 |  |
| eu-north-1 | 0.508 |  |
| eu-south-1 | 0.474 |  |
| eu-west-1 | 0.369 |  |
| eu-west-2 | 0.409 |  |
| eu-west-3 | 0.424 |  |
| me-south-1 | 0.802 |  |
| sa-east-1 | 0.548 |  |
| us-east-1 | 0.115 | 65 |
| us-east-2 | 0.166 | 18 |
| us-gov-east-1 | 0.158 | 4 |
| us-gov-west-1 | 0.319 |  |
| us-west-1 | 0.267 | 34 |
| us-west-2 | 0.317 |  |