Corporate Firewalls

If you are accessing our systems from inside a corporate IT environment, then this is the stuff your techy people will need to know:

System Background

The application is spread across multiple data centres in different countries. In the initial connection requests to Medic52, the app or web will be geo-routed with Amazon’s Route 53 to the closest server.

Once the user is logged in (so we know which resort the user is connected too), then they will be sent to that country server.

For this reason we recommend you whitelist all of our server addresses, to ensure that the initial connection is not blocked.

We also use a few third party services for customer support, system monitoring/diagnosis and functionality that we simply cannot build and host ourselves.

URI’s

We cannot provide you with IP Addresses as they change regularly and often. We utilise load balancers and other technology to help keep our systems online and available across the world and this relies on some smart technology that is always changing.

  Medic52:

    • www.medic52.com
    • help.medic52.com
    • app.medic52.com
    • api-us.medic52.com
    • api-au.medic52.com

  Third Party Services we use:

    • Google Mapping (you like to see maps)
      • maps.gstatic.com
      • maps.google.com
      • *.googleapis.com
    • Google Analytics (We track anonymous usage)
      • *.google-analytics.com
    • NewRelic (We like to know the app is performing in a timely manner)
      • *.nr-data.net
      • *.newrelic.com
    • Intercom.io (We like to be able to talk to our users)
      • api.intercom.io
      • *.intercomcdn.com

 

Was this article helpful?

Related Articles

Leave A Comment?