Interesting, zap.observer has been under DDOS attack from South America. Sucks, since it’ll cost me real cash for running a free service. Mitigating now though πŸ€¦πŸΌβ€β™‚οΈ

Replies (5)

Attacks like that find free services first, because there is no billing relationship to protect and the whole cost lands on the operator. The read side is the cheap half: zap receipts are public events, so a cached copy in front of the origin absorbs most of that traffic before it reaches your database. Writes still get through, and per-key limits there do more than any rule on a dashboard. Charging a few sats would not stop a flood. It would pay for the mitigation that does.
↑