Home / Sitemap

Sitemap

Every page on PingCrumb, in one place.

Home
PingCrumb overview, features, pricing, and FAQ
/
Author
About Julien Jimenez, the founder behind PingCrumb
/author/
Blog
Guides on uptime monitoring
/blog/
How to Choose an Uptime Check Interval That Actually Catches Outages
A shorter interval is not always better. Here is how to pick a check frequency that catches real downtime without drowning you in noise or cost.
/blog/uptime-check-interval/
Status Page Best Practices That Reduce Support Tickets
A good status page answers the question your customers are about to ask. Here is how to build one that cuts your support load during an incident.
/blog/status-page-best-practices/
Uptime vs Response Time: What to Monitor and Why Both Matter
A site can be up and still be failing your users. Here is the difference between availability and performance, and why you need to watch both.
/blog/uptime-vs-response-time/
How to Set Up Alerting That Avoids False Alarms
Alert fatigue is how real outages get ignored. Here is how to build alerting people actually trust and act on.
/blog/alerting-without-false-alarms/
SSL Certificate Expiry: How to Never Get Caught Offline
An expired certificate can take a healthy site down in an instant. Here is how to make sure it never happens to you.
/blog/ssl-certificate-expiry/
What Five Nines Really Means for a Small SaaS
99.999 percent uptime sounds impressive, but the number hides some hard math. Here is what different reliability targets actually cost.
/blog/what-five-nines-means/
Synthetic Monitoring vs Real User Monitoring, Explained
These two approaches answer different questions. Here is when to use each, and why most teams need a bit of both.
/blog/synthetic-vs-real-user-monitoring/
How to Write a Clear Incident Update Your Customers Trust
During an outage, your words matter as much as your fix. Here is a simple structure for updates that calm people instead of alarming them.
/blog/clear-incident-update/
Monitoring APIs and Webhooks: A Practical Checklist
APIs fail in quieter ways than websites. Here is a checklist to make sure your monitoring catches the failures that matter.
/blog/monitoring-apis-webhooks-checklist/
How many monitoring locations do you actually need to confirm a real outage?
One probe in one region can page you for problems that only exist on that probe. Here is how to think about location count, confirmation logic, and the difference between a regional blip and a real outage.
/blog/monitoring-locations-needed/
Why does a website return 200 OK while customers see a broken page?
A green HTTP check and an unusable site are not contradictions. Here is what a status code actually proves, the failures it cannot see, and how to check for the page your customers experience.
/blog/status-200-but-broken/
How do you run an on-call rotation when your whole team is three people?
Big-company on-call playbooks assume you have a dozen engineers to spread the load. Here is a rotation, an alert policy, and a set of ground rules that actually hold up when there are only three of you.
/blog/on-call-tiny-team/
When should a small SaaS start monitoring DNS resolution separately from HTTP checks?
Most teams discover DNS is part of their uptime the day a registrar, a nameserver, or an expired domain takes them offline. Here is what DNS monitoring adds, and the point where it stops being optional.
/blog/monitor-dns-separately/
What is the best way to schedule a maintenance window without alarming your customers?
Planned downtime should never look like an outage. Here is how to pick the time, silence the right alerts, announce it on the status page, and confirm you are actually back.
/blog/scheduling-maintenance-windows/
Which monitoring approach catches a nightly cron job that silently stopped running?
A website check cannot see a backup that never ran or an invoice batch that quietly stopped. Heartbeat monitoring flips the model so that silence itself becomes the alarm.
/blog/cron-job-heartbeat-monitoring/
How much detail should a public postmortem include after a customer-facing outage?
Too little detail reads as evasive, too much reads as an excuse. Here is a structure for the public version of a postmortem that earns trust without exposing what should stay internal.
/blog/public-postmortem-detail/
What should a bootstrapped SaaS founder do when a prospect demands a 99.99% uptime SLA?
Four nines sounds like a number, but in a contract it is a promise with money behind it. Here is how to evaluate what a prospect is really asking for and how to negotiate an SLA you can keep.
/blog/prospect-demands-uptime-sla/
How should a small team monitor third-party vendors that can take its app offline?
Your uptime is only as good as your payment processor, email API, auth provider, and CDN. Here is how to map those dependencies, watch them without drowning in vendor noise, and fail gracefully when one goes down.
/blog/monitoring-third-party-vendors/
How do you monitor a customer login flow without storing a real password in your monitoring tool?
A homepage check stays green while nobody can sign in. Here is how we monitor the login path end to end using a synthetic account and a scoped secret, so no customer credential ever sits in a monitoring config.
/blog/monitoring-login-flows-safely/
What should a small team do when the alerting channel itself goes down during an outage?
Every alerting setup has a single path from monitor to human, and that path fails more often than people admit. Here is how we build a second route, prove it works, and make silence itself trigger an alarm.
/blog/backup-alert-channels/
Complete guide
Everything a small team needs to know to monitor availability, alert the right person, and communicate clearly when things break. Written by people who run production systems, not by a marketing department.
/guide/
Compare options
Five honest ways to find out your site is down before your customers do, from a cron job on a spare server to a full observability stack, with the trade-offs each one carries for a small team.
/compare/
Glossary and FAQ
Plain definitions of the words that show up in monitoring dashboards, alert messages, status pages, and service agreements, followed by answers to the questions we hear most often.
/glossary/
Free tools
Free calculators and planners
/tools/
Website Downtime Cost Calculator
Estimates what a single outage costs a SaaS or online business in lost revenue, response labor and credits, so you can put a real number on uptime.
/tools/website-downtime-cost-calculator/
Uptime SLA Error Budget Calculator
Converts an uptime target like 99.9 percent into allowed minutes of downtime, then checks whether your real incident pattern fits inside that budget.
/tools/uptime-sla-error-budget-calculator/
Uptime Check Interval Detection Time Calculator
Shows how long an outage can go unnoticed at a given check interval and confirmation setting, and how many monitoring requests that setup sends per month.
/tools/check-interval-detection-time/
Which uptime monitoring setup is right for you?
Seven quick questions about what you run, who gets woken up and what you have promised customers, followed by honest guidance on where to start.
/quiz/
Uptime Monitoring Setup Checklist
A step-by-step checklist for setting up checks, alerting, and a status page that a small software team can actually maintain.
/templates/uptime-monitoring-setup-checklist/
Monitor Inventory and Alert Routing Worksheet
One sheet that records every check you run, what counts as failure, how often it runs, where alerts go, and who owns the response.
/templates/monitor-inventory-worksheet/
Disclosure
How this site is funded
/disclosure/
Legal notice
Publisher and hosting information
/legal/
Privacy policy
How your data is collected and protected
/privacy/
Terms of service
The terms that govern use of the service
/terms/

Looking for the machine readable version? See sitemap.xml.