Re: N2Usenet nym gateway issue

> Our Nym requester on Victor recently stopped forwarding traffic because
> the public Nym gateway it was registered with became unreachable and
> refused connections on both its main WebSocket endpoint and fallback IP
> address.

> The gateway was not operated by us or directly by the Nym team. It was a
> public Nym gateway run by an independent network operator.

> The exact reason for the outage remains unknown. Possible causes include
> a stopped service, reverse proxy failure, firewall changes, a software
> incompatibility, or an issue with the operator’s server.

  One possibility left out: It could be haunted!

> We restored service by registering a working gateway, updating the
> corresponding requester address on Pietro, and verifying the complete
> SMTP and TLS path.

> Operating our own Nym gateway is also being considered to  reduce
> dependence on randomly selected third-party infrastructure.