Create a monitor

A monitor is one check fastry repeats for you. Open Monitors, choose New monitor, pick the kind of check and save. fastry then records uptime, response time and, for a website, the performance measurement, deployments and SEO details.

Create the monitor

Open Monitors and choose New monitor. Select what you want to monitor.
Enter the address: a URL for a website or an API, or a host name for a ping test, a port or UDP. Give the monitor a name you will recognize in alerts.
Optionally add the domain to a group, choose the check interval and, for a website or an API, the check location.
Open Advanced options when you need a keyword on the page, a timeout, request headers or the HTTP method. Then choose Create monitor.

New monitor

Which monitor to use

Website monitoring

Use this for a shop, a landing page or a blog. fastry calls the URL and checks that the page answers, that the status code is fine and that the SSL certificate is valid. On the same monitor you follow the performance measurement, deployments and, with keyword tracking, your Google rankings.

API

Use this for a health URL, a login service or a payment API. fastry checks the status code, the content type, the JSON and how long the answer took. You can send a method, a body and headers such as an API key, stored encrypted and sent only to that address.

Port (TCP)

Use this when a database, a mail server or SSH must accept connections, or when a port should stay closed. fastry opens a TCP connection to the host and port and alerts when the result flips.

Ping test

Use a ping test when you want to know whether a server is reachable at all, and how long a packet takes to get there and back. fastry sends a few ICMP packets and records packet loss and round-trip time. Lost packets mark the monitor as degraded. From the loss threshold you set, it is down and you can get a downtime notification.

UDP

Use this for a DNS server or an NTP time server. fastry sends a UDP packet (a DNS request, an NTP request, or your own text) and checks that an answer comes back.

How do I measure how fast my page is for users in other countries?

Create a ping test for the server and a website monitor for the page. The ping test shows the round trip: how long a packet takes to reach the server and come back. That is the delay visitors in that country wait before the page even starts. The website monitor loads the page and keeps the response time. Its performance measurement adds the loading time and the Core Web Vitals, so you see how the page feels for someone waiting on it.

fastry measures from Helsinki in Finland and from Berlin in Germany. From the Starter plan you pick this check location for website and API monitors. A visitor in Germany is close to Berlin; a visitor in northern Europe is close to Helsinki. Singapore and Canada are coming soon, so the same ping test and the same website monitoring will cover Asia and North America.

Rankings, deployments and performance on a website monitor

Performance measurement

fastry measures the loading time on a schedule. Google PageSpeed Insights supplies the scores and the Core Web Vitals (LCP, INP, CLS), including field data from real Chrome users when Google has them. fastry’s own run loads the page in a browser and shows a waterfall of every file. You see whether the page got slower than last week.

Deployments

Connect GitHub, GitLab, Bitbucket, Vercel or Netlify, or report a deployment with your API key. Each release becomes a marker on the uptime and performance charts. fastry compares the values before and after, and can notify you when the new version is slower or broken.

Google rankings

Add the keywords that should bring visitors, with the country (Germany, Austria, Switzerland, the United Kingdom or the USA) and the device (desktop or mobile). fastry checks the Google position every day and keeps the history. A drop, a keyword leaving the top 10, or a new keyword in the top 10 can trigger a notification.

Downtime and keyword alerts

Further settings

The check interval is how often fastry runs the test. Shorter intervals are in the higher plans. The timeout is how long fastry waits for an answer.

For a website you can require a text on the page, or require that a text is absent. That catches an error page which still returns a success status. HEAD is the faster request. GET is the one that can read the page text.

You can create the same monitor from the HTTP API and from an AI assistant over MCP, with the API key from API & Webhooks.