Ask your monitoring. It answers back.

• Ask anything about your uptime

  Reads run immediately, straight from your live account data. Anything that changes something waits for your go-ahead.

• 

Answered instantly

• Instant fleet status

  Current status, URL, uptime percentage and response time for every monitor on the account, in one sentence instead of a dashboard grid to scan.

  "Is anything down right now?"

• Uptime math on demand

  Uptime percentage, total downtime, incident count and average response time for any monitor over 1, 7, 30 or 90 days. No export, no report to build.

  "Give me uptime and average response time for checkout over the last 7 days."

  Free-form date ranges go through account analytics.

• Account-wide analytics

  Aggregate questions over a date range you choose, filtered by continent, region or a subset of monitors, grouped by monitor, region or day. Reporting work, answered in a sentence.

  "How was our uptime in Europe last week, grouped by monitor?"

  Capped at 93 days per question. If archived data can't be reached, the answer is flagged partial rather than presented as complete.

• Downtime and event history

  Every online and offline event for a monitor over a date range, or the total downtime it accumulated over the last N days.

  "How much total downtime did the API have in the last 30 days?"

  Event lists default to 7 days; downtime totals default to 30 days.

• Account-wide event feed

  Everything that went offline and came back, across all monitors and heartbeats, in one chronological timeline.

  "Show me everything that went down or came back in the last 48 hours."

  Defaults to the last 7 days; ask for a wider window explicitly.

• Change history and audit

  What was created, updated or deleted across monitors and heartbeats, filterable by resource type and date range. Answers "did someone change this?" before you debug the wrong thing.

  "What changed on our monitors in the last week?"

  Covers monitors and heartbeats; defaults to the last 30 days.

Done with your approval

• Create, edit, pause, resume, delete monitors

  Spin up HTTP, TCP or ICMP monitors by describing what you want checked, then rename them, change the URL or check interval, or delete them from the same conversation.

  "Add an HTTP monitor for status.example.com, checked every minute."

  Your plan's monitor limit is enforced and stated plainly if you hit it.

• Cron and heartbeat management

  Create heartbeat checks, change the expected interval or grace period, pause, resume or delete them. Background jobs get the same depth as web endpoints.

  "Create a heartbeat for the nightly backup, expected every 24 hours with a 30-minute grace period."

  Missed-check alerts follow the heartbeat's existing notification settings.

• Incident management

  Open an incident with an initial update, post follow-ups, then resolve it with a closing message. From "why is checkout down?" to a published update in one conversation.

  "Open an incident for the checkout outage and post an update."

  Incidents attach to status pages rather than directly to monitors.

• Status page administration

  Create status pages, change their configuration and monitor lineup, attach a custom domain, or delete a page. Setting a custom domain triggers SSL provisioning automatically.

  "Put the API and checkout monitors on our public status page."

  Monitors and heartbeats you don't own are dropped rather than attached. Deleting a page also removes its incidents and maintenance windows; the assistant says so before you confirm.

• Scheduled maintenance windows

  Schedule a maintenance window on a status page, or delete one, so planned work is announced to customers in the time it takes to type the sentence.

  "Schedule maintenance on the status page for Saturday 02:00-04:00 UTC."

• Two changes, handled one at a time

  Ask for two changes at once and the assistant proposes the first, then moves to the second only after you've decided. No batch of changes ever rides on a single yes.

  "Pause the staging monitor and delete the old test one."

  Pending confirmations expire after 15 minutes.

Beyond uptime

Real user monitoring, domains, badges, tags and your monitoring IP allowlist, all in the same conversation.

Real user monitoring in chat

What your visitors actually experienced, asked the same way you'd ask a teammate. Everything RUM collects is a question away.

• Real-visitor performance

  Pageviews, load-time percentiles, TTFB and Core Web Vitals over a date range, answered from real visitor data rather than a lab test.

  "What's our p75 load time this week?"

  92-day range cap; the default window is the last 7 days.

• Timeseries and breakdowns

  Bucket any RUM metric by hour or day, or break it down by path, country, city, browser, OS, device or referrer, all in plain language.

  "Break down load time by country for the checkout page."

• Realtime visitor snapshot

  Visitors in the last 5 minutes, uniques and pageviews over the last 30 minutes, a per-minute series, plus top pages and traffic sources.

  "How many people are on the site right now, and what are they looking at?"

• JavaScript and HTTP errors

  Top JS errors and top HTTP errors from real sessions, with totals and an overall error rate. Catches breakage even when every uptime check is green.

  "What are the top JavaScript errors our visitors hit today?"

  92-day range cap.

• RUM usage and quota

  RUM request usage against your plan limit for the current billing period, including an over-quota flag. Billing visibility without leaving the chat.

  "How much of our RUM quota have we used this month?"

  Counted per billing period, not per calendar month.

• RUM site setup and control

  Create a RUM site and get the embed snippet back in chat, rename or re-domain it, enable or disable collection, or delete it.

  "Set up RUM for example.com and give me the snippet."

  Confirmation required. Deleting a site purges its collected data.

Everything else you monitor

• Domain expiration and WHOIS

  List monitored domains with registrar, WHOIS status and expiration date. Add, rename, toggle alerts, pause, resume or delete WHOIS checks.

  "Which of our domains expire in the next 90 days?"

  Just-added domains may briefly show blanks until the WHOIS lookup completes.

• Status badges

  List, inspect, create with sensible defaults, restyle or delete embed badges, with the ready-to-paste embed URL returned in chat.

  "Make an uptime badge for the API and give me the embed code."

  Creating, updating and deleting need a plan with customization enabled.

• Tags and organization

  List tags with usage counts across monitors, heartbeats and domains. Create, rename or delete a tag, or set a resource's full tag set by name.

  "Tag every staging monitor with staging."

  Setting tags replaces a resource's tags rather than adding to them.

• Monitoring IP allowlist

  The complete IPv4 and IPv6 source-address list for Pulsetic's checks, grouped by monitoring location, ready for a firewall or WAF allowlist.

  "Give me all your monitoring IPs so I can allowlist them."

  Matches the list published in the docs.