RegionHop

A DIFFERENT PLACE TO START

Same request.
Different place.

See how your API behaves from around the world. Add a location to the URL, send your usual request, and get the response back.

Start with the API Try a request

Invited? Sign in and create your own API key.

ONE REQUEST, ANOTHER LOCATIONExample
Your clientcurl, Postman, code
ParisCDG
Your APIThe original target
Try the proxy
curl --include 'https://regionhop.com/CDG/https://httpbingo.org/anything' \
  -H "X-RegionHop-Key: $REGIONHOP_KEY" \
  -H 'Content-Type: application/json' \
  --data-binary '{"hello":"world"}'

Set REGIONHOP_KEY in your terminal. Changing this example does not send a request.

THE OBSERVED NETWORK

Global locations, with health you can inspect.

Hourly checks of the catalog's existing nodes.
See live locations

FITS THE WAY YOU ALREADY WORK

A small change
to your existing request.

Keep your HTTP client, payload, and workflow. RegionHop handles the regional hop.

  1. 01

    Choose a location

    Pick an observed colo such as CDG, or use a broad region hint such as weur. Strict colo routes verify the node before sending.

  2. 02

    Put it in front of your URL

    Prefix the target with https://regionhop.com/CDG/ and add your X-RegionHop-Key header. Send the method and body your API expects.

  3. 03

    Read the response

    The target's status and body come back directly. RegionHop headers tell you the observed colo and how long the request took to reach response headers.

TWO WAYS TO ASK

Pass it through. Or look closer.

01 / PROXY

Your API's response, intact.

Use a URL prefix to keep the target's request and response shape. JSON, uploads, and streamed responses work with your existing HTTP tools.

/{destination}/https://your-api.example/pathUse proxy mode
02 / PROBE

A report around the request.

Send the URL, destination, and payload as JSON. Get location details, timings, target status, headers, and a captured response body in one report.

POST /probeUse probe mode

Know what the location means.

Colos are observed through a separate Cloudflare trace request. They are not proof of your target's exact network egress. Strict routes check before sending and do not silently fall back to another colo.

How location selection works ↗

Built around your API.

RegionHop runs on Cloudflare Workers and Durable Objects. Target payloads and responses are not persisted by RegionHop. Use it directly from curl, Postman, or your application.

Read the behavior and limits ↗

Make your next request
from somewhere else.

Open the API reference