Alertly.Net

Sharing

Status pages

Status pages show your customers whether your services are working, without them having to ask. They update automatically from your monitors and servers.

Create a status page

Open Status pages → New status page and choose:

  • Name, address and description: the page lives at https://alertly.net/status/your-slug. The address is made from the name if you leave it blank, and must be 3 to 60 characters.
  • Branding: upload a logo (JPG, PNG, GIF, WebP or AVIF, up to 5 MB), pick an accent colour and add a link back to your website. Pages without a logo show the Alertly.Net logo.
  • Components: the monitors and servers to show. Give each a Public name. If you leave it empty, the monitor's or server's own name is shown, so set one if that name is internal.
  • Groups: put components in groups such as "API" or "Europe". Each group shows its worst status and average uptime. Visitors can collapse groups, and their browser remembers it.

Pages are drafts until you tick Published. Team members can preview a draft. Anyone else gets a "not found" page.

What visitors see

  • An overall status: All systems operational, Maintenance in progress, Some systems are degraded or Some systems are down.
  • 90 days of daily uptime bars for each component.
  • Your team's ongoing public incidents, and those resolved in the last 7 days, with their updates and published postmortems. Affected components are worked out from the alerts linked to each incident.
  • Public maintenance affecting this page's components, up to 14 days ahead.
  • Incident history with every public incident, and a page for each one you can link to.
  • A page for each component with its 7, 30 and 90-day uptime, response time and recent incidents. Servers are at /servers and websites at /websites. Both show response time, with a time filter from the last hour through 30 days, and both refresh every minute.

The page refreshes every minute. Only things you mark as public are shown. IP addresses, host names, process lists and internal notes are never published.

Subscriptions

Tick Email updates and visitors of a published page can choose Get updates to subscribe by email. They confirm their address within 2 days, then get an email for every public incident in your team and each update you post. Every email has an unsubscribe link.

RSS feed

Every published page has an RSS feed at https://alertly.net/status/your-slug/feed.rss, linked from the RSS icon in the page header. It lists up to 50 incident updates from the last 90 days and upcoming maintenance, and works in any feed reader and in Slack's RSS app. Drafts have no feed.

Use your own domain

You can show a page on your own address, such as status.example.com, instead of https://alertly.net/status/your-slug.

  1. Open the status page, find Custom domain, enter the domain and click Save domain. Enter just the name: no https:// and no path.

  2. At your DNS provider, add the two records shown on that card. Each has a copy button:

    • a TXT record on _alertly. plus your domain, which proves you own it. The value starts with alertly-verify= and is unique to this page and domain;
    • a CNAME record from your domain to the target shown, which sends visitors to the page. For a root domain like example.com, use your provider's CNAME flattening or ALIAS record.

    Some providers want just the first part of the name, such as status or _alertly.status.

  3. Click Verify domain. It tells you if a record is still missing. You can also just wait: we check every few minutes and connect the domain by itself once both records are live.

Once the domain is connected, the card shows it as connected and the DNS records are hidden.

The domain starts working once it's connected and the page is published, with a free secure (HTTPS) certificate that renews by itself. The first visit can take a minute while the certificate is issued. Keep both records in place afterwards. Changing the domain means connecting it again, with a new TXT value.

Using Cloudflare for your DNS? Set the CNAME to DNS only (grey cloud), not Proxied (orange cloud). A proxied record sends visitors to Cloudflare's servers instead of ours, so we can't connect the domain, and the page shows a Cloudflare error such as 1014, 525 or 526.

The card shows Waiting for DNS until the domain is connected. We stop checking a week after you save it, so save it again if you add the records later. A domain can only be used by one status page. To stop using it, clear the field and choose Save domain, then delete both records.

Visiting the domain shows the page. Only that status page and its incident, component and feed pages are served there. Nothing else from Alertly.Net is available on it.

Tips

  • Use names your customers recognise ("Website", "Payments") rather than hostnames.
  • Post a public incident update early, even if it only says "Investigating". Silence makes people anxious.

Still stuck? Read troubleshooting.