> For the complete documentation index, see [llms.txt](https://support.incidents.cloud.solarwinds.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.incidents.cloud.solarwinds.com/integrations/alert-source-integrations-native/hyperping.md).
# Hyperping
[Hyperping](https://hyperping.io/) is an uptime monitoring platform for websites, APIs, and public status pages.
Route detailed alerts from Hyperping to the right users in Squadcast.
### How to integrate Hyperping with Squadcast
### In Squadcast: Using Hyperping as an Alert Source
1. Navigate to **Services** -> **Service Overview** -> select or search for your Service. Expand the accordion -> In the Alert Sources section, click **Add**.
1. Select **Hyperping**. Copy the displayed **Webhook URL** to [configure](#in-hyperping-set-up-a-webhook-for-squadcast) it within **Hyperping.** Finish by clicking **Add Alert Source** -> **Done**.
{% hint style="warning" %}
**Important:**
When an alert source turns Active, it’ll show up under Configured Alert Sources, you can either generate a test alert from the integration or wait for a real-time alert to be generated by the Alert Source. An Alert Source is active if there is a recorded incident via that Alert Source for the Service.
{% endhint %}
### In Hyperping: Set up a Webhook for Squadcast
1. Click on **Project** and navigate to **Project settings**
2. Paste the previously copied Squadcast **Webhook URL** in the **URL** field under the **Webhook** section
{% hint style="info" %}
**Information**:
You can test the newly configured webhook by clicking on `Down test`. This will trigger a test alert in Squadcast. Clicking on `Up test` may or may not send out the *correspoding* resolve signal to Squadcast for auto-resolution of the newly triggered incident.
However, if you see that a test alert is triggered in Squadcast when you click on `Down test`, you can be rest assured that the integration will work as expected.
{% endhint %}
{% hint style="info" %}
**Note**:
You can configure webhooks in Hyperping across different Projects as well.
That is it, you are now good to go!
In Hyperping, whenever an event is generated with `down: true`, an incident will be created for it in Squadcast. When an event is generated with `down: false`, the corresponding incident will automatically get resolved in Squadcast as well.
{% endhint %}
{% hint style="info" %}
**Helpful Links to Hyperping's Documentation**:
You can find more information on setting Webhooks up [here](https://hyperping.io/docs/integrations/webhooks).
{% endhint %}
*Have any questions?* [*Ask the community*](https://community.squadcast.com/view/home)*.*
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://support.incidents.cloud.solarwinds.com/integrations/alert-source-integrations-native/hyperping.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.