Skip to main content
Multi-Region Tests allow you to run the same load test from multiple geographic locations at once. This helps understand how your application performs for users around the world and identify regional performance differences.

​
Key Benefits

Global Performance Visibility

See how latency varies across continents and identify regions with poor performance.

Simultaneous Execution

All regions start testing at the same time for accurate comparison under identical conditions.

Aggregated Metrics

View combined statistics across all regions plus detailed per-region breakdowns.

Fastest/Slowest Detection

Automatically identifies best and worst performing regions for quick analysis.

​
Available Regions

Tests can run from locations across six continents:
Available countries may vary based on proxy provider availability. The country selection dialog shows only currently available locations.

​
How to Create a Multi-Region Test

1

Create a Test Plan First

Multi-region tests use existing Test Plans. If you don’t have one, create it from the New Test wizard first.
2

Open Multi-Region Tests

Navigate to Load Testing → Multi-Region Tests.
3

Click New Multi-Region Test

Click the New Multi-Region Test button.
4

Enter Test Name

Provide a descriptive name (e.g., “Global API Performance Q1 2024”).
5

Select Test Plan

Choose the test plan to run across all regions.
6

Select Regions

Click on countries to select them. You must select at least 2 regions.
7

Start Test

Click Start Test. Tests begin simultaneously in all selected regions.
Running tests from many regions simultaneously consumes more resources. Consider your load testing quota when selecting region count.

​
Test Status Types

​
Multi-Region Run List

The main page shows all multi-region test runs in a table:

​
Stats Cards

Quick overview showing:
  • Total Runs: Number of multi-region tests executed
  • Successful: Tests where all regions passed
  • Running: Currently executing tests
  • Regions Used: Unique regions tested across all runs

​
How to View Multi-Region Results

1

Find the Test

Locate the multi-region run in the list.
2

Click to Open

Click the arrow icon or anywhere on the row to open details.
3

Review Aggregated Metrics

The header cards show combined statistics across all regions.
4

Compare Regional Performance

The latency comparison chart ranks regions by response time.
5

Drill Into Individual Regions

Click View Test Details on any region card to see full test results.

​
Detail Page Components

​
Aggregated Metrics Cards

​
Latency Comparison Chart

Horizontal bar chart comparing response times:
  • Sorted by latency (fastest at top)
  • Color-coded by performance:
    • Green (< 100ms): Excellent
    • Yellow (100-200ms): Good
    • Orange (200-500ms): Acceptable
    • Red (> 500ms): Needs improvement
  • Shows status for incomplete or failed regions

​
Region Cards

Each region displays:
  • Country flag and name
  • Status badge (Success, Failed, Running, Pending)
  • Latency: Average response time
  • Success Rate: Percentage of successful requests
  • Requests: Total requests from this region
  • Fastest/Slowest badges: Highlights best and worst performers
  • Link to full test results (for successful tests)

​
Live Progress Tracking

While tests are running:
  • Progress bar shows completion percentage
  • Status updates automatically every few seconds
  • Region cards update as each test completes
  • No manual refresh needed

​
How to Cancel a Running Test

1

Find the Running Test

Locate the test with “Running” status in the list.
2

Click Cancel

Click the X button in the actions column.
3

Confirm

The test is cancelled. Completed regions retain their results; pending regions are stopped.

​
Use Cases

​
Global CDN Validation

Test your API through CDN edge locations to verify caching and routing work correctly worldwide.

​
Regional Compliance

Verify that data residency requirements are met by testing response content from specific regions.

​
Performance Baseline

Establish baseline latency expectations for users in different geographic areas.

​
Incident Response

During outages, quickly test from multiple regions to identify if issues are global or regional.

​
Troubleshooting

  • Check the error message on the region card
  • The target server may block requests from certain countries
  • Network issues or rate limiting at specific locations
  • Try running a single-region test from that location to debug
  • Proxy resources may be temporarily unavailable
  • Try reducing the number of selected regions
  • Check if other tests are consuming available proxies
  • Expected for geographically distributed servers
  • Check if your server has regional deployments
  • Consider CDN or edge caching for global performance
  • Country may be temporarily unavailable
  • Proxy provider may not support that location
  • Try again later or select alternative nearby regions
  • Some regions succeeded, others failed
  • Review individual region cards for failure reasons
  • Partial results are still valuable for successful regions

​
FAQ

You can select any number of available regions (minimum 2). However, more regions consume more resources and may take longer to complete.
Yes. The selected test plan’s configuration (URL, method, load pattern, thresholds) is identical across all regions. Only the geographic origin differs.
Individual region tests appear in Test Results and can be compared using the standard comparison feature.
Physical distance to your server is the primary factor. A server in the US will naturally have higher latency from Asia than from Canada. Consider deploying to multiple regions or using a CDN.
Tests are dispatched to all regions within seconds of each other. Minor timing differences (1-5 seconds) may occur due to proxy initialization, but this doesn’t affect comparison validity.
Direct scheduling is not available in the UI. Use the API to integrate multi-region tests into CI/CD pipelines for automated execution.