Uptime and incident management

Know first.
Fix fast.
Tell everyone.

Xuptify checks your websites and APIs every 30 seconds from around the world, pages the right engineer the moment something breaks, uses AI to point to the likely cause, updates your status page and turns every incident into a clear timeline.

Monitor 10 sites free
30 s
check interval on paid plans
10
regions in India and abroad
2+
regions confirm before anyone is paged
  • HTTP and HTTPS
  • API
  • Keyword
  • SSL expiry
  • Domain expiry
  • Ping and TCP
  • Cron heartbeat

Where it runs

Built around the pages that earn your money.

Teams start with the one URL that hurts most when it fails, then add the rest in an afternoon.

  • Ecommerce

    Sale nights, payment callbacks and the checkout that pays the bills.

    /checkoutpayment webhooksearch API

  • SaaS

    Login, core APIs and background jobs your customers never see until they stop.

    /loginapi/v2billing cron

  • Fintech

    Strict SLAs, regulator-friendly incident records and transparent status pages.

    UPI callbackKYC APISSL

  • Edtech

    Exam days and live classes where five minutes down means thousands of students.

    video APIexam portalLMS

  • IT services

    Many environments, many clients, one on-call rota and monthly SLA proof.

    client portalsVPNTCP 443

  • Agencies

    A branded status page and a white-label uptime report for every client site.

    client sitesdomainsSSL

The platform

One pulse, from first failed check to final report.

Five parts that share one timeline, so nothing is copied between tools while customers wait.

BEAT 01every 30 s

Uptime Monitors

Every endpoint, checked from where your customers are.

HTTP, API, keyword, SSL expiry, domain expiry, ping and cron-job heartbeat checks from Mumbai, Delhi, Bengaluru and seven global regions. A failure must be seen by two regions before it counts.

  • JSON assertions on API responses
  • SSL warnings at 30, 14 and 7 days
  • Heartbeat URLs for cron jobs and queues
Explore Uptime Monitors
Monitors · 24 active22 up
AllDown 1Degraded 1Paused 0
  • api.shopkart.in/checkoutAPI · POST212 ms99.98%
  • shopkart.inHTTPS · keyword388 ms100%
  • payments.shopkart.inAPI · GET1.42 s99.91%
  • SSL · shopkart.inCertificate61 daysvalid
  • nightly-invoice-exportCron heartbeatlate 14 m98.7%
  • db-primary:5432TCP port3 ms100%

BEAT 02within 60 s

Status Pages

Customers hear it from you first.

Public or private status pages on your own domain, with your logo, components customers recognise, scheduled maintenance and email or SMS subscribers. Update it from the incident in one click.

  • Custom domain with HTTPS
  • Private pages behind SSO or password
  • One branded page per client for agencies
Explore Status Pages
status.shopkart.inPublic
Checkout is having issues. We're on it.Investigating · updated 20:42 IST
  • WebsiteOperational
  • CheckoutDegraded performance
  • PaymentsOperational
  • Mobile app APIOperational
2,418 subscribers notified by email and SMS

BEAT 03paged in 3 s

On-Call Rota

One phone rings. The right one.

Fair schedules, clean handovers and escalation rules that keep moving until someone answers. Paging by voice call, SMS, push, Slack and Microsoft Teams, acknowledged from wherever the engineer is.

  • Overrides and swaps in two clicks
  • Escalation chains with timeouts
  • Quiet hours for low-severity alerts
Explore On-Call Rota
Checkout team · weekly rotationIST
MonTueWedThuFriSatSun
Primary
ArjunMeera
Secondary
KabirArjunSana
  1. 0 mCall + push to Arjun (primary)ACK 25 s
  2. 5 mSMS + call to Kabir (secondary)skipped
  3. 15 mPage engineering managerskipped

BEAT 04cause in 25 s

Incident Room + AI Root Cause

One room, one timeline, a likely cause with evidence.

Each incident gets roles, a channel, customer updates and a timeline that writes itself. AI Root Cause lines the failure up against recent deploys, error spikes and metrics, then shows its working for an engineer to confirm.

  • Timeline recorded automatically
  • Ranked causes with linked evidence
  • Postmortem draft when the incident closes
Explore Incident Room
AI Root Cause · INC-2194analysed in 25 s
Most likely cause · confidence highConnection pool change in deploy v4.18.2
  • Deploy v4.18.2 by ci-bot at 20:39:04, 2 min 8 s before first failure
  • DB connections 48 → 200 / 200 (100%) from 20:40:51
  • New error PoolTimeoutError · 3,912 events in 60 s
  • Failing in all regions, so not a network or CDN issue
Other hypothesesPayment gateway latency lowCDN edge errors ruled out
Confirm causeMark as wrong

BEAT 05monthly

Performance Watch + Uptime Reports

Catch slow before it becomes down. Prove uptime after.

Response times by region and request phase, Core Web Vitals and a ranking of your slowest endpoints. At the end of the month, SLA reports with error budgets and white-label PDFs for every client.

  • p50, p95 and p99 per region
  • Amber alerts on sustained slowdowns
  • Scheduled SLA reports with your branding
Explore Performance Watch
p95 response time · checkoutDEGRADED
MumbaiSingaporeFrankfurtBudget 800 ms
LCP1.9 sINP142 msCLS0.14TTFB186 ms

Alerts you can trust

No 3 am calls for a single dropped packet.

Every check runs from several regions at once. One region timing out is logged and retried. Only when two or more regions agree is the monitor marked down and the on-call engineer paged.

2+
regions must agree before a page
10
check regions, 3 of them in India
30 s
between checks on paid plans

20:12:30 · shopkart.in

  • MUM
  • DEL
  • BLR
  • SIN
  • FRA
  • LON

1 of 6 failed Retried, still up. Nobody paged.

20:41:12 · api.shopkart.in/checkout

  • MUM
  • DEL
  • BLR
  • SIN
  • FRA
  • LON

4 of 6 failed Confirmed down. Arjun paged in 3 s.

Connects to your stack

Plugs into the tools already open on your screen.

Paging and chat

  • Slack
  • Microsoft Teams
  • Voice call
  • SMS
  • Push
  • Email

Deploys

  • GitHub
  • GitLab
  • Bitbucket
  • CI webhooks

Errors and metrics

  • Sentry
  • Prometheus
  • Datadog
  • AWS CloudWatch
  • Grafana

Tickets and automation

  • Jira
  • GitHub Issues
  • Webhooks
  • REST API

Responsible AI and data

The AI points. Your engineers decide.

AI Root Cause is a fast second opinion, not an autopilot. It reads, it ranks, it shows its evidence, and then it waits for a person.

How AI Root Cause works

  • Suggests, never decides

    AI Root Cause ranks likely causes with evidence. Engineers confirm and choose what to do.

  • Read-only by design

    Xuptify never changes your systems. It only reads the data you connect.

  • Encrypted keys

    Integrations use read-only access where possible, and API keys are encrypted at rest.

  • You publish, we don’t

    Status pages show only what your team chooses to publish.

  • Your data stays yours

    Customer data is encrypted in transit and at rest, and never sold.

Our Plans

Three heart rates. Pick the one your systems run at.

Priced per monitor per month. SMS and voice alerts included up to a monthly limit.

60 bpm

Free

$0free, no time limit

10 monitors, 1-minute checks and one status page. For side projects and the first site you want to watch.

Compare plans 90 bpm

Team

$1.20per monitor / month, from 25 monitors

Up to 100 monitors, 30-second checks, On-Call Rota, Incident Room and AI Root Cause for product teams.

Compare plans 120 bpm

Scale

$0.90per monitor / month, from 100 monitors

Unlimited monitors, Performance Watch, client reports, single sign-on and the API for platforms and agencies.

Compare plans

FAQ

Before you add your first monitor

How often do you check?

Every 30 seconds on Team and Scale plans, and every minute on the free plan. Cron heartbeats can use any interval from one minute to one day.

Do you check from India?

Yes. Mumbai, Delhi and Bengaluru, plus Singapore, Tokyo, Sydney, Frankfurt, London, North Virginia and Oregon.

Does AI fix things automatically?

No. AI Root Cause suggests the likely cause and shows the evidence. Rolling back, restarting or changing anything is always your team’s decision, and Xuptify only has read access to the tools you connect.

Can agencies give each client a status page?

Yes. Each client can have their own branded status page on their own domain, their own subscribers and a white-label monthly uptime report.

Which tools do you connect to?

Slack, Microsoft Teams, GitHub, GitLab, Bitbucket, Sentry, Prometheus, Datadog, AWS CloudWatch, Grafana and Jira, plus webhooks and a REST API for anything else.

How long does setup take?

Minutes. Add a URL and the first check runs straight away. Connecting Slack and an on-call schedule usually takes another ten minutes.

60 bpm 10 monitors · 1-minute checks · free, no time limit

Put your first site on the monitor.

→ yourstore.com/checkout will be checked every 60 s from Mumbai, Singapore and Frankfurt

No card needed. Your first check runs within a minute of sign up.