Service Level Agreement
Effective date: March 8, 2026
Table of Contents
1. Overview
This Service Level Agreement ("SLA") describes CronAlert's uptime commitment for our monitoring infrastructure. It defines what we guarantee, what happens if we fall short, and how you can claim service credits.
This SLA is a part of and subject to our Terms of Service. In the event of a conflict between this SLA and the Terms of Service, the Terms of Service take precedence.
Important: This SLA covers the CronAlert monitoring infrastructure itself -- our ability to execute your scheduled checks and deliver alerts. It does not cover or guarantee the uptime of the services you are monitoring.
2. Infrastructure
CronAlert's monitoring infrastructure runs on Cloudflare Workers and Cloudflare Pages. Our database is Cloudflare D1. All scheduling is handled by Cloudflare Cron Triggers.
This means our availability is directly tied to Cloudflare's global edge network, which spans 300+ cities across 100+ countries. Cloudflare Workers carries a published 99.99% uptime SLA for Enterprise customers and has historically maintained availability well above that threshold across all tiers.
By building entirely on Cloudflare, we inherit the reliability of one of the world's largest edge networks without introducing additional points of failure from self-managed infrastructure.
3. Uptime Commitment
CronAlert commits to 99.99% monthly uptime for our monitoring infrastructure. This means no more than approximately 4.3 minutes of downtime per month.
"Uptime" is defined as the CronAlert monitoring infrastructure being available to execute scheduled URL checks and deliver alerts through configured channels. Uptime is measured on a calendar-month basis.
Monthly Uptime Percentage is calculated as:
(Total minutes in month - Downtime minutes) / Total minutes in month x 100
4. Eligible Plans
This SLA applies only to the following subscription plans:
- Team plan ($20/month or $16/month billed annually)
- Business plan ($50/month or $40/month billed annually)
Free and Pro plan users benefit from the same infrastructure and the same operational commitment to uptime, but are not eligible for service credits under this SLA.
5. Service Credits
If CronAlert fails to meet the 99.99% uptime commitment in a given calendar month, eligible customers may request a service credit applied to their next billing cycle.
| Monthly Uptime | Service Credit |
|---|---|
| Below 99.99% but at or above 99.9% | 10% of that month's subscription fee |
| Below 99.9% but at or above 99.0% | 25% of that month's subscription fee |
| Below 99.0% | 50% of that month's subscription fee |
Service credits are issued as a credit toward future CronAlert subscription charges. Credits are not refundable for cash and cannot be transferred to other accounts. The maximum credit for any single month is 50% of that month's subscription fee.
For customers on annual billing, the monthly subscription fee for credit calculation purposes is the annual fee divided by 12.
6. Exclusions
The following are not considered downtime for the purposes of this SLA:
- Scheduled maintenance -- planned maintenance windows that we announce at least 48 hours in advance via email or status page. We aim to perform maintenance during low-traffic hours and keep windows as short as possible.
- Force majeure -- events beyond our reasonable control, including natural disasters, war, terrorism, government actions, labor disputes, or pandemic-related disruptions.
- Customer-side issues -- problems with your network, DNS, browser, or local infrastructure that prevent you from reaching CronAlert.
- Third-party service outages -- outages affecting the URLs or services you are monitoring. CronAlert monitors your services; their downtime is not our downtime.
- Alert delivery failures -- failures in downstream notification services (email providers, Slack, Discord, PagerDuty, etc.) that are outside our control. We are responsible for dispatching the alert; delivery depends on the receiving service.
- Abuse or violations -- downtime resulting from actions that violate our Terms of Service, including excessive API usage or abusive behavior.
7. How to Claim Credits
To request a service credit:
- Email [email protected] within 30 days of the month in which the downtime occurred.
- Include your account email, the date(s) and approximate time(s) of the downtime you experienced, and a brief description of the impact.
- We will review your request and verify the downtime against our internal monitoring data.
- If the claim is valid, we will apply the credit to your next billing cycle within 15 business days of confirming the claim.
Failure to submit a claim within 30 days of the affected month forfeits the right to receive a credit for that period.
8. Definitions
- "Downtime" means a period of 5 or more consecutive minutes during which the CronAlert monitoring infrastructure is unable to execute scheduled URL checks, as confirmed by our internal monitoring systems. Isolated failed checks or brief transient errors do not constitute Downtime.
- "Monthly Uptime Percentage" means the total number of minutes in a calendar month minus the total Downtime minutes, divided by the total minutes in that month, expressed as a percentage.
- "Service Credit" means a credit applied to a future CronAlert invoice, calculated as a percentage of the subscription fee for the affected month.
9. Changes to This SLA
We may update this SLA from time to time. If we make changes that materially reduce our uptime commitment or credit structure, we will notify affected customers at least 30 days in advance via email.
The current version of this SLA is always available at cronalert.com/sla.
10. Contact
If you have questions about this SLA or need to submit a credit claim, contact us at [email protected].