# Meshed-handler **URL:** \ **Category:** TTN Network and Services\ **Created:** [May 30, 2018, 12:22am UTC](https://www.thethingsnetwork.org/forum/t/meshed-handler/14652 "2018-05-30T00:22:19Z")\ **Posts on this page:** 1\ **Showing post:** 55
**Author:** ![Maj](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/maj/32/47732_2.png) [@Maj](https://www.thethingsnetwork.org/forum/u/Maj)\ **Post date:** [February 4, 2020, 5:18am UTC](https://www.thethingsnetwork.org/forum/t/meshed-handler/14652/55 "2020-02-04T05:18:02Z")
In you’re in Australia you should use: - meshed-router for gateways - meshed-handler for applications - console.thethings.meshed.com.au for the Console when configuring integrations. You can use the regular console at all other times. The problem with using asia-se is that other people in Australia may have applications registered on meshed-handler trying to use your gateway and the cross-region routing is intermittent and won’t be resolved until V3 is implemented. * * * ⚠ See also [below](https://www.thethingsnetwork.org/forum/t/meshed-handler/14652/63) for a [July 2020 discussion](https://www.thethingsnetwork.org/forum/t/meshed-handler/14652/69) about: > [@Maj](#): > > AU915 UDP gateways should point to au915.thethings.meshed.com.au > AS923 UDP gateways should point to as923.thethings.meshed.com.au > AU915 and AS923 MQTT (and other) gateways should point to thethings.meshed.com.au (or router.au.thethings.network) --- _[View the full topic](https://www.thethingsnetwork.org/forum/t/meshed-handler/14652)._