GitHub by the Hour: API Limits, OAuth Callbacks, Release Pages

Most GitHub work never needs a proxy. The exceptions are small and specific: you want to see what an unauthenticated client gets from the REST API when it arrives from a fresh address, you want to walk an OAuth or GitHub App flow from a phone network instead of your office fiber, or you want to check that a release page and its assets load cleanly for a US visitor on cellular. None of that takes a month. HourlyProxies gives you one dedicated US 4G or 5G line, in hardware we own, for $2 or $3 for the first two hours, then by the hour up to four. The meter starts when you say so and stops on its own.

Where the address matters on GitHub

GitHub applies a per-address allowance to unauthenticated API calls and a per-account allowance to authenticated ones. If you build tooling that other people will run without a token, the honest way to see their experience is to make the same calls from an address that is not yours and read the rate limit headers that come back. A carrier line carries only your traffic, so the counter you watch is the one your code is filling, not one shared with a stranger on a cloud box.

The same goes for anything GitHub serves to anonymous visitors: public repositories, Pages sites, release downloads, raw file links. A check from a US mobile line tells you how a developer on a phone in Chicago sees your README, whether a large release asset starts quickly, and whether a redirect chain behaves the same as it does from your desk.

OAuth and GitHub App flows from a phone network

OAuth callbacks are where a surprising number of integrations break. The redirect lands on a URL that resolves differently from outside, a cookie is scoped to the wrong host, or a device-flow prompt assumes a desktop screen. Route a test browser through the line, start the authorization from the GitHub side, and follow the redirect back to your app the way a user on T-Mobile would. The whole loop takes minutes, and two hours leaves room to fix and retry.

Use your own test account and your own app registration. The point is to observe the flow from a different network, not to appear as someone else.

Webhooks and Actions runners

If you run a self-hosted Actions runner or receive webhooks behind an IP allowlist, a mobile line is a cheap outside vantage point. Confirm that the allowlist really rejects an unknown address, that your public endpoint answers on both IPv4 paths your users will hit, and that a redelivered webhook reaches the handler. You are testing your side of the connection, which is exactly what the address is for.

Carrier addresses change when the modem reconnects, so if you add the line to an allowlist for a test, expect to update it after a rotation. Sticky sessions hold the address as long as the carrier keeps it.

What the hourly plan looks like

Buy in the dashboard at meter.hourlyproxies.com, in the app or in the Telegram bot. 4G is $2 for the first two hours and $2 per extra hour; 5G is $3 and $3. Four hours is the most one purchase holds, it never renews, and if the job stretches across the day the hours you already paid count toward the day price of $5 on 4G or $6 on 5G. You get HTTP(S) and SOCKS5 endpoints, unlimited data under a fair-use rule, free rotation and a free move between our eight cities.

Pick a city close to the users you care about: New York, Boston, Chicago, Houston, Phoenix, Los Angeles, Miami or North Carolina. Carrier choice is AT&T, T-Mobile or Verizon, subject to stock in that city.

• Two hours is enough for an OAuth loop, a webhook test and a release check
• Read GitHub's rate limit headers from a clean address
• HTTP(S) or SOCKS5, whichever your tooling prefers
• Nothing renews; the meter simply stops

What this is not for

A proxy does not raise GitHub's limits, revive a suspended account or let you run several accounts as if they were different people. Those break GitHub's terms and we will not help with them. Stay on your own accounts, keep automated requests paced, and treat the line as a second window onto the service rather than a way around it.

Setting up a GitHub proxy on HourlyProxies

1. Open the dashboard, choose a city and carrier, and buy two hours on 4G or 5G.
2. Set the HTTP or SOCKS5 endpoint in your test browser, curl or SDK.
3. Call the GitHub API once and check the rate limit headers to confirm you are on the new address.
4. Run your OAuth, webhook or release test and note anything that differs from your desk.
5. Add an hour if you need it; otherwise let the meter run out.

GitHub proxy questions