Is Luarmor down? How to check
There is no status page we could find, so test the two hosts yourself. What each answer means and when the fault is your key, not the service.
Luarmor does not publish a status page we could find, so the quickest check is
to ask the same hosts the loader asks. If api.luarmor.net returns a
loader and cdn.luarmor.net returns Lua text, the service is
reachable and the fault is more likely in your key or your client.
Where a loader request can fail
A loader failure has three possible owners, and they fail differently.
| Layer | What it is | How it fails |
|---|---|---|
| API host | api.luarmor.net, which serves the loader |
The fetch returns nothing or a non Lua body |
| CDN host | cdn.luarmor.net, which serves the second stage |
The loader downloads an empty body or a placeholder |
| Seller project | The project and its keys | A KEY_ code, or a key page that is gone |
The first two belong to the licence service. The third can fail while both are healthy.
Check the API host
Take the loader URL from the line you paste and request it with a tool that shows the status code. In a terminal:
curl -s -o /dev/null -w "%{http_code}\n" https://api.luarmor.net/files/v4/loaders/<loader-id>.lua
Replace <loader-id> with the id in your line. A
200 means the host answered. A 404 means the path is
wrong or the loader no longer exists. A 403 or a challenge page
means a proxy refused the request, which is not proof of an outage.
Do not compare the body against a saved copy. In our sample, two downloads 28 seconds apart differed in 8 of 12 fields, and the ones that stay fixed are in the loader anatomy.
Check the CDN host
The second stage has a fixed path. Request it and read the first lines:
curl -s https://cdn.luarmor.net/v4_init_ocmid.lua | head -n 5
A request without a client fingerprint receives the rejection branch: two
comment lines and a LocalPlayer:Kick with
Your executor is not supported by Luarmor. That text is a healthy
answer: the host is serving the endpoint.
If the command returns nothing, or an HTML error page, the second host is not serving Lua. That is the case where waiting is the right move.
Read the result
| What you see | What it means | Next step |
|---|---|---|
200 from the API and Lua text from the CDN |
Both hosts reachable | Look at the key and the client |
Your executor is not supported |
CDN up, client not recognised | Treat it as a client problem |
403 or a challenge page |
A proxy refused the request | Retry from a normal browser before concluding |
| DNS error | The name did not resolve | Check the connection, not the key |
5xx |
The host answered with an error | Retry later and tell the seller |
| Timeout | No answer in time | Retry once, then treat it as a network fault |
The second row is the one people misread. A kick message is a reply from the CDN: it arrives before the key is read, and it means the second stage was delivered.
When the service is up and the loader still fails
A reachable service returns a code, and the code names the layer. The full list is in the error code dictionary; five entries cover most failures.
| Code | First thing to check |
|---|---|
KEY_HWID_LOCKED |
Whether the device changed, or the key moved |
KEY_EXPIRED |
The end date the seller set |
KEY_INCORRECT |
The string, including spaces and truncation |
KEY_BANNED |
A message to the seller, not a retry |
TIME_ERROR |
The clock on your machine |
TIME_ERROR is the one a user can fix without the seller. The check
compares timestamps, and a clock that is off by enough looks like an outage. The
fix is on the time error
page.
What the seller sees that you cannot
The response depends on the client, so two users with the same loader can receive different files. Our unauthenticated request received the rejection branch; a recognised client receives an init. The seller can also pause a project, revoke a key or upload a new build, and none of that appears in your browser request. A rejection from the client layer is covered in executor not supported.
A five step check
- Open the seller's key page. If it is gone, the project is the problem.
- Request the loader URL and note the status code.
- Request the second stage and read the first lines.
- Run the loader once and copy the exact message.
- Send the seller the code, the time, the client name and a screenshot.
Step 4 matters more than it looks. A code and a time can be triaged; "it does not work" cannot.
Wait or change something
If both hosts answer, waiting will not fix a KEY_ code. The service
is doing its job, and the answer is about your key or your client. If neither
answers, waiting is the only action available.
There is a middle case: one host answers and the other does not. The loader then fails after a successful fetch, and the message is usually a script error rather than a licence code. Report both results.
FAQ
Is there an official Luarmor status page?
The documentation does not describe a status page, and the domains we checked do not carry one. News shows up in the seller's Discord and the service's own Discord, both run by people rather than by an automated status feed. A request to each host is a check you can run yourself.
How often does Luarmor go down?
We have no measurement, so any frequency would be invented. We checked both hosts on one day and got a working response every time. An uptime figure would need months of monitoring.
Does a 403 mean the service is down?
No. A 403 comes from a proxy or a bot rule in front of the host, and it says the request was refused, not that the backend is broken. A browser can receive the same page while the service is healthy. Retry from a normal browser before drawing a conclusion.
Why does the loader work for my friend and not for me?
The response depends on the client that asks. Your friend's client may be recognised and yours may not, which produces an init for one and a kick message for the other. The same loader is not the same request. Compare clients before comparing keys.
Can I run a cached copy while the service is down?
Only if a valid second stage was already written to static_content_170926 and it is longer than 2,000 characters. The loader also writes the file before it validates it, so a failed download can leave something behind. purge_cache() clears it when the cache is the problem rather than the fix.
Why does the URL return a different hash every time?
Because the loader is generated per request. A timestamp and several identifiers change, so the bytes change even when the design does not. Comparing hashes across requests produces a false outage signal. Compare the status code and the shape of the body instead.
Do I need a VPN to reach Luarmor?
No. A VPN changes your IP, and the licence check is built around a hardware fingerprint. It does not fix a KEY_HWID_LOCKED, and it does not make an unreachable host reachable unless your network is the problem. The HWID page explains the difference.
Can the seller tell whether the service is down?
They can see their project and their keys, and they can try the same requests you did. They cannot see your browser or your client. A message with both status codes is more useful to them than a report that the loader does not work.