How to View System Status?
The status page helps you quickly see whether communication channels and platform modules are healthy, and whether an issue looks like a global messenger outage or something specific to your instance.
When You'll Need This
- You need to check channel availability (Telegram, Viber, WhatsApp, and others).
- Message delivery or modules seem unstable.
- You want to tell a provider-wide outage from a problem on your instance only.
- You want a quick health check before starting work.
What's Important to Know
- Status page — a monitoring screen in the help menu.
- Channels — status is based on telemetry across the ConnectiveOne instance network. The number and list of other instances are never shown. Until your instance is connected to network monitoring, the cards show the results of the instance's own checks (see "If the instance is not connected to network monitoring yet" below).
- e-chat channels — checks of the e-chat integration for Telegram, Viber and WhatsApp. Everyone with access to the page sees this section.
- Platform modules — internal checks for your instance (operator panel, files, statistics, and similar). The modules block and manual re-run are available to Root users.
- Refresh — the page periodically loads fresh data (about once per minute).
- Access — Root users always see the page. Other users need access granted in instance settings.
Before You Start
Step-by-Step Instructions
1. Open the Status Page
- Sign in.
- Open the help menu in the top navigation (question icon / Help).
- Select Status Page.
- If you do not see the item, ask an administrator — non-root access is configured in instance settings.
- The page opens with the current component state.
2. Review channel status
The Communication Channels Availability section shows channel cards for:
- Telegram
- Viber
- Facebook Messenger
Each card includes:
- Current status
- Short reason when one is available
- Status strip for the last hour — older minutes on the left, Now on the right
Scope switch (Root only):
- All instances — aggregated network view (useful for provider-wide outages).
- Current instance — status for your instance only.
Other users with access see the network view (All instances) without the switch.
If monitoring is unavailable for the current instance, the card shows "This instance is not connected to monitoring.".
If the instance is not connected to network monitoring yet
Until your instance is connected to network monitoring, the page works as before, from the instance's own checks:
- the cards show the channels the instance checks itself: Telegram, Viber, Facebook Messenger, WhatsApp and Email (the Email card checks that Google mail servers are reachable);
- each card shows the name, the status (Working, Error or Insufficient data) and the time of the last check (Checked at);
- there is no All instances / Current instance switch, no one-hour strip and no color legend;
- there is no Instagram card: the instance has no check of its own for it.
The network view appears without any action on your side once monitoring is connected for your instance.
3. Understand channel statuses
| Status | Meaning |
|---|---|
| Operational / Working | Metrics are within normal range. |
| Degraded performance | The channel works with limitations or worse metrics. |
| Unavailable / Error | Critical problems — attention needed. |
| Insufficient data | Not enough sample (little recent traffic or metrics temporarily unavailable). This is not necessarily an outage. |
| Not connected | The channel is not connected on this instance (in Current instance scope, when that can be determined). |
A color legend above the cards explains the timeline strip.
4. Review e-chat channels
Below the channel cards, the e-chat channels section shows Telegram (e-chat), Viber (e-chat) and WhatsApp (e-chat):
- Working means the e-chat API for that channel responds; Error means the check failed;
- the time of the last check (Checked at) is shown under the name;
- hover a card to see what is checked.
5. Review platform modules (Root)
- Click More details near the top of the page.
- The Platform Modules Health section appears — for the current instance only.
- Typical modules: operator panel, files and images, statistics, Fastline Pro, widget.
- When a module has a problem, its card shows Failure reason and Error code. Check failed means the check itself could not run (for example, the module is not configured on the instance), not necessarily that the module is down.
- Hover a module card for a tooltip about what is checked.
- Optionally click Restart Checks next to Hide details — modules and e-chat channels show Checking…, then statuses refresh and Checks updated appears.
Users who are not Root can see channels and e-chat channels; the modules block and manual re-run are Root-only.
6. Check the update time
Under the page title you see when data was last updated. If metrics are temporarily unavailable, a card may keep the last confirmed state with the note "Last confirmed status; waiting for fresh data".
What Happens Next
You can:
- tell a broad messenger outage from an instance-local issue;
- see whether a channel is connected at all;
- review the last hour of channel state before escalating to support.
How to Verify Everything Worked
- The page opens from the help menu.
- Channel cards show a status and, when data exists, a one-hour strip.
- Until the instance is connected to network monitoring, channel cards show a status and the check time, without the switch and the strip.
- The e-chat channels section shows three cards with the check time.
- As Root, the All instances / Current instance switch and the modules block after More details work.
- The updated-at time is visible and changes on the next refresh.
Related Materials
Important Notes
- The page does not list other instances or show how many exist — only an aggregated view.
- Insufficient data often means little recent traffic or temporary metric unavailability, not a confirmed channel outage.
- Only Root users can change non-root access to the Status Page in instance settings.