# Network and egress

> Where Skipbox VMs run, what they can reach, what is blocked, and what that means for latency and allowlists.

## Region

Every job runs in **Helsinki, Finland**. There is no other region. A job that talks to servers far from Europe spends longer on each request, so a step that makes many small requests to one far away can take longer than on GitHub.

## Inbound

Nothing on the internet can connect to a job's VM. A job can't serve a port to the outside, so a test that needs a public webhook to reach it won't work.

## Outbound

The internet is open, as on GitHub-hosted runners, except outbound mail: TCP port 25 is blocked. Send test mail through your mail provider's HTTP API instead.

Traffic isn't charged.

## Addresses

Skipbox has no fixed outbound address, so a firewall that allows only listed IP addresses can't list Skipbox. Reach such a service through a token or a VPN step instead.

## Docker images

VMs pull images from Docker Hub without logging in. Docker Hub limits anonymous pulls per address; if a job hits that limit, log in with `docker/login-action` first.

```yaml
      - uses: docker/login-action@v3
        with:
          username: ${{ secrets.DOCKERHUB_USERNAME }}
          password: ${{ secrets.DOCKERHUB_TOKEN }}
```

Updated 2026-11-09 · https://docs.skipbox.dev/network