Coreload: GitHub Actions runners Coreload Acceptable Use Policy

Last updated: 6 November 2026.

This policy is part of the Coreload Terms of Service. It covers everything your jobs, sandboxes, installations and keys do, and anyone you let use them.

Not allowed

You will not use Coreload, or let anyone use it, to:

Network limits

Outbound traffic is limited per VM and per machine: the number of connections, new connections per second, new destinations per minute and bandwidth. The limits are not published and may change. Outbound mail ports are refused, and so are mining-pool and IRC ports and DNS other than the resolver we provide. Work that needs more must be agreed with us in writing first.

Shared addresses

A job's outbound traffic leaves from addresses that other customers share, and that can change without notice. Do not put them in an IP allow list, and never treat traffic from them as proof that it is yours.

What happens if this policy is broken

We may stop the job, suspend the organization, installation or key at once, and end the service, as the Terms of Service say. Where the law requires it, we report illegal content and activity to the authorities.

Reporting abuse

Report abuse coming from Coreload to hello@coreload.com, and a security problem in Coreload to hello@coreload.com. Tell us what you saw, when, and from which address.