Authentication
OperationalLogin and session validation are responding normally.
System status
Live view of Plexidy services.
Check component health, recent incidents, and planned maintenance.
Primary actions
See live component health
Refresh the snapshot or contact support if you see unexpected behavior.
Last updated: February 24, 2026 4:00 PM
Refreshing status
Gathering the latest component signals for this workspace view.
Scheduling API
OperationalAppointment create/update requests are within normal latency bounds.
Billing connector
DegradedMinor delays observed in invoice sync; monitoring in progress.
Analytics pipeline
OperationalDashboard calculations are processing under expected thresholds.
Current status / summary
Overall platform health
Area
Summary
Availability
All core services are online; billing connector under observation.
Performance
API latency within target ranges for scheduling and auth.
Support
No active incidents; latest history shown below.
Maintenance
Planned work
No maintenance scheduled
There are no planned maintenance windows this week. Planned work will appear here with timing and impact scope.
Recent activity / history
Latest incidents and communications
-
Feb 7, 2026 — Billing sync latency
Intermittent delay in invoice synchronization. Service remained available; issue mitigated and monitored.
-
Jan 29, 2026 — Authentication spike
Short authentication error increase during deployment window. Rollback completed within 14 minutes.
-
Jan 14, 2026 — Scheduled maintenance
Planned maintenance completed without disruption to appointment management workflows.
No incidents in the last 90 days
There are no open or recent incidents to report. Subscribe to updates or check the component board for live signals.
Stay informed
Subscribe to updates
Use release notes and changelog to track functional changes.
Bookmark this page
Keep the status board handy for quick health checks.
Escalate with context
Include component names and timestamps if you open a ticket.
Operational depth
Use status visibility to coordinate response decisions in real time
Status communication should distinguish component health, incident scope, and recovery progress so teams can make informed operational choices.
Primary audience
Incident responders, managers, and customer-facing teams
Decision focus
Decide whether operations can continue, degrade, or require contingency procedures
Operational risk
Without clear status signals, teams either overreact or miss early degradation indicators
Field scenario
Service latency rises and operations must decide whether to pause customer-facing commitments.
Execution walkthrough
1. Frame the objective
Status communication should distinguish component health, incident scope, and recovery progress so teams can make informed operational choices.
2. Align participants
Incident responders, managers, and customer-facing teams
3. Validate the decision
Decide whether operations can continue, degrade, or require contingency procedures
4. Mitigate known risk
Without clear status signals, teams either overreact or miss early degradation indicators
Interpretation matrix
Signal
Interpretation
Operational scenario
Service latency rises and operations must decide whether to pause customer-facing commitments.
Successful outcome
Successful use of this page leaves teams with clear direction on Decide whether operations can continue, degrade, or require contingency procedures.
If skipped
Skipping this step often introduces Without clear status signals, teams either overreact or miss early degradation indicators.
Recommended next step
Pair status interpretation with contact support when impact exceeds local runbook limits.