Does Opsgenie Work in China? Data Residency, ICP & Cross-Border Rules
Opsgenie is cloud-only (US/EU regions, no mainland-China region, no self-host) yet stores responders' names, emails, phone numbers and alert payloads. Collected in China and landing offshore, that is a PIPL cross-border transfer and a residency problem redaction cannot close.
Does Opsgenie work in China?
Opsgenie runs only on Atlassian's offshore cloud (US and EU regions, no mainland-China region and no self-managed edition), yet it stores your responders' names, emails and phone numbers plus alert payloads — so the real question is not whether alerts reach you in China, but that this incident PII is collected inside China and lands offshore.
That makes it a PIPL cross-border transfer: you owe notice, separate consent for the export, and a lawful transfer mechanism; a CIIO or large-volume handler also owes in-country storage under Article 39 (formerly Article 37), and a China-facing dashboard needs an ICP filing. Because Opsgenie has no in-country region and no self-host edition, there is no native path to keep that data in China — redacting fields narrows what crosses, not whether it crosses, and does nothing for residency.
What Opsgenie's own documentation says about China
| Fact | Primary source |
|---|---|
| Opsgenie stores data only in a US region (the default) or an EU data center in Frankfurt, Germany, hosted by Amazon Web Services; the region is chosen at the login page and there is no mainland-China region. | Atlassian Support — Opsgenie, "European service region" (retrieved 2026-10-13) |
| Opsgenie is a hosted cloud service; Atlassian's data-residency doc states certain personal data, such as users' full names and emails, is stored in its US location regardless of the region selected — so responder contact details land offshore and there is no self-managed edition to run in China. | Atlassian Support — Opsgenie, "Opsgenie data residency" (retrieved 2026-10-13) |
| Exporting personal information collected in China — here, responders' contact data and the identifiers inside alert payloads — requires notice, separately obtained consent for the cross-border transfer, and a lawful transfer mechanism under PIPL Articles 38–40. | China Personal Information Protection Law (promulgated 2021-08-20), Arts. 38–40 — 21YunBox China compliance reference (retrieved 2026-10-13) |
| Operators of critical information infrastructure must store personal information and important data collected in China within the mainland under China's Cybersecurity Law, Article 39 (formerly Article 37). | China Cybersecurity Law (2016; 2025 revision effective 2026-01-01), Art. 39 (formerly Art. 37) — 21YunBox China compliance reference (retrieved 2026-10-13) |
Sources verified by the 21YunBox compliance team on 2026-10-13.
The question that matters for Opsgenie in China is not “will the alert reach my phone in Shanghai.” It is where the incident data lands, and whether it is allowed to leave China at all. Opsgenie is incident and on-call tooling, so the record it keeps is one of the most unfiltered your organization produces: responders’ names, work emails and phone numbers stored outright as personal information, plus alert payloads that carry system and service context and routinely embed user identifiers, error strings and request details. Opsgenie runs only on Atlassian’s offshore cloud, so when that record is collected from inside China it lands in the United States or the European Union — not in the mainland.
That makes it a cross-border transfer of personal information under China’s Personal Information Protection Law. A handler exporting China-collected personal data owes a specific cross-border discipline: give notice, obtain separate consent for the export, and stand up a lawful transfer mechanism (Articles 38–40). An operator of critical information infrastructure, or a high-volume handler, additionally owes in-country storage under China’s Cybersecurity Law, Article 39 (formerly Article 37). And any China-facing dashboard served from your own domain needs an ICP filing before it may lawfully operate. None of those duties is about speed.
Scrubbing narrows what crosses — it does not close the door
A reasonable reflex is: “we mask IPs, drop emails and redact sensitive fields in our alert payloads, so we are fine.” Masking and redaction are worth doing, and they shrink your exposure. But they change what crosses the border, not whether it crosses — and they do nothing for residency, which is about whether the data stays in-country at all. Opsgenie still needs a responder directory to page the right engineer: real names, real emails, real phone numbers. That identity data is the point of the product, and it lands offshore no matter how aggressively you scrub the payloads around it.
Is there an in-country option for Opsgenie? No.
Opsgenie is a cloud-only SaaS. Atlassian documents exactly two data regions — a US region (the default) and an EU data center in Frankfurt, Germany, hosted by Amazon Web Services — and the region is chosen on the login page. There is no mainland-China region, and there is no self-managed or on-prem edition of Opsgenie you could run inside China. Switching from the US region to the EU region does not help: the EU is simply another offshore location. (Atlassian has also announced it is winding Opsgenie down and folding its operations capabilities into Jira Service Management and Compass, so there is no future in-country path on this product either.) Because the data cannot be kept in China inside Opsgenie, the compliant answer has to be built around it.
| Question | Opsgenie | What it means for China |
|---|---|---|
| Where does incident data land? | US region (default) or EU — Frankfurt, Amazon Web Services | Offshore either way; switching US to EU is still outside China |
| Mainland-China region? | None | No in-country landing spot for the data itself |
| Self-managed / on-prem edition? | None — cloud-only SaaS | No way to run the backend inside China |
| What PII does it hold? | Responders' names, emails, phone numbers; alert payloads | One of the most unfiltered records your systems emit |
| Cross-border transfer under PIPL? | Yes, once collected in China | Notice + separate consent for export + a transfer mechanism (Arts 38–40) |
| In-country storage duty? | Cannot be met inside Opsgenie | CIIO / bulk handlers owe storage in China (Art 39, formerly Art 37) |
| China-facing dashboard? | Needs an ICP filing | A separate regulatory step, regardless of load speed |
Why a reachability check misses this
A reachability test asks whether packets move: can the dashboard open from Shanghai, can the agent POST an alert to the backend. Those checks can all pass while you remain non-compliant, because they never reveal where the responder directory and alert history physically rest, or whether moving that data out of China was lawfully permitted. The most sensitive personal-information stream your infrastructure emits is exactly the thing a latency probe cannot see. That is the half of the question a speed-only or CDN-only vendor structurally cannot answer — and the half that decides whether your on-call setup is legal in China.
The lever: map, localize, deliver
- Map. Inventory the incident data’s cross-border and in-country-storage duties by your legal entity and data volume: which China-collected responder records and alert history must stay in-country, and which telemetry may lawfully be exported to your global observability and on-call tools.
- Localize. Put what must stay on an in-country, consented processing and storage footing, so the responder identities and incident records that cannot leave China do not — while only the lawfully-exportable signals reach Opsgenie offshore. (In-country infrastructure is not automatic compliance; the notice, consent and transfer-mechanism duties still apply — we set those up with you.)
- Deliver. Carry the China-facing dashboard or origin with an ICP filing and in-country compliant delivery via the 21YunBox Optimizer, which sits in front of your existing stack with no rebuild.
The outcome is that your monitoring and on-call run lawfully and compliantly in China — never through circumvention of any kind.
Talk to our China team
Opsgenie cannot keep your incident data in China, and no region switch or redaction setting changes that. We will map your exposure, put the data that must stay in-country on a lawful footing, and deliver your China-facing dashboard with an ICP filing. Reach out for a compliance assessment and a quote — we will walk through your specific on-call and incident-tooling setup.
