TG Region Specific Details

As of mid-2018, TG is hosted in a number of regional data centers. This improves performance and scalability. The following TG features must be targeted at the right region:

  • Website access: normally a partner's URL will direct them to the correct server. If they are used to accessing telematics.guru, they may no longer be able to login.
  • Mobile App access: the mobile app will prompt the user to select their region before logging in.
  • TG API: the API should be accessed with a region specific domain name. The partner URL may work, but in future the API may be seperated from the website.
  • Devices Direct to TG: some devices connect directly to TG. These need to target the right instance of TG.

This table gives the details for each of these aspects. They are discussed further below.

RegionServer LocationGeneric URLAPI URLDevice URLIP Address*
APAC01Australia East
NSW, Aus
apac01.telematics.guruapi-apac01.telematics.gurudevice-apac01.telematics.guru40.82.219.2
APAC02Australia East
NSW, Aus
apac02.telematics.guruapi-apac02.telematics.gurudevice-apac02.telematics.guru40.82.219.4
APAC03Australia East
NSW, Aus
apac03.telematics.guruapi-apac03.telematics.gurudevice-apac03.telematics.guru40.82.219.106
APAC04Australia East
NSW, Aus
apac04.telematics.guruapi-apac04.telematics.gurudevice-apac04.telematics.guru40.82.220.205
APAC05Australia East
NSW, Aus
apac05.telematics.guruapi-apac05.telematics.gurudevice-apac05.telematics.guru52.237.222.152
EMEA01East USAemea01.telematics.guruapi-emea01.telematics.gurudevice-emea01.telematics.guru52.179.86.26
EMEA02West Europeemea02.telematics.guruapi-emea02.telematics.gurudevice-emea02.telematics.guru40.119.147.99
EMEA03West Europeemea03.telematics.guruapi-emea03.telematics.gurudevice-emea03.telematics.guru40.119.152.46
EMEA04West Europeemea04.telematics.guruapi-emea04.telematics.gurudevice-emea04.telematics.guru40.119.153.184
AMER01East USAamer01.telematics.guruapi-amer01.telematics.gurudevice-amer01.telematics.guru20.185.104.80

* DM will attempt to keep the IP addresses constant, but they are subject to change. Use the DNS entries as far as possible.


Website Access

  • The partner specific URL (eg client1.telematics.guru) should resolve to the correct TG instance.
  • Clients should not use telematics.guru to login - this is likely to resolve to the wrong TG instance and their login will fail.
  • See the table at the top of this article for the generic, non client specific URL's for each TG instance.

The generic URL will work for accessing the correct server, but we encourage clients to use their client specific URL. eg client1.telematics.guru


Mobile App Access:

The standard Telematics Guru mobile app will have a region selector on the login screen. To login successfully, choose the correct region. If the user is unsure which region they are in, check the lower right hand corner of their website login page.


Telematics Guru API

The TG API should be accessed with the API URL shown in the table at the top of this article. This will resolve to the correct region.


Devices Connecting Directly to TG

There are a number of devices that send data directly to TG. When setting these devices up, use the Device URL. This will resolve to the correct region. Avoid using the IP address, as this may change in future.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.