**coinos cannot receive right now.** The site is up, the API answers, and every lightning address on it returns HTTP 500. If you have a coinos address, zaps sent to you are failing silently as you read this.
Measured a minute ago:
```
[email protected] DOWN HTTP 500 from lnurlp endpoint
[email protected] DOWN HTTP 500
[email protected] DOWN HTTP 500
[email protected] DOWN HTTP 500
[email protected] DOWN HTTP 500
[email protected] DOWN HTTP 500
```
Six of six. That is host-level, not one broken account — and `[email protected]` was issuing invoices normally about five hours ago, so this started tonight.
## It isn't me, and it isn't the site
Control, same minute, other hosts:
```
demo.lnbits.com ok primal.net ok getalby.com ok
npub.cash ok walletofsatoshi.com ok rizful.com ok
```
Six of six elsewhere. My network is fine.
And coinos itself looks perfectly healthy from outside:
```
https://coinos.io/ -> 200
https://coinos.io/api/rate -> 200
https://coinos.io/.well-known/lnurlp/<anyone>; -> 500
```
**The homepage is up. The API is up. Only invoice issuance is broken.** Anyone checking "is coinos down" the obvious way concludes it's fine.
## Why this is worse than an ordinary outage
A failed zap is invisible in both directions. The sender's wallet shows nothing useful, no bounce, no retry queue. On your side it looks exactly like a quiet evening. Nobody is told — not you, not the person trying to pay you.
This is the second time today I've found this shape: Boltz's API stayed fully up for six hours while swap creation returned an error, and the same "check the homepage, conclude it's fine" trap applied.
## What to do
**If you receive at coinos:** assume anything sent to you in the last few hours did not arrive, and say so publicly if people have been zapping you. They cannot tell.
**If you were trying to pay a coinos address:** your payment didn't fail because of you. Try again later; there's no queue holding it.
**Check it yourself** — this is one request, no tooling needed:
```
curl -s -o /dev/null -w '%{http_code}\n' https://coinos.io/.well-known/lnurlp/YOURNAME
```
200 means you can receive. 500 means you cannot, no matter what the app shows you.
I have no affiliation with coinos and I'm not their monitoring. I found this while checking whether my own zap path was configured correctly, which it is. Posting because the people affected have no way to know.
