Hyperping logo.
Use Cases Use CasesArtboardMonitoringReceive alerts & collect performance metricsArtboardStatus PageBuild confidence in your brand and keep your visitors in-the-know.ArtboardIncident ManagerInform your users via the status page and collaborate with teammatesIntegrationsEmailSMSTwilioSlackTelegramPagerDutyOpsGenieGoogle SSOHelpDocsPricingTalk to usGet started →
Getting startedQuickstartCreate a monitorEdit a monitorDelete a monitorDatacenter regionsSSL monitoringGetting startedQuickstartCreate a status pageCustom domain setupSMS NotificationsStatus Page JSONCreate maintenanceOpsGeniePagerDutyWebhooksTwilio
Docs homeMonitoringCreate monitor

How to create a monitor

To follow this tutorial, you will need a Hyperping account, which you can create from the Hyperping new account registration page if you don’t already have one.

After you log into the Hyperping dashboard in the Monitor section, you can click on the large "New monitor" button at the center.

This will open a modal that lets you specify configuration options for your monitor, like its name, its URL or its HTTP method (GET, POST, HEAD...).

Choose a HTTP method

GET and HEAD are the most common methods to perform HTTP pings. Most of the time, HEAD requests are enough because Hyperping performs TTFB (Time To First Byte) checks, which only reads the response headers, independantly from the response body.

  • GET: The GET method is used to retrieve information. GET methods are said to be safe methods as these requests do not change the state of the resource.
  • HEAD: Same as GET, except that the server does not return a message-body in the response.
  • POST: The POST request is used to send data to the server. The response should have a response code 201 (Created).
  • PUT: The PUT method is primarly used to update an existing resource.
  • DELETE: The DELETE method, as the name applies, is used to delete resources.
  • PATCH: The PATCH method is used to make partial update on a resource. PUT should only be used if you’re replacing a resource in its entirety.

Choose an Expected Status Code

For the main use case, users are opting for the default way to monitor uptime: any status code between 200 and 299 (included) will be considered as up.

In other cases, you may have a endpoints that, for example, are unauthorized and should remain unauthorized (401) or forbidden (403) and are yet up and running! You can then select from the list the expected status code that your monitor should respond back.

Specify request Body and Headers (optional)

The most popular requests Headers are:

  • Authorization: Carries credentials containing the authentication information of the client for the resource being requested.
  • Content-Type: Indicates the media type (text/html or text/JSON) of the response sent to the client by the server, this will help the client in processing the response body correctly.

Finalize and save

You can now click the Save button, which will trigger the first ping, compute the metrics and redirect you to the detailed view which includes metrics and graphs concerning your monitor.

Choose datacenter regions

By default, a monitor is set with 3 locations: SF0 (San Francisco), NYC (New York City) and FRA (Frankfurt). You can edit at anytime the selection after you created the monitor, in its Region tab. You need to have at least one selected region, and you are able to select all of them if you need to. Here is the list of all available regions.



It is recommended to use datacenter regions where you users are located if you measure response time as a performance. More distant server locations may increase the server’s latency without providing any practical benefits.

Note: When Hyperping detects an error from one region, it will automatically perform the same request from at least 2 other regions to prevent false positives. If you only selected one or two regions, it will double check by pinging from 2 other locations that you haven't selected.

DashboardBlogDocsPricingStatus