Start Testing Now BlazeMeter University Submit a Support Request My Support Tickets

Whitelisting BlazeMeter Engines

Avatar
BlazeMeter Support
  • Updated

To ensure BlazeMeter's cloud engines can communicate with your application server, you may need to whitelist the relevant IP ranges.  Here you'll find the available CIDRs (Classless Inter-Domain Routing) for the IPs used by BlazeMeter cloud engines.

While this document only pertains to engines, if you want more information about whitelisting other BlazeMeter addresses, please refer to our master guide Whitelisting BlazeMeter.

NOTE: Our providers each require a wide range of IPs to be whitelisted in order to use them for engines.  If you find these ranges to be too wide to fit your security standards, then please consider the alternative options we provide for Running Performance Tests Behind Your Corporate Firewall.

Debug Test Engines

35.245.251.194 35.245.232.79
35.245.160.5 34.64.185.248
35.194.77.139 35.198.210.225
35.194.88.224 35.244.89.90
35.245.24.75 35.203.78.93
35.221.19.213 35.234.97.23
35.245.0.140 34.76.64.195
35.245.200.243 35.246.9.61
35.245.217.101 35.231.2.168
35.245.242.163 35.236.93.4
34.86.94.3
 34.82.42.213
35.245.162.86
 34.86.129.102
34.86.55.231 34.86.129.100
34.86.18.245 34.86.129.101
34.86.167.17  
35.199.23.208  
 
AWS:

Downloadable list of AWS Engines in JSON format

Find the AWS EC2 Region code<>Name mapping chart here.

GCE (Google Compute Engines):

Downloadable list of GCE Engines in JSON format

For more information, see Where can I find Compute Engine IP ranges? (in the Google Cloud documentation).

Find the Google Cloud Region code<>Name mapping chart here.

Azure:

Downloadable list via this link (XML format).

Find the Azure Region code<>Name mapping chart here.

 

Functional GUI Testing Location IPs:


US East (Virginia) - Default Location

CIDR: 34.86.129.64/26
US West (Oregon) 34.82.137.166
35.247.48.254
35.197.44.138
34.83.234.170
34.82.232.108
35.185.206.63
34.83.173.62
34.83.79.24
EU West (London) 35.189.104.226
35.242.133.63
35.246.94.188
35.230.145.198
35.234.150.228
35.234.156.180
35.234.138.9
35.242.129.55
Have more questions? Submit a request

6 Comments

Date Votes
  • 0
    Avatar
    Eduardo Tergolina Filho

    I just had our network configured to receive calls from the 6 IPs listed here for Blazemeter SandBox. When I tried running the test, the loadgenerator IP was NOT any of the ones listed. And then, for my surprise, when I looked at this page today, the SandBox IPs were REMOVED from the page content. Since I'm working on a PoC for Blazemeter, please reply to this comment ASAP. Thanks.

    Edited by Eduardo Tergolina Filho
  • 0
    Avatar
    Tommy Riddle

    hi,

    I want to know if BlazeMeter connects over port 443? Please confirm

  • 0
    Avatar
    Matthew Andrus

    Yes, Blazemeter utilizes SSL port 443

  • 0
    Avatar
    Marco Carcangiu

    Hi,

     

    I am having same issue as in Eduardo's comment above.

    Eduardo Tergolina Filho did you solve this issue?

     

    Thanks

     

    Marco

  • 0
    Avatar
    Rauf Abdul
     

    Hi,

    Why do we have Azure and AWS locations in Blazemeter. Will it make any difference in response time or anything else, if we run test.

     

    Regards,

    Rauf

  • 0
    Avatar
    Carlos Moro

    How is it useful to tell us to whitelist the entire AWS IP ranges (Downloadable list in JSON format)? That would open up our network to anyone running in AWS, not only BlazeMeter agents. That is a huge security risk. I'm surprised this article is even suggesting that.

Article is closed for comments.