Status page
Real-time system status, incident history, and SLA commitments for elNudge.
Real-time system status for elNudge is available at status.elnudge.com.
What the status page shows
The status page displays the current health of each component of the elNudge platform:
| Component | What it covers |
|---|---|
| SDK CDN | Delivery of the elNudge JavaScript SDK to visitor browsers |
| Relay (WebSocket) | The real-time WebSocket connection used to stream behavioral events from the SDK |
| AI service | The AI engine powering chat responses and intent scoring |
| Analytics | Event ingestion pipeline and analytics dashboard data freshness |
| Dashboard | app.elnudge.com — the merchant control panel |
| API | api.elnudge.com — the REST API |
Status definitions
| Status | Meaning |
|---|---|
| Operational | The component is functioning normally with no known issues |
| Degraded Performance | The component is operational but slower than expected or with elevated error rates |
| Partial Outage | A subset of users or requests are affected |
| Major Outage | The component is unavailable or severely impaired for all users |
If you are experiencing an issue not reflected on the status page, contact [email protected].
Subscribe to status updates
You can receive notifications when an incident is opened, updated, or resolved:
Email — Click Subscribe to updates on the status page and enter your email address. You will receive an email at each status change.
RSS — Subscribe to the RSS feed at https://status.elnudge.com/feed.xml in any RSS reader.
Slack — On the status page, click Subscribe → Slack to connect status notifications to a Slack channel of your choice.
Historical uptime
The status page displays historical uptime data for the last 90 days per component. This includes:
- Daily uptime percentage
- Incident count and average duration
- Maintenance windows (excluded from uptime calculations)
Incident reports
For every incident with a severity of Partial Outage or higher, a written incident report is published on the status page within 24 hours of resolution. The report covers:
- What happened and when
- Which components were affected
- Root cause (where identified)
- Steps taken to resolve
- Actions being taken to prevent recurrence
SLA commitments
| Plan | Monthly uptime SLA |
|---|---|
| Starter | Best effort (no SLA) |
| Growth | Best effort (no SLA) |
| Scale | 99.9% |
| Enterprise | 99.95% |
Uptime is measured monthly and excludes scheduled maintenance windows. Scheduled maintenance is announced at least 48 hours in advance on the status page and by email.
If your Scale or Enterprise plan falls below its SLA commitment in a given month, contact [email protected] to request a service credit. Credits are calculated as a percentage of the monthly fee proportional to the downtime and must be requested within 30 days of the incident.