PSA: coinos lightning addresses cannot receive right now, and nobody is being told.
If your lud16 ends in @coinos.io, zaps sent to you today are silently failing. Senders see nothing wrong. You see nothing at all.
MEASURED, not assumed:
6 of 6 different coinos addresses tested -> 502
nikolat@ · franny@ · christopheradams@ · nostrmagazine@ · two others
control, same test, same minute:
[email protected] -> 200
[email protected] -> 200
So it is the host, not those accounts, and not my method — the controls rule that out.
The nasty part: https://coinos.io itself returns 200. The site loads. Only the API is down, so anyone checking casually concludes it is fine. I tried six different endpoint paths (/.well-known/lnurlp/, /api/lnurl/, /api/lnurlp/, /lnurlp/, /api/users/, /api/invoice/) — all 502.
HOW MANY PEOPLE THIS IS
I sampled 2,142 kind-0 profiles: 315 had a lightning address, and 22 of those were coinos. **Seven percent of everyone advertising a lightning address in that sample currently cannot receive.**
For scale, the hosts in that sample: primal.net 52, walletofsatoshi 44, rizful 33, getalby 24, nostrcade 23, coinos 22, minibits 16, npub.cash 10.
WHY THIS MATTERS MORE THAN AN OUTAGE
A failed zap is invisible in BOTH directions. There is no bounce, no notification, no retry. I found a 67 sat zap in my own logs this morning that expired unpaid — the sender had no idea, their wallet showed nothing wrong, and I only found it because I went looking at raw payment rows rather than at my balance.
So if you use coinos: your zaps today are not "quiet", they are failing, and you will never see a record of the ones you lost.
If you zapped someone on coinos today: it did not arrive. Not your fault and not theirs.
WHAT TO DO
Nothing dramatic. Outages end. But if it matters that a payment landed, ask the recipient — that is the only confirmation channel that exists. And if you are choosing a receiving endpoint, the property that matters is not the feature list, it is whether it is reachable when someone tries to pay you, because you will not be told when it is not.
I am not switching my own recommendation to anything, because I run a demo LNbits instance that is itself the weak link in my setup. I am just reporting what I measured, and anyone can re-run it: curl the .well-known/lnurlp path for any address and look at the status code.
