---
title: "Public probes | Grafana Cloud documentation"
description: "Public probes Public probes are probes operated by Grafana Labs in distributed locations around the world. They run tests against your targets and report the results to Grafana Cloud."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

# Public probes

Public probes are [probes](/docs/grafana-cloud/testing/synthetic-monitoring/introduction/#probes) operated by Grafana Labs in distributed locations around the world. They run tests against your targets and report the results to Grafana Cloud.

Running tests from different regions can reveal performance and availability issues that are specific to a location. You can choose from public probes in AMER, EMEA, and APAC.

You can also set up [Private probes](/docs/grafana-cloud/testing/synthetic-monitoring/set-up/set-up-private-probes/) in Synthetic Monitoring.

If you need to allow access through your firewall, refer to [source IP addresses for allow-listing](/docs/grafana-cloud/account-management/allow-list/).

## Public probe locations

You can find a list of public probes and your private probes by going to **Testing & synthetics > Synthetics > Probes**.

The following tables list public probe locations, countries, and cloud providers by region.

### The Americas (AMER)

Expand table

| Location         | Country | Cloud Provider |
|------------------|---------|----------------|
| Calgary          | CA      | AWS            |
| Montreal         | CA      | AWS            |
| North California | US      | AWS            |
| North Virginia   | US      | AWS            |
| Ohio             | US      | AWS            |
| Oregon           | US      | AWS            |
| São Paulo        | BR      | AWS            |

### Europe, Middle East, Africa (EMEA)

Expand table

| Location  | Country | Cloud Provider |
|-----------|---------|----------------|
| Cape Town | ZA      | AWS            |
| Frankfurt | DE      | AWS            |
| London    | UK      | AWS            |
| Paris     | FR      | AWS            |
| Spain     | ES      | AWS            |
| Stockholm | SE      | AWS            |
| UAE       | AE      | AWS            |
| Zurich    | CH      | AWS            |

### Asia-Pacific (APAC)

Expand table

| Location  | Country | Cloud Provider |
|-----------|---------|----------------|
| Hyderabad | IN      | AWS            |
| Jakarta   | ID      | AWS            |
| Mumbai    | IN      | AWS            |
| Seoul     | KR      | AWS            |
| Singapore | SG      | AWS            |
| Sydney    | AU      | AWS            |
| Tokyo     | JP      | AWS            |

## Compatibility and limitations for k6 checks

Scripted checks and browser checks have specific limitations when it comes to public probes:

- For how to view the k6 channels each probe supports, refer to [Probe compatibility](/docs/grafana-cloud/observe-and-act/testing/synthetic-monitoring/create-checks/manage-k6-versions/#probe-compatibility).
- For public probe memory limits, refer to [k6 browser check limitations](/docs/grafana-cloud/observe-and-act/testing/synthetic-monitoring/create-checks/checks/k6-browser/#public-probe-memory).