Meta.AI US IP Region Not Supported Solutions
Update (2025.4.29)
Account registered mid-last year was dead when logging in this year first half. Meta’s risk control is definitely the strictest. Also tried re-registering on US East Windows machine—basically get risk controlled immediately upon registration.
Near the Llama Developer Conference, I bought a US Facebook account online and successfully used meta.ai on US East Windows machine. Hoping Llama Developer Conference has surprises, but personally expect the release won’t match today’s Alibaba team’s Qwen3.

Background
Recently Meta released open-source Llama 3.1. via

When I tried logging into Meta.AI official site to try the latest model, I found US IP wasn’t supported.

So I opened Microsoft Remote Desktop, connected to my US East Windows machine, and in incognito mode tried logging into Meta.AI with Meta account—still got region not supported error.
Not giving up, I used a US educational network residential node I got free for a month earlier, enabled nekobox TUN mode, tried again—same error.
Helplessly, could only use WhatsApp to experience the latest model.

Later searching for solutions online, first saw this L Site post—High quality IP can’t access Meta.AI?.
Post author described in May 2024 also couldn’t access Meta.AI with high quality US IP.
Later I also posted on L Site—meta.ai US IP not supported? Stricter risk control?, to see if anyone else had the same error.
One comment made perfect sense.

Since the latest Llama model in WhatsApp was still slightly inferior to Claude 3.5 Sonnet, I didn’t act on it.
Solution
This morning while clearing tabs, I saw last month’s leftover content and re-registered a Facebook account with email. Didn’t use US proxy IP locally—operated entirely on US East Windows machine. Then used Facebook to log into Meta.AI—successfully accessed.

Indeed as that user said—whether you can log into Meta.AI depends on Facebook account’s regional attribute.
Years ago I probably registered Meta apps through Hong Kong IP.
This Meta.AI region restriction should be risk control Meta.AI added mid-year—this restriction is probably based on your Meta account’s registration location [region-restricted Meta accounts showed nothing abnormal in all settings]. In April this year, I could access Meta.AI with US IP without this restriction. In July, I encountered this restriction again.
Overall, if you encounter similar issues, best use native US IP [after enabling proxy, ping0.cc shows native IP, not broadcast IP], re-register a Facebook account with email, then use the new account to log into Meta.AI—should work normally.

Finally attaching what I think is Meta AI’s most surprising feature—real-time image generation [released in April first half of year]. Here’s an example of me using Meta AI real-time image generation in WhatsApp app [fishes means multiple fish species 😁].
Web can also experience real-time image generation. Use Imagine: xxx prompt to try.

This real-time interactive experience is quite nice.
Other models like Llama 3.1-405B are beneficial for open-source LLM research and development. For ordinary people, as this fellow said—can skip it, just embrace Claude 3.5 Sonnet.

Document Info
- License: Free to share - Non-commercial - No derivatives - Attribution required (CC BY-NC-ND 4.0)