TG Region Specific Details
Written by Matthew Clark-Massera
Updated at February 18th, 2026
Table of Contents
Telematics Guru Regional Instances and API Access
Telematics Guru (TG) is hosted across multiple regional data centres to improve performance, scalability, and data residency compliance. It is important that you use the correct regional instance for website access, API integrations, and devices connecting directly to TG.
If you are unsure which instance your organisation is on, you can:
- Check the lower right-hand corner of your TG web app login page.
- Perform a ping test on your TG URL (for example
mycompany.telematics.guru) and check the responding server name.
- Contact your TG administrator or Digital Matter support if needed.
The following TG features must be targeted at the correct region.
-
Website access – normally a partner-specific URL will direct users to the correct server. Accessing telematics.guru directly may result in login failure if it resolves to the wrong instance.
-
Mobile app access – the mobile app will prompt the user to select their region before logging in.
-
TG API – the API must be accessed using the region-specific domain name. While a partner URL may currently work, API access may be separated from website access in future.
-
Devices connecting directly to TG – devices configured to send data directly to TG must target the correct regional Device URL.
Regional Instance Details
Use the table below to identify the correct Generic URL, API URL, Device URL, and direct documentation links for your region.
| Region | Server Location | Generic URL | API URL | GraphQL Link | Swagger Link | Device URL | IP Address* |
|---|---|---|---|---|---|---|---|
| APAC01 | Australia East NSW, AUS |
apac01.telematics.guru | api-apac01.telematics.guru | Link | Link | device-apac01.telematics.guru | 40.82.219.2 |
| APAC02 | Australia East NSW, AUS |
apac02.telematics.guru | api-apac02.telematics.guru | Link | Link | device-apac02.telematics.guru | 40.82.219.4 |
| APAC03 | Australia East NSW, AUS |
apac03.telematics.guru | api-apac03.telematics.guru | Link | Link | device-apac03.telematics.guru | 40.82.219.106 |
| APAC04 | Australia East NSW, AUS |
apac04.telematics.guru | api-apac04.telematics.guru | Link | Link | device-apac04.telematics.guru | 40.82.220.205 |
| APAC05 | Australia East NSW, AUS |
apac05.telematics.guru | api-apac05.telematics.guru | Link | Link | device-apac05.telematics.guru | 52.237.222.152 |
| APAC06 | Australia East NSW, AUS |
apac06.telematics.guru | api-apac06.telematics.guru | Link | Link | device-apac06.telematics.guru | 20.53.86.248 |
| EMEA01 | East USA | emea01.telematics.guru | api-emea01.telematics.guru | Link | Link | device-emea01.telematics.guru | 52.179.86.26 |
| EMEA02 | West Europe | emea02.telematics.guru | api-emea02.telematics.guru | Link | Link | device-emea02.telematics.guru | 40.119.147.99 |
| EMEA03 | West Europe | emea03.telematics.guru | api-emea03.telematics.guru | Link | Link | device-emea03.telematics.guru | 40.119.152.46 |
| EMEA04 | West Europe | emea04.telematics.guru | api-emea04.telematics.guru | Link | Link | device-emea04.telematics.guru | 40.119.153.184 |
| AMER01 | East USA | amer01.telematics.guru | api-amer01.telematics.guru | Link | Link | device-amer01.telematics.guru | 20.185.104.80 |
| AMER02 | East USA | amer02.telematics.guru | api-amer02.telematics.guru | Link | Link | device-amer02.telematics.guru | 52.191.219.242 |
* Digital Matter will attempt to keep IP addresses constant, however they are subject to change. Always use the DNS entries where possible.
Devices Connecting Directly to TG
Some devices send data directly to TG. When configuring these devices, use the Device URL for your region. This ensures traffic is routed correctly and avoids issues if IP addresses change in future.
Next Steps
If you are building an integration, use the GraphQL or Swagger link for your region above. For broader API guidance, see the GraphQL API for Telematics Guru or related REST guides within the TG Integration section of this Knowledge Base.
