What external services and IP addresses are used by Panoramic Power?
Discover a comprehensive list of external services and IP addresses utilized by Panoramic Power to enhance your understanding of their energy monitoring system.
Table of Contents
Some network environments, such as enterprise firewalls or proxy configurations, require allowlisting of external domains and IP addresses for full product functionality. This document lists all the third-party services and endpoints used by the Panoramic Power software platform.
Note: We recommend allowlisting based on domain names whenever possible. IPs may change over time due to third-party provider infrastructure.
Domains and Services Used
Service |
Purpose |
Domain(s) |
|---|---|---|
Sentry |
Error tracking and monitoring |
http://sentry.io , o123456.ingest.sentry.io (region dependent) |
Userflow |
Onboarding guides and product tours |
http://userflow.com , http://app.userflow.com , cdn.userflow.com |
Intercom |
Customer support chat |
http://intercom.io , api-iam.intercom.io, widget.intercom.io, static.intercomcdn.com |
FullStory |
Session replay and product analytics |
|
Google Maps |
Maps and address autocompletion |
|
Locize |
Translations and i18n |
api.locize.app, cdn.locize.com |
LaunchDarkly |
Feature flag management |
clientstream.launchdarkly.com, events.launchdarkly.com, sdk.launchdarkly.com |
IP Addresses (if required)
Although we strongly recommend relying on domain allowlisting, the following IPs were observed from our platform and may be required in highly restrictive network environments:
Destination |
IP Address |
Associated Service |
|---|---|---|
api.locize.app |
3.161.20.99 |
Locize |
3.161.20.41 |
Locize |
|
3.161.20.119 |
Locize |
|
3.161.20.103 |
Locize |
|
Dynamic (CDN-based) |
LaunchDarkly |
Note: These IPs are provided based on recent connection logs and may change over time depending on the CDN or cloud provider used by each third-party service.
Recommendations
Allow by domain – Whenever possible, configure your network to allow traffic to the domains listed above.
Proxying (Advanced) – If your organization requires tighter control, consider routing these requests through your infrastructure (e.g. api.powerradar.energy/locize-proxy) and maintaining internal DNS/proxy rules.
Monitoring – You can monitor outbound requests using HAR logs or network tools to validate new third-party endpoints when integrations are updated.