Website and API
Public pages and the monitoring endpoint are responding.
LIVE SYSTEM CHECK
Refresh status
Meetin.gs system health
A clear view of the services behind booking pages, group polls, accounts, and meeting communication.
ALL CORE CHECKS PASSED
Core scheduling systems are operational
Live application and scheduling-data checks passed.
LAST CHECKED
Checks run again whenever this page is refreshed.
CURRENT STATUS
Service components
Core checks read the live application database. Provider rows describe configuration, not a promise about an external provider's network.
Operational
Meeting scheduler
Booking links and group polls can read the required scheduling records.
Scheduling data store
The connection and core scheduling tables passed a live read check.
Google account sign-in
Google OAuth credentials are configured. Provider availability is confirmed during sign-in.
Lifecycle email
Email credentials and a sender address are configured. Inbox acceptance is recorded per delivery.
Useful checks, without exposing private data.
The page verifies that the application responds, the data store accepts a read, and the tables required for meetings, responses, and accounts are present.
- No participant or organizer records are displayed.
- No credentials or provider responses are exposed.
- The check does not create a meeting or send an email.
Configuration is different from delivery.
Google sign-in and email are marked configured when the required credentials exist. Their external availability and recipient acceptance are verified during the real action.
Open the machine-readable health endpointNEED HELP?
Seeing a problem that is not shown here?
Include the page address, approximate time, meeting code if safe to share, and the action you were taking. Never send a private management token.
