A live check of the only server Aurora uses — the rendezvous service that helps two phones find each other. It never sees your messages and keeps no logs; this page only tells you whether it is reachable.
Rendezvous server
Checking…Contacting api.auroramessenger.com…
This check runs in your browser, directly against the server. If it shows unreachable, the server may be briefly restarting for an update, or your network may be blocking it — your existing conversations are peer-to-peer and don't depend on it being up moment to moment.
The status above reflects whether the rendezvous server answers a request. It carries no message content, no node identities, and no user counts — there is nothing else for it to report.
Your conversations travel directly between phones. Even when the rendezvous server is down, an already-connected chat keeps working; the server is only needed to first find a peer or wake a sleeping device.
A running log of releases and site / server changes. The full app history lives in the changelog.
Site & infrastructure
18 June 2026 LatestWebsite and server updates (no app release).
/health liveness endpoint (which powers this page) and turned off API access logging, so no IP-to-node history is retained.v0.2.2-pre
17 June 2026An onboarding patch so a fresh install can actually receive messages.
v0.2.1-pre
17 June 2026A pairing-reliability patch.
v0.2.0-pre
17 June 2026The second pre-alpha — in-app video, calls that survive leaving the app, and a large internal cleanup.
v0.1.0-pre
14 June 2026The first public pre-alpha. Source published to GitHub under AGPL-3.0 with a signed APK.
Where Aurora is headed — direction, not dated promises.