Point your uptime monitor at your community’s /health/ URL so your team is alerted when your Bevy instance is unavailable. A healthy response includes "status": "OK". This check is for your instance — it does not replace the Bevy status page.
Uptime monitoring watches your community URL on a schedule and alerts your team when the site stops responding the way it should. Use it so you learn about an outage from your own tools — not only from members who cannot sign in, register, or open an event page.
Why set up instance uptime monitoring
Your Bevy community runs on its own domain. When that site is unavailable, organizers and members cannot complete everyday jobs until it recovers. An uptime check gives your operations or IT team:
- Earlier notice — Alerts fire when the health check fails, so you can investigate before support volume spikes.
- A clear signal for your instance — The check targets your community domain, not a generic Bevy marketing page.
- Evidence for incident response — Timestamps from your monitor help you confirm when the site became unreachable and when it recovered.
- Independence from member reports — You do not have to wait for someone to say the site is down.
Note: Instance uptime monitoring does not replace the Bevy status page. Use both: your /health/ check for your community site, and Check the Bevy status page when you need Bevy’s platform-wide service status.
| Check | What it tells you | What it does not cover |
|---|---|---|
Your instance /health/ URL
|
Whether your Bevy community site is reachable and responding as healthy. | Bevy platform-wide incidents across many customers, or whether one virtual room, booth, or session is working. |
| Bevy status page | Whether Bevy’s shared platform services have a reported incident or maintenance window. | Whether your specific community domain is up. A green status page does not prove your instance is reachable. |
Tip: A healthy instance check still does not prove that one Bevy Virtual Meetup room, conference booth, or webinar session is working. Those are separate surfaces. Use this endpoint for whole-site availability only.
What the health endpoint returns
Bevy exposes a public health URL on every community instance. No sign-in or API key is required.
-
URL:
https://<your-domain>/health/(include the trailing slash) -
Method:
GET -
Healthy response: HTTP
200with a JSON body that includes"status": "OK"
A healthy body looks like this (your monitor may also see a version field next to status):
{"status": "OK", "version": "…"}Treat the instance as unavailable when any of the following is true:
- The request times out or cannot connect
- The HTTP status is not
200 - The JSON
statusvalue is anything other thanOK
Important: Do not configure your monitor to require an exact body match of only {"status": "OK"}. A healthy response can include additional fields (for example version). Match on HTTP 200 and "status": "OK", or on the presence of that status value in the body.
Set up the check in your monitoring tool
Use any uptime or synthetic monitoring tool your organization already trusts (for example an external ping service or an internal synthetic check).
- Create a new HTTP(S) monitor or check.
- Set the request URL to
https://<your-domain>/health/, replacing<your-domain>with your community’s domain (the same host members use in the browser). - Use method
GET. Do not add authentication headers, cookies, or API keys — the endpoint is public. - Configure success criteria:
- HTTP status
200 - Response body includes
"status": "OK"(or a JSON field check forstatusequalsOK)
- HTTP status
- Choose a check interval that matches your operations needs (many teams use every 1–5 minutes).
- Route alerts to the people who should respond when the community site is down (for example on-call, IT, or community operations).
- Run the check once manually and confirm it passes while the site is healthy.
Tip: Keep the check on your production community domain. A staging or preview host is a different instance and will not tell you whether members can reach the live site.
When the check fails
- Open the failing URL in a browser or with a simple
GETrequest and confirm whether you still see"status": "OK". - Check the Bevy status page for a platform-wide incident or maintenance window. See Check the Bevy status page.
- If status.bevy.com is clear but your
/health/check still fails, contact Bevy Support with your community domain, the time the monitor first failed, and the response or error your tool recorded.