If your team reaches Medic52 from inside a corporate IT environment, your network administrators may need to allow (whitelist) the addresses below so connections aren’t blocked. This article is written for your IT team.
Background
Medic52 runs in three regions — the United States, Australia, and Canada. When you connect, you first reach a Medic52 entry point; once you sign in, Medic52 knows which resort you belong to and routes you to that region’s server. Because we use load balancers and cloud infrastructure whose IP addresses change, whitelist by hostname, not by IP address.
Medic52 addresses to allow
medic52.comandwww.medic52.com— website and knowledge baseapp.medic52.com— web platform entry pointapp-us.medic52.com— United States region serverapp-au.medic52.com— Australia region serverapp-ca.medic52.com— Canada region server
Allowing all of the regional servers ensures the initial connection and any region routing are not blocked.
Third-party services Medic52 uses
We rely on a few external services for maps, support, and monitoring that we can’t host ourselves. Allow these so the platform works fully:
- Google Maps (map display):
maps.gstatic.com,maps.googleapis.com,*.googleapis.com - Intercom (in-app support messenger and help search):
.intercom.io,.intercomcdn.com - Sentry (error monitoring so we can spot and fix problems):
*.sentry.io
Getting a definitive list
Third-party services and hostnames change over time. If your firewall is strict and something isn’t loading, contact Medic52 support for the current, definitive list for your region.