> For the complete documentation index, see [llms.txt](https://developers.hyp.co.il/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.hyp.co.il/enterprise/advanced-considerations/status-monitoring.md).

# System Status Monitoring

Hyp provides real-time visibility into the health and availability of its payment services through both dedicated **status pages** and **programmatic health checks**.

## Hyp service status page

The [main Hyp status page](https://smbusiness-status.hyp.co.il/) provides a real-time overview of Hyp's core systems. It is the primary resource for monitoring the health of Hyp gateway components such as the Payment API, payment page features, and the Hyp Console.

You can access the status page directly or through the Hyp Console in your production environment by navigating to the menu and selecting the **Status Page** link.

![Status page link in the Hyp Console](https://3255314327-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQDmIAW4sQ20lCItJGzcS%2Fuploads%2Fgit-blob-050334a2deccf12174234d7d2f95cbc561d91b62%2Fhyp-console-status.png?alt=media)

We recommend that you **bookmark the direct URL** so you can check system health even if the console itself is unavailable.

## Third-party service status page

Because Hyp integrates with various external providers to facilitate payments, we also maintain a separate [status page for third-party services](https://thirdparty-status.hyp.co.il/).

This page monitors the live availability of external payment providers and networks, including credit card networks (Max, Isracard, and Cal), gift card providers, and 3D Secure (3DS) authentication providers.

These services are operated externally. While Hyp services may be running normally, incidents affecting these providers can still prevent you from processing transactions through them.

## Programmatic health checks

You can also perform automated health checks directly through the Hyp API using the `performMonitors` command with the `NOOP` monitor.

The `NOOP` (No Operation) monitor acts as a basic "ping" to the Hyp Enterprise system. It verifies that core services are available and responsive to API requests without performing any actual financial transactions.

To check the system status, send a `performMonitors` request with `moduleName` set to `ashrait` and `monitorName` set to `NOOP`:

```xml
<ashrait>
    <request>
        <version>2000</version>
        <language>ENG</language>
        <command>performMonitors</command>
        <terminalNumber>0882818012</terminalNumber>
        <performMonitors>
            <monitor>
                <moduleName>ashrait</moduleName>
                <monitorName>NOOP</monitorName>
            </monitor>
        </performMonitors>
    </request>
</ashrait>
```

Here's what a response may look like:

```xml
<ashrait>
    <response>
        <command>performMonitors</command>
        <dateTime>2026-07-21 10:56</dateTime>
        <requestId/>
        <tranId/>
        <result>000</result>
        <message>Permitted transaction</message>
        <userMessage>Permitted transaction</userMessage>
        <additionalInfo/>
        <version>2000</version>
        <language>Eng</language>
        <performMonitors>
            <monitor>
                <moduleName>ashrait</moduleName>
                <monitorName>NOOP</monitorName>
                <monitorValue>0</monitorValue>
                <monitorResult>000</monitorResult>
                <monitorMessage/>
                <monitorData/>
            </monitor>
        </performMonitors>
    </response>
</ashrait>
```

If `monitorValue` is `0`, the system is healthy. Any non-zero value indicates that an error or delay was encountered. In this case, `monitorResult` returns an error code, and `monitorMessage` provides details about the error.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.hyp.co.il/enterprise/advanced-considerations/status-monitoring.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
