# System Status and Notifications

RoamingiQ maintains a public status page where you can view real-time system health and any ongoing or past incidents. This page contains all data from June 1, 2025 onward.

This is the primary place to check during an issue before contacting support.

### How and When To Use the Status Page

You can view real-time system status, active incidents, and historical incident reports at <https://status.roamingiq.com>

The status page should be your first stop when investigating an issue. It provides:

* Current system status across core services
* Active incidents and ongoing updates
* Historical incidents and resolution timelines

If there is a broader system issue, it will be reflected on the status page. If you do not see your issue listed, you can continue troubleshooting using other Knowledge Base articles or contact support through the normal channels.

### How To Receive Incident Notifications

You can subscribe to receive notifications when incidents are created, updated, or resolved. VAULT Administrators will not be automatically added to this notification list.

To unsubscribe, click the unsubscribe link at the bottom of any incident notification e-mail or the confirmation e-mail you received after subscribing. You can also reach out to <support@roamingiq.com> to unsubscribe any user.

#### Important recommendation

We do not recommend that individual users subscribe directly to incident notifications. Instead, we strongly recommend that each customer:

* Create an internal distribution list (email), and/or
* Use an internal channel (such as Microsoft Teams or Slack)

Then:

* Subscribe that single email address or channel to the status page

#### Benefits

* Employees can be added or removed internally without needing to manage subscriptions in an external service.
* Notifications stay consistent even as teams change.
* Avoids duplicate or stale subscriptions over time.
* Keeps your organization’s alerting clean and controlled.
* RoamingiQ makes no assumptions about who should or should not receive these notifications, putting it in our customer's control.

For example:

* `support@yourcompany.com`
* `noc@yourcompany.com`
* A Teams or Slack channel integration

Because subscriptions should be tied to a shared distribution or channel, please work with your internal administrators to ask if your company already has a distribution list subscribed, before subscribing to alert notifications.

#### I Am Already a Network Admin or SIEM Admin, Will I Receive Notifications?

We have learned from customer feedback that assuming your Network Admin list and Notification list are the same, is incorrect. As a result, we are running this notification system separate from our [admin roles](/network-administrator-console/network-operator-settings/network-administrators.md). Although this requires an additional step to subscribe, it puts total control in your hands for who receives widespread system alerts.&#x20;

If your organization wants SIEM Administrators auto-subscribed, you can simply create an internal distribution list and enroll that e-mail address and a [SIEM Administrator](/network-administrator-console/network-operator-settings/network-administrators.md#network-administrator-roles) and subscribe it to this status page.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.roamingiq.com/getting-started/system-status-and-notifications.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
