Earlier this year, we announced that a New Relic region was coming to Japan. Today it's open. As of the morning (JST), the Japan region is generally available, and customers can onboard now. This data center is hosted in the AWS Tokyo region. It was built to answer requests we hear from Japanese enterprises: keep our data in Japan and let us do it on the same platform we already run.
Data sovereignty is essential for regulated industries
Telemetry data such as logs and traces may carry sensitive PII data, including customer identifiers, transaction detail, and operational metadata that regulated organizations cannot move across borders. Increasingly, internal governance committees will not approve moving across borders even when the law permits it.
In the Japan region, your observability data is ingested, stored, and processed in Japan. For financial services, telecommunications, healthcare, public infrastructure, and the manufacturers that supply them, that is essential for an enterprise-grade observability. Teams that have had to strip fields before sending logs, or exclude their critical systems from monitoring altogether, can now bring those workloads in.
“Japan continues to set the standard in terms of quality and observability is a vital part of that. Japanese enterprises told us they needed local control and speed without accepting a lesser product, and in the age of AI, that has to include where the reasoning happens. The Japan region delivers all of this.”
-Ashan Willy, CEO, New Relic
In the age of AI, in-region matters even more
Here is what has changed since we first announced this region. Observability is as much as where the data is stored and where telemetry is reasoned over. When an AI agent investigates an incident, it reads your telemetry metadata and the payloads inside them. Any architecture where inference happens outside the country has quietly reintroduced the exact cross-border data flow in the region was meant to eliminate.
We built the Japan region so that doesn't happen. Working with AWS, AI processing for Japan region customers runs in-region. Your telemetry does not leave Japan to be analyzed, including when it is being analyzed by a model.
It's a question worth asking your vendors: when your AI analyzes our telemetry, where does that happen? As AI becomes the primary interface to operational data, where data rests and where it is reasoned over has to be answered together.
“AI is becoming the way engineers interact with their operational data. That makes the question of where the inference runs just as important as where storage lives. We built the Japan region, so our customers never have to choose between the two.”
-Brian Emerson, CPO, New Relic
The same New Relic platform, in Japan
The New Relic platform supporting the Japan region is the same platform your teams already run — the same product, the same workflows, the same instrumentation and performance.
For a global enterprise and a global engineering organization, that matters practically. The runbooks, dashboards, and instrumentation your teams have built elsewhere carry over. Choosing the Japan region doesn't mean adopting a different way of working, retraining your engineers, or maintaining a second operating model.
Because the region sits alongside customer workloads in Japan, latency drops across the board faster ingestion, faster queries, more responsive dashboards and alerts. For teams running daily operational reviews or triaging a live incident at 3am, that performance matters.
Built with, and for, the Japanese market
New Relic is one of the leading observability platforms in Japan, and the Japan region is the clearest expression yet of our commitment to that market. It joins our local technical, support, and field teams, our Japan leadership, and our long-standing partnership with AWS.
Customers across telecommunications, pharmaceuticals, financial services, systems integration, and logistics have been building toward this launch with us, and are onboarding now.
Getting started
New customers can get in touch with our Japanese account team and will get you set up. Existing customers can move to this Japan region with white-glove support from New Relic's local customer success team, who will help scope migration, validate the environment, and manage the transition.
Want to see it in action? Sign up for a live demo.
이 블로그에 표현된 견해는 저자의 견해이며 반드시 New Relic의 견해를 반영하는 것은 아닙니다. 저자가 제공하는 모든 솔루션은 환경에 따라 다르며 New Relic에서 제공하는 상용 솔루션이나 지원의 일부가 아닙니다. 이 블로그 게시물과 관련된 질문 및 지원이 필요한 경우 Explorers Hub(support.newrelic.com)에서만 참여하십시오. 이 블로그에는 타사 사이트의 콘텐츠에 대한 링크가 포함될 수 있습니다. 이러한 링크를 제공함으로써 New Relic은 해당 사이트에서 사용할 수 있는 정보, 보기 또는 제품을 채택, 보증, 승인 또는 보증하지 않습니다.