Some ICP boundary nodes (e.g., 208.115.197.139) are serving text/html error pages instead of JavaScript files for id.ai/_app/immutable/... URLs. This causes II login to randomly fail depending on which boundary node handles the request. CSS loads fine, only JS fails.
Behavior: intermittent — sometimes works, sometimes fails, varies by browser and refresh. Started around Feb 19, 2026.
Affects all browsers. id.ai homepage loads fine, only /#authorize sub-resources fail.
Update: This issue likely started after II upgrade proposal 140447 (release-2026-02-17). Some boundary nodes appear to be caching stale JS filenames from the pre-upgrade frontend. Requests hitting these nodes get 503s because the old filenames no longer exist on the canister. CSS files (unchanged between versions) load fine. The issue is intermittent because load balancing distributes requests across both stale and updated nodes.
The proposal was not executed yet .
Update with full details:
I’m experiencing inconsistent behavior with Internet Identity login on my ICP-hosted dapp (sudokuchallenge.com) since approximately February 19, 2026.
The problem: When my app opens id.ai/#authorize as a popup for authentication, the JavaScript assets under id.ai/_app/immutable/ randomly fail to load. CSS files always load successfully. The failures are intermittent — the same browser on the same device may work one attempt and fail the next.
What the errors look like:
Chrome/Edge report:
Failed to load resource: the server responded with a status of 503 ()
TypeError: Failed to fetch dynamically imported module: https://id.ai/_app/immutable/entry/app.BwBhTjuN.js
Firefox reports:
Loading module from "https://id.ai/_app/immutable/nodes/2.CMV56_xp.js" was blocked because of a disallowed MIME type ("text/html")
NS_ERROR_CORRUPTED_CONTENT
The Firefox error reveals that the server returns Content-Type: text/html instead of application/javascript for .js files — meaning an HTML error page is being served instead of the actual JavaScript.
Network tab observation: One of the failing requests showed:
Remote Address: 208.115.197.139:443
Status Code: 503 Service Unavailable
Content-Type: text/html; charset=utf-8
Content-Length: 39773
X-Ic-Canister-Id: rdmx6-jaaaa-aaaaa-aaadq-cai
The response is a 39KB HTML page instead of the requested JS file.
Inconsistency pattern:
Login worked perfectly for the first 2 days after launch (Feb 17–18)
Started failing Feb 19
At any given moment, login may work on one browser but not another on the same machine
Firefox worked, then stopped working after a computer restart, then worked again, then stopped again
Mobile Chrome works, desktop Chrome doesn’t — then reverses
Edge mobile works, Edge desktop doesn’t — then reverses
Sometimes all browsers fail simultaneously, sometimes one works while others don’t
Visiting id.ai directly in a browser tab loads fine every time. Only the /#authorize sub-resources fail intermittently
What I’ve ruled out:
Not a caching issue (fails in incognito, persists after clearing all browser data)
Not browser extensions (fails in incognito with all extensions disabled)
Not my CSP (updated connect-src to include all IC/II domains — login now works more often but still fails intermittently)
Not my canister cycles (both canisters running, healthy balance)
Not DNS (tried Google 8.8.8.8, Cloudflare 1.1.1.1, Quad9 9.9.9.9 — no difference)
Not my network (same behavior on home WiFi and mobile hotspot)
Not McAfee/firewall (verified no blocked connections, web protection off for Chrome)
My canisters serve the website and all gameplay features perfectly — only the II popup fails
Environment:
@dfinity/auth-client: 3.4.3
@dfinity/agent: 3.4.3
Identity provider URL: https://id.ai
Windows 11, tested on Chrome 145, Firefox, Edge
Samsung mobile, tested on Chrome, Edge, Firefox, Opera
App hosted on IC: sudokuchallenge.com
This is blocking all user authentication for my live app. Any guidance appreciated.
Hello @Ra1
This not an issue with the HTTP gateways/API boundary nodes, but with the canister itself. The asset that you are requesting does not exist.
$ curl -sLv https://rdmx6-jaaaa-aaaaa-aaadq-cai.raw.ic0.app/_app/immutable/nodes/2.CMV56_xp.js
...
* Request completely sent off
< HTTP/2 404
...
Asset /_app/immutable/nodes/2.CMV56_xp.js not found.%
Couldn’t replicate. On Win11 logging in and out multiple times works fine on Brave and Chrome latest versions.
Edit : location Eastern Europe.
I’m located in Sydney, Australia. This is likely region-specific — the HTTP gateway serving my region (208.115.197.139) appears to be the one failing.
This affects all browsers on my machine — Chrome, Edge, and Firefox all fail with the same errors. Even visiting https://id.ai directly (not from my app) fails. It’s not browser-specific.
Also, the current filenames are failing too, not just the old deleted ones. Can you test these from the canister directly?
curl -sLv https://rdmx6-jaaaa-aaaaa-aaadq-cai.raw.ic0.app/_app/immutable/entry/app.BwBhTjuN.js
curl -sLv https://rdmx6-jaaaa-aaaaa-aaadq-cai.raw.ic0.app/_app/immutable/chunks/qbgVze6d.js
Can you try with a VPN set to Australia/APAC region to replicate?
Confirmed: region-specific issue.
I just tested with a VPN set to USA — Internet Identity works perfectly. As soon as I disconnect the VPN and use my Australian connection, it fails again with the same 503 errors on all browsers.
The HTTP gateway at 208.115.197.139 (serving the APAC/Australia region) is returning 503 for all JS assets from the II canister while CSS loads fine.
@zeeghazi — what region are you located in?
This screenshot shows the issue on Edge visiting id.ai/#authorize directly (not from any dapp): all JS files return 503.
Also tested with VPN set to Australia — different gateway IP (208.115.197.147) but same 503 failure. So at least two Australian gateways are affected:
208.115.197.139 (my direct connection)
208.115.197.147 (VPN Australia)
Both are in the 208.115.197.x range — likely the same data center/cluster.
try setting this in AuthClient options
identityProvider: “Internet Identity
reference: 🚀 Announcement: identity.ic0.app & identity.internetcomputer.org → id.ai (Internet Identity 2.0)
Thanks, but all three II URLs point to the same canister and route through the same regional gateways. I’ve tested id.ai, identity.ic0.app, and identity.internetcomputer.org — all fail identically from Australia. The issue is the HTTP gateways in the 208.115.197.x range, not the URL used. VPN to USA works immediately.
Request URL
https://identity.ic0.app/_app/immutable/entry/start.CG7kSU6k.js
Request Method
GET
Status Code
503 Service Unavailable
Remote Address
208.115.197.155:443
Referrer Policy
same-origin
It was a regional issue that should be resolved now.
Thank you @rbirkner and the DFINITY team for the quick fix! Confirmed — login is working perfectly now from Australia on all browsers. Really appreciate the fast response.
