import ligo.lvalert
LVAlert 1.5.5 has implemented stability fixes that we discussed over email: Re__some_stats_on_LVC_notices_received.eml.
I have been advised by the LVC Security Committee to implement TLSv1.1-1.2 encryption, which I'm tracking here. From what I can tell, this requires changes to the client and some server-side settings. The downside is, without the modifications to the client protocol, the listeners will not be able to connect to the LVAlert server after the server-side changes have been made. This will break GWCelery's communication with LVAlert. I don't have a firm ETA for this change yet: within the next couple weeks, after I've tested it more and finished the GraceDB/LVAlert security review.
I suggest that GWCelery change its LVAlert listener from its internal sleeklvalert module to the LVC ligo.lvalert. There aren't any API changes, the certs are the same, so I suspect that it should "just work" after changing the import. Let me know if I can help.