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.
| Region | Server Location | Generic URL | API URL | Device URL | IP Address* |
|---|---|---|---|---|---|
| APAC01 | Australia East NSW, Aus | apac01.telematics.guru | api-apac01.telematics.guru | device-apac01.telematics.guru | 40.82.219.2 |
| APAC02 | Australia East NSW, Aus | apac02.telematics.guru | api-apac02.telematics.guru | device-apac02.telematics.guru | 40.82.219.4 |
| APAC03 | Australia East NSW, Aus | apac03.telematics.guru | api-apac03.telematics.guru | device-apac03.telematics.guru | 40.82.219.106 |
| APAC04 | Australia East NSW, Aus | apac04.telematics.guru | api-apac04.telematics.guru | device-apac04.telematics.guru | 40.82.220.205 |
| APAC05 | Australia East NSW, Aus | apac05.telematics.guru | api-apac05.telematics.guru | device-apac05.telematics.guru | 52.237.222.152 |
| APAC06 | Australia East NSW,Aus | apac06.telematics.guru | api-apac06.telematics.guru | device-apac06.telematics.guru | 20.53.86.248 |
| EMEA01 | East USA | emea01.telematics.guru | api-emea01.telematics.guru | device-emea01.telematics.guru | 52.179.86.26 |
| EMEA02 | West Europe | emea02.telematics.guru | api-emea02.telematics.guru | device-emea02.telematics.guru | 40.119.147.99 |
| EMEA03 | West Europe | emea03.telematics.guru | api-emea03.telematics.guru | device-emea03.telematics.guru | 40.119.152.46 |
| EMEA04 | West Europe | emea04.telematics.guru | api-emea04.telematics.guru | device-emea04.telematics.guru | 40.119.153.184 |
| AMER01 | East USA | amer01.telematics.guru | api-amer01.telematics.guru | device-amer01.telematics.guru | 20.185.104.80 |
| AMER02 | East USA | amer02.telematics.guru | api-amer02.telematics.guru | device-amer02.telematics.guru | 52.191.219.242 |
* 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
Which is my instance?
If the user is unsure which region they are in, check the lower right hand corner of their website login page.
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.