Skip to main content
An issue is Sitepulse’s record of something going wrong. Automatic monitoring opens one when a site crosses the thresholds you’ve set, and it bundles repeated failures for the same site and check together - so a site that’s been down for an hour is one issue to deal with, not a hundred separate alerts.
On-demand checks save results to check history and can send completion notifications, but they do not open or resolve issues.

​
When issues are created

Sitepulse opens an issue when an enabled automatic check meets the problem thresholds configured under Monitoring. Examples include:
  • Repeated status failures after confirmation retries, based on the selected incident response codes
  • Invalid or expiring SSL certificates
  • DNS hard failures or missing expected records
  • Broken-link counts above your threshold across consecutive crawls (after team or site link filters are applied)
  • Performance scores, TTFB, or load time (TTI) outside configured limits
When the underlying problem clears on subsequent automatic checks, Sitepulse marks the issue resolved and can send recovery notifications.

​
How quickly do issues open?

Different failures use different evidence, so they open on different timelines:
  • Status, SSL, and DNS failures are confirmed before alerting you. A failed scheduled check triggers a confirmation retry, and the issue opens once the required consecutive failures are reached. With default settings, a persistent failure produces an issue and alert within a few minutes, while a momentary blip produces nothing.
  • Broken-link and performance issues open after their configured consecutive breach threshold is met.
DNS expected-record issues also require matching observations from multiple resolvers before Sitepulse treats a record change as confirmed. See Monitoring settings for the full threshold reference.

​
Issue lifecycle

You can acknowledge and resolve issues yourself, or let Sitepulse resolve them automatically once checks start passing again. If the same problem comes back - same site, same tool, same kind of failure - Sitepulse reopens the original issue instead of creating a new one, so a recurring fault stays as a single thread of history rather than cluttering your list.

​
Issues page

Use Issues to filter, sort, and act on incidents for the current team. Available filters:
  • Status - Active, Open, Acknowledged, or Resolved
  • Site - one site or all sites
  • Tool - Status, SSL, DNS, Broken Links, Performance, or all tools
  • Severity - Critical, Warning, Info, or all severities
You can sort by summary, site, tool, status, or opened date. Issue summaries link to the related check result when Sitepulse has one.

​
Actions

Select one or more issues to use bulk actions. Single-row actions follow the same rules. Manual resolution does not stop future automatic checks; if the same failure happens again, Sitepulse can reopen or create an issue according to the normal evaluation rules.
Broken-link entries appear on the Issues page only after the site breaches its broken-link issue rule. A latest broken-link check with one failed URL may show on the Sites page without opening an issue if it is below your threshold.

​
Severities

​
Notifications and quiet time

Issue lifecycle events drive outbound alerts:
  • Issue detected - when a new issue opens (including when a resolved issue reopens)
  • Issue resolved - when automatic monitoring confirms recovery
  • Escalation - follow-up reminders while an issue stays open or acknowledged (when escalation is enabled)
Configure destinations under Notifications. Quiet time (set in Monitoring) suppresses outbound alerts but does not stop checks or issue evaluation. See Notifications for channel setup.

​
API access

Integrations can read issues through the v1 API with the issues:read scope. The API is read-only - acknowledge and resolve actions are available in the dashboard only. See Issues endpoints and the Issue resource.