LoRa Frequency Bands Worldwide: A Guide to Regional Plans

LoRa does not use one universal frequency worldwide. A deployment needs radio hardware for the local band, a channel configuration that matches the network, and settings permitted in the country where the device will operate. An “868 MHz” or “915 MHz” label alone does not establish all three.

For LoRaWAN, these settings are organized into regional plans such as EU868, US915 and AS923. Start with the deployment country and network operator’s plan before choosing a device or changing its firmware configuration.

What is the difference between a frequency band and a regional plan?

A frequency band is a range of radio spectrum. A LoRaWAN regional plan also describes how a network uses spectrum: channels, data rates and receive parameters. Two devices can both carry a “915 MHz” label and still use incompatible channel settings.

LoRa is the radio modulation; LoRaWAN adds the network protocol. A proprietary point-to-point LoRa link can use its own packet format and is not automatically compatible with a LoRaWAN gateway. The LoRaWAN introduction explains that distinction and the roles of devices, gateways and servers. Semtech describes the physical and network layers in its LoRaWAN overview.

Which LoRaWAN regional plans are commonly used?

These names follow LoRa Alliance RP002-1.0.5. They identify regional plans, not blanket transmission permissions. Numeric ranges are in MHz.

Australia supports AU915 and AS923-1. Major public operators recommend AS923-1 in the reference; confirm the actual network’s configuration.

Why are there four AS923 sub-plans?

Different AS923 suffixes select different defaults. Examples include Japan (AS923-1), Indonesia (AS923-2) and Israel (AS923-4).

These RP002-1.0.5 defaults are not a deployed network’s complete channel list. Confirm additional channels, receive settings and local access rules.

Which local differences are easy to miss?

India: check newer references, not just an old “865–867” label

India’s 2021 short-range-device rules cover 865–868 MHz and superseded earlier 865–867 MHz RFID rules, with provisions for equipment approved under the older rules. Match the device’s hardware, firmware and approval to the applicable conditions; a newer plan name does not update an older device automatically. See the official WPC rules, G.S.R. 853(E).

Indonesia and Japan: “Asia” is not a channel setting

Indonesia’s 2024 LPWAN technical standard sets requirements for operation in 920–923 MHz. Do not copy a generic AS923-1 configuration into an Indonesian installation. Japan’s ARIB STD-T108 covers several 920 MHz equipment categories. The approved category and channel-access profile matter as well as the frequency.

China: CN470 is not blanket permission for industrial IoT

China’s 470–510 MHz provisions for civil metering equipment include application and deployment limits. Do not treat the existence of a CN470 LoRaWAN plan as approval for any industrial network, antenna or transmit power. Check the applicable category in the MIIT announcement and technical requirements.

Europe, the United States and Australia: band limits are only the beginning

European short-range-device conditions vary by sub-band and operating mode; one duty-cycle or power figure should not be applied to all EU868 operation. ETSI EN 300 220-2 is a technical standard, and national spectrum rules still need checking.

In the United States, 47 CFR 15.247 places conditions on operation in 902–928 MHz. Selecting US915 is not, by itself, evidence of FCC compliance. Australia’s LIPD class licence also attaches technical and interference conditions to eligible devices.

Can the same device work in every region?

Only if the complete device supports each intended region. A radio chip’s tuning range is not the same as the finished product’s usable range: filters, amplifiers, antennas and approved configurations can limit where the device works. Software cannot make an unsuitable RF front end or antenna support a different band.

For a LoRaWAN link, compare the end device and gateway against the network’s plan, sub-plan and channel mask, which selects the active channels. Check both uplink and downlink operation. Successful reception of a packet does not prove that the device can join or receive a downlink correctly.

Frequency compatibility also does not establish application compatibility. Activation credentials, LoRaWAN version and payload decoding still need to match the network and application. Keep those checks separate so a channel problem is not mistaken for a decoder problem.

What should you confirm before a rollout?

1. Deployment location: identify every country where the equipment will transmit, including later relocation.
2. Network configuration: obtain the operator’s exact regional plan, AS923 suffix where applicable, channel mask and receive settings.
3. Hardware variant: confirm that the RF front end and antenna cover the required uplink and downlink frequencies.
4. Software revision: check the device and server support the intended regional-parameter revision and LoRaWAN features.
5. Local conditions: check equipment approval, allowed antenna, power and channel-access rules for the installation.
6. Field test: test joining, representative uplinks and required downlinks at the actual installation sites before scaling up.

Record the confirmed plan alongside the hardware variant and firmware version. That small record prevents a later replacement device from arriving with the right-looking frequency label and the wrong network configuration.

Related reading

Read What Is LoRaWAN? for network architecture, device classes and activation, or Global 4G LTE Bands Explained for the different checks involved in a cellular connection.