Legal

Service Level Agreement

Our uptime commitment, credit policy, and what happens when we fall short — written clearly, without hiding behind footnotes.

Effective: January 1, 2025
Last updated: January 1, 2025
Questions? hello@podpapa.com

Overview

The short version: Monitor by PodPapa guarantees 99.9% monthly uptime. If we fall short, you automatically receive a service credit on your next invoice — no need to ask.

This Service Level Agreement ("SLA") describes our uptime commitment and credit policy for Monitor by PodPapa. It applies to all paid subscription plans and is part of the Terms of Service.

This SLA covers the availability of the Monitor platform itself — the dashboard, monitoring engine, and alert delivery system. It does not cover the uptime of the external websites or servers you configure Monitor to watch.

Uptime Guarantee
99.9%
per calendar month
Max Allowed Downtime
43.8m
per month (~8.7 hours/year)

Uptime Commitment

PodPapa commits to 99.9% monthly uptime for the Monitor platform, calculated as:

Uptime % = ((Total Minutes − Downtime Minutes) / Total Minutes) × 100

This commitment covers:

  • The Monitor dashboard and web interface being accessible to users
  • The monitoring engine actively performing checks at your configured intervals
  • Alert notifications being dispatched when monitors change state
  • The REST API being available for programmatic access
  • Public status pages being accessible to your end users

Uptime is measured on a per-calendar-month basis. Each month is evaluated independently.

What Counts as Downtime

"Downtime" is any continuous period of 5 minutes or more during which the Monitor platform is completely unavailable — users cannot access the dashboard and the monitoring engine has stopped running checks.

The following do NOT count as downtime:

  • Scheduled maintenance announced at least 24 hours in advance
  • Partial degradation where core monitoring continues but secondary features are slow
  • Slowness or increased latency that does not cause complete unavailability
  • Outages caused by your own actions, misconfigurations, or Terms violations
  • Third-party service outages outside our direct control (CDN, DNS, cloud region)
  • Incidents shorter than 5 continuous minutes

Monitoring Check Intervals

Checks run at your configured interval per plan. We commit to the following delivery accuracy:

Plan
Min Interval
Accuracy
Starter
60s
±10 seconds
Pro
20s
±5 seconds
Agency
20s
±5 seconds

Under heavy load, checks may be slightly delayed but will never be skipped — they execute as soon as the system recovers.

Service Credits

If monthly uptime falls below 99.9%, you receive a credit on your next invoice — calculated based on severity:

Monthly Uptime
Downtime
Credit
99.0% – 99.9%
43m – 7.3h
10% of monthly fee
95.0% – 99.0%
7.3h – 36h
20% of monthly fee
Below 95.0%
More than 36h
30% of monthly fee
  • Credits are applied automatically to your next invoice — no action needed
  • Credits are non-transferable and cannot be exchanged for cash
  • For annual plans, monthly equivalent is used (annual fee ÷ 12)
  • Maximum credit per month is capped at 30% of your monthly fee

Exclusions

The following are excluded from SLA calculations and do not qualify for credits:

  • Scheduled maintenance — announced ≥24 hours in advance
  • Emergency maintenance — to prevent data loss or security compromise
  • Your own actions — misconfigurations, API abuse, or Terms violations
  • External dependencies — cloud provider outages, DNS failures, internet backbone issues
  • Force majeure — natural disasters, war, government actions
  • Free or trial accounts — this SLA covers paid plans only
  • Beta features — features explicitly marked as experimental

Incident Response

When a platform incident occurs, we commit to the following response timeline:

Stage
Target
Action
Detection
≤ 5 min
Automated alert triggered
Acknowledgment
≤ 15 min
Status page updated, team engaged
Updates
Every 30 min
Progress posted to status page
Post-mortem
Within 48h
Root cause & remediation published

Reporting an Incident

Credits are applied automatically. If you believe a qualifying incident wasn't captured, report it within 30 days:

  • Email hello@podpapa.com with subject: "SLA Credit Request"
  • Include your account email, incident start/end time, and a brief description
  • We'll respond within 5 business days with our determination
In most cases credits are applied automatically. Manual reporting is only needed if you believe an incident wasn't reflected in our internal monitoring.

SLA Changes

Changes that reduce your SLA rights will be communicated via email at least 30 days before taking effect. Changes that improve your rights (higher uptime guarantee or higher credits) may take effect immediately.

Continued use of Monitor after the effective date constitutes acceptance of the updated SLA.

Contact

For credit requests, incident reports, or uptime questions — we respond within 2 business days.

SLA & Uptime Inquiries

For credit requests, incident reports, or uptime questions.

hello@podpapa.com