Why 21YunBox Pricing Contact Log in
Talk to an expert Test your site in China

Does PRTG Work in China? Self-Hosted vs Hosted Monitor, ICP & PIPL

PRTG is on-premises software — run it inside the mainland and your monitoring data stays in-country. The compliance lines are a publicly exposed console (ICP) and PRTG Hosted Monitor's offshore AWS servers (PIPL cross-border). A compliance-first look at both.

Does PRTG work in China?

It depends which PRTG you mean. The self-hosted PRTG core server runs wherever you install it, so deploy it inside the mainland and your monitoring data stays in-country — one of the cleaner tools to keep compliant. The line gets crossed two ways: a console opened to the public mainland internet, or PRTG Hosted Monitor, whose offshore AWS servers pull your data out of China.

Paessler's own manual draws the split: with PRTG on premises “the PRTG core server and local probe run within your network,” whereas with Hosted Monitor “we at Paessler run the PRTG core server and hosted probe for you” on “AWS servers in the region of your choice” — a region setup “automatically selects… closest to your location from our available regions,” none of them inside mainland China. Keep monitoring in-country and residency is yours to answer; send it to the hosted cloud and your users' and devices' data becomes a cross-border transfer PIPL governs. And a PRTG console you expose to the mainland public is internet information service that needs an ICP filing. The table below pairs Paessler's wording with the rule each path triggers.

This is a risk map, not a verdict — whether PRTG trips ICP or a cross-border transfer turns on where you host it, who reaches the console, and what the sensors capture. Our China team can map your exposure with you →

Compliance snapshot

  • ✓ Run self-hosted PRTG inside China and your monitoring data stays in-country
  • ! A PRTG console exposed to the public mainland internet needs an ICP filing
  • ! Device IPs, hostnames and metrics can be personal data under PIPL
  • ✕ PRTG Hosted Monitor runs on offshore AWS regions — that data leaves the mainland
  • ! Paessler publishes no mainland-China region, so there is no in-country hosted option
Get a compliance assessment
We'll map which parts of your PRTG setup stay in-country — and which cross the border

What PRTG's own documentation says about China

FactPrimary source
Self-hosted PRTG runs wherever you install it — including inside China. Paessler's manual states that with PRTG on premises “the PRTG core server and local probe run within your network.” Put that core server on infrastructure inside the mainland and the data it gathers need never leave the country — so for the self-hosted product, data residency is a deployment choice you control, not something the vendor decides for you. Paessler PRTG Manual — Using PRTG hosted by Paessler (manuals.paessler.com), retrieved 2026-10-07
PRTG Hosted Monitor is the opposite — Paessler runs it for you, in the cloud, offshore. In Paessler's words, “Hosted by Paessler” means “we take over the hosting for you” on “AWS servers in the region of your choice,” and at setup it “automatically selects the region closest to your location from our available regions.” Paessler publishes no mainland-China region among them (inference from its documentation), so a China deployment that reports to Hosted Monitor sends its monitoring data to servers outside the mainland — a cross-border transfer of personal information under PIPL (notice, separate consent and a transfer mechanism, Articles 38–43). Paessler PRTG Hosted Monitor FAQ (paessler.com), retrieved 2026-10-07; PIPL Articles 38–43
What PRTG's sensors capture is the data that puts it in scope. Through its auto-discovery and sensors PRTG records device IP addresses, hostnames, traffic and performance metrics — detail that, tied to identifiable people or to critical systems, can be personal or operational data under China's rules. Where it lives then matters: held on an in-country core server it stays in the mainland; routed to an offshore instance it becomes a cross-border transfer, and for a critical information infrastructure operator or large-volume handler, personal information collected in China must be stored in the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)). Paessler PRTG (paessler.com), retrieved 2026-10-07; PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)
Whether PRTG needs an ICP filing depends on how you expose it, not on the software. A PRTG web console reached privately inside an organization raises no filing question. But a monitoring console or status page served to the public over a mainland domain is providing internet information service, which under China's ICP regime (State Council Order No. 292; MIIT Order No. 33) requires an ICP filing bound to an in-country hosting resource — something neither a self-managed offshore box nor an offshore cloud instance can hold. State Council Order No. 292; MIIT Order No. 33 (China ICP regime), as explained by 21YunBox; retrieved 2026-10-07

Sources verified by the 21YunBox compliance team on 2026-10-07.

For a mainland-China audience, the first question about PRTG is not how quickly a dashboard paints — it is where the software runs and where the data it gathers is allowed to live. And PRTG does not have one answer, because it is not one product. The self-hosted PRTG core server runs wherever you install it, so putting it on infrastructure inside the mainland keeps your monitoring data in-country; PRTG Hosted Monitor, by contrast, is a cloud service Paessler runs for you on offshore AWS infrastructure, which pulls that same data back out of China. The compliance exposure — an ICP filing for a publicly exposed console, a PIPL cross-border transfer for anything sent to the hosted cloud — follows directly from which of those you choose.

Paessler PRTG Hosted Monitor FAQ page stating that Hosted Monitor is hosted on AWS servers in the region of your choice and automatically selects the region closest to your location from available regions, with no mainland-China region
Paessler's own Hosted Monitor FAQ: “Hosted by Paessler” means “we take over the hosting for you,” on “AWS servers in the region of your choice,” with setup that “automatically selects the region closest to your location from our available regions” — none of them inside mainland China. Source: paessler.com/prtg-hosted-monitor/faq

PRTG in China at a glance

What decides it In PRTG's own terms
Where it runs On-premises: “the PRTG core server and local probe run within your network” — you pick the location, the mainland included. Hosted Monitor: “we at Paessler run the PRTG core server and hosted probe for you,” in the cloud.
Where Hosted Monitor sits On “AWS servers in the region of your choice”; setup “automatically selects the region closest to your location from our available regions.” Paessler lists no mainland-China region.
Serving the public A console used internally raises no filing question; one exposed to the public mainland internet is internet information service and needs an ICP filing tied to an in-country host.
Your monitoring data Device IPs, hostnames, traffic and performance metrics can be personal or operational data. On an in-country core server it stays in the mainland; via Hosted Monitor it crosses the border.
Is it reachable? Self-hosted, the console lives on your own network — reaching it is a LAN or VPN question, not a public-internet one. Hosted Monitor's console is offshore, reached across the border.

Two products, one name — and two different China questions

PRTG ships in two shapes, and they land on opposite sides of the compliance line. The classic product is software you install and operate yourself: in Paessler’s words, with PRTG on premises “the PRTG core server and local probe run within your network.” The newer one, PRTG Hosted Monitor, is a managed cloud service — “we at Paessler run the PRTG core server and hosted probe for you.” Everything that follows about ICP and cross-border data depends on which of these you are running, so the honest answer to “does PRTG work in China” has to start by naming the deployment.

Self-hosted inside China — your data stays where you put it

Because the self-hosted core server runs on your own infrastructure, you decide where it lives. Install it on a mainland server and the IP addresses, hostnames and performance data its sensors collect stay in the country; nothing about running PRTG this way forces a cross-border transfer. That makes self-hosted PRTG one of the more straightforward tools to keep compliant — with one caveat that is about exposure, not the software. A PRTG web console reached privately by your own staff raises no filing question. Publish that console or a status page to the public over a mainland domain, though, and you are providing internet information service, which turns on an ICP filing under State Council Order No. 292 and MIIT Order No. 33, bound to an in-country hosting resource. Keep the console internal and in-country, and PRTG sits comfortably on the right side of both questions.

PRTG Hosted Monitor — the data leaves the mainland

Hosted Monitor inverts the picture. Paessler runs the instance for you on “AWS servers in the region of your choice,” and at setup it “automatically selects the region closest to your location from our available regions” — a list that, by Paessler’s own documentation, includes no region inside mainland China. So a China deployment reporting to Hosted Monitor ships its monitoring data to an offshore instance. Under China’s Personal Information Protection Law that is a cross-border transfer: you — the handler, not Paessler — must give notice, obtain separate consent, and clear one transfer mechanism (a CAC security assessment, the CAC standard contract, or certification). If you are a critical information infrastructure operator or a large-volume handler, personal information collected in China has to be stored in the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)) — a residency duty an offshore AWS region cannot meet.

This is a risk map, not a verdict: whether PRTG trips an ICP filing, a cross-border transfer, or neither turns on where you host it, who can reach the console, and what the sensors actually record — worth settling with counsel before you build.

Where 21YunBox fits — a compliant overlay, not a migration

Keep running PRTG exactly as you do. Where a public-facing China presence is involved — a status page, a customer-facing dashboard, an exposed console — we add the piece your own deployment or an offshore cloud instance cannot: compliant, ICP-filed delivery from inside the mainland, set in front of your existing origin, with no rebuild and no second codebase. Our China team works through which parts of your monitoring stack can stay in-country and which cross the border, assesses your PIPL cross-border and data-residency position for your entity and data volumes, and stands up the in-country, ICP-filed delivery a lawful mainland presence requires — while PRTG keeps running wherever you already run it.

Get a compliance assessment →


Related reading:

Frequently Asked Questions

If we run PRTG on our own servers in China, is that a problem?

Not inherently. Paessler's on-premises model puts “the PRTG core server and local probe” inside your own network, so if you install it on infrastructure located in the mainland, the monitoring data it collects stays in the country — you are not making a cross-border transfer simply by running it. Two things still deserve a check with counsel: whether anything the sensors capture counts as personal information under PIPL, and whether the web console is reachable by the public mainland internet, which would raise the ICP question. Keep it internal and in-country and PRTG is one of the cleaner tools to run.

Does PRTG Hosted Monitor keep our data in mainland China?

No. PRTG Hosted Monitor is Paessler's cloud product — “we take over the hosting for you” on “AWS servers in the region of your choice,” with setup selecting “the region closest to your location from our available regions.” Paessler publishes no mainland-China region, so a China deployment reporting to Hosted Monitor sends its monitoring data to an offshore instance. Under PIPL that is a cross-border transfer of personal information, requiring notice, separate consent and a transfer mechanism — and for a CIIO or large-volume handler, data collected in China has to be stored in the mainland, which an offshore instance cannot satisfy.

Can 21YunBox help us run PRTG compliantly in China?

Yes. Our China team can map which parts of your PRTG setup stay in-country and which cross the border — assessing your PIPL cross-border and data-residency exposure for your entity, data volumes and users, plus the ICP question if you expose a console publicly — then stand up the ICP-filed, in-country delivery a public mainland presence requires, in front of the stack you already run. Get in touch to work through your specific deployment.

ARTICLES RELATED TO PRTG

Make Your Site Work inside the Great Firewall of China

Enter your information, and our staff will assist you in getting a 21YunBox account for China.

Make Your Site Work Within the Great Firewall of China
Make Your Site Work Within the Great Firewall of China

By clicking 'Get Started', I also agree to 21YunBox's Terms of Service and Privacy Policy.