Runscope Developer Guide

Map of Runscope Service Regions

Service Regions

Runscope operates servers in different regions around the world to reduce the amount of time it takes to execute requests. When you make a request to runscope.net, your traffic will be sent to the Runscope gateway server closest to your client. If there is a service interruption in the closest region, your request will automatically be sent to another region that's operating normally.

You can send your request to a Runscope server in a specific service region by adjusting the URL to include the code for the target region. This can be useful if you want to use the Runscope server closest in geographic proximity to the API you're calling.

For example:

curl -X POST -d "hello=world" https://api-yourapihere-com-bucket_key.runscope.net/post?fizz=buzz
curl -X POST -d "hello=world" https://api-yourapihere-com-bucket_key.us1.runscope.net/post?fizz=buzz
curl -X POST -d "hello=world" https://api-yourapihere-com-bucket_key.au1.runscope.net/post?fizz=buzz

To create region-specific Runscope URLs from the dashboard, use the URL Helper.


Available Regions

Runscope currently operates servers in these regions:

Region Code Location Provider Hostname
  Automatic (default)   runscope.net
us1 US East (Northern Virginia) Amazon Web Services us1.runscope.net
us2 US West (Northern California) Amazon Web Services us2.runscope.net
us3 US Midwest (Chicago) Rackspace us3.runscope.net
us4 US Texas (Dallas) Rackspace us4.runscope.net
eu1 Europe (Ireland) Amazon Web Services eu1.runscope.net
sg1 Singapore Amazon Web Services sg1.runscope.net
au1 Australia (Sydney) Amazon Web Services au1.runscope.net
br1 Brazil (São Paulo) Amazon Web Services br1.runscope.net

Which service region should I use for my API calls?

When possible, use the standard runscope.net domain without specifying a service region. This way, your requests will be served by the nearest service region, no matter where your client is located. If there's a service interruption in the nearest region, your request will automatically be rerouted to another region.

Depending on your traffic pattern, you may find it's faster to use the service region that is closest in geographic proximity to the API you are calling.

Everything is going to be 200 OK

Sign Up — Free