We just renewed the jabber.org certificate via @LetsEncrypt, the SHA-256 signature is A34F5C071542CECC9363302B536F48C92842C194AA0160B48759C9FD7C236441

Just installed a new Let's Encrypt cert at jabber.org. SHA-256 fingerprint is 1E 01 90 79 47 D7 50 73 26 95 CD DF 0A FC AD 23 B8 1B 4C 08 08 3F D0 93 64 62 A7 DD E6 66 1F DD. ~ Peter Saint-Andre

Jabber.org is migrating to Prosody! Performance might suffer temporarily as we run migration scripts and such. Thanks for your patience.

Jabber.org is down right now because of a major Internet outage in Iowa (where our data center is located). Stand by for further details.

And we're back!

We just installed a new security certificate at the jabber.org IM service. Big thanks to the Let's Encrypt community for their help debugging an issue we ran into, and to Dehydrated for the excellent certificate request script!

The Jabber.org IM service is planning a major server migration this weekend, January 14-15. The service may be unavailable for extended periods of time. You can view the live server status at status.jabber.org.

The jabber.org server migration is done! If you see any issues, feel free to poke Peter Saint-Andre

Just a reminder about our server migration tomorrow. jabber.org/notices.html

Server migration complete. We might have residual issues for a few days. Thanks for your patience. -- Peter Saint-Andre

We are planning a series of security improvements, including mandated encryption of client connections. Details at jabber.org/security.html

The jabber dot org IM service is under attack. Please see jabber.org/notices.html for details. We're working on fixes. Stand by for updates.

We've removed some weak TLS cipher suites and now receive an "A" grade from the IM Observatory! xmpp.net/result.php?dom…

Folks, we're aware that the jabber dot org certificate has expired and we'll have a new one installed pronto. Sorry about that! -- Peter Saint-Andre

We've installed a new certificate. FYI, some IM apps can't handle the stronger signature (SHA-256 vs. SHA-1). -- Peter Saint-Andre

We just installed a new digital certificate - the SHA-1 fingerprint is 2E:74:2C:EE:3B:DF:2C:1E:64:18:24:C4:45:BF:C7:0D:11:29:90:5E

Sorry about the late notice, but we switched our cert to Let's Encrypt. SHA-1 = 26:0B:2A:85:F4:53:EF:F7:87:59:FC:0D:9A:9A:3F:31:B9:6F:55:F4.

We're experiencing connectivity issues over IPv4 and IPv6 right now, caused by upstream issues. We're investigating!

DNS issues should be fixed now, changes are propagating. Sorry about the outages. Process improvements on the way. - Peter Saint-Andre

TFW you find a lost email folder with 2,000+ support requests. Working my way through them now. :( Peter Saint-Andre