Author
Kristoffer Pihlfelt
Developer and founder, Pihlfelt & Vänner
Kristoffer Pihlfelt is a developer and the founder of Pihlfelt & Vänner, a Swedish web agency he has run since 2014. He builds Ravnsight and the Ravnsight Detective WordPress plugin, and has spent years building, troubleshooting and maintaining WordPress and WooCommerce sites for clients.
At Ravnsight
He is responsible for the Ravnsight monitoring platform and the Ravnsight Detective plugin — from the check engine that confirms an outage from Germany, Finland and Sweden before anyone is alerted, to the in-site diagnostics that correlate an error with the change that preceded it.
Elsewhere
Latest articles
- TCP Port Monitoring: Catching the Silent Service Failures HTTP Checks Miss An HTTP check only sees the homepage. TCP monitoring of mail, database and API ports reveals silent service failures before customers do.
- How to Communicate Incidents to Clients Without Scaring Them — or Lying to Them How agencies can build incident communication that reassures clients instead of scaring them — the right information, in the right order, without jargon.
- Autumn Storms and Hosting Power Outages: Why Downtime Isn't Always Your Fault Autumn storms knock out power at hosting providers every year. Learn why multi-country monitoring is essential to tell real outages apart from local network glitches.
- Security headers explained: what they are and why they matter HSTS, CSP, X-Frame-Options and the rest — the HTTP headers that harden your site against common attacks, what each one does, and how to add them.
- Turn website care into recurring revenue (white-label monitoring) A packaged “Website Care” plan turns irregular hours into predictable monthly revenue. Here's how to build one – and make the margin work.
- Alert fatigue: why your monitoring cries wolf, and how to fix it When every blip becomes a critical alert, the team stops reading – and misses the real outage. Here are the causes of alert fatigue and how to design them out.
- WooCommerce checkout not working but the site is up The homepage returns 200 OK but customers can't pay. Troubleshoot the WooCommerce checkout step by step: purchase flow, gateway, logs, templates and the JS console.
- Uptime monitoring vs synthetic monitoring: what's the difference A 200 OK doesn't mean the site works. Understand the difference between uptime and synthetic monitoring, and when you need which.
- How to find which WordPress plugin is behind a fatal error A fatal error with no obvious cause? Read the stack trace, use the deactivate-half bisect method, and Health Check’s troubleshooting mode to isolate the culprit – without disturbing visitors.
- WordPress cron stopped running: how to notice before anything is missed Scheduled posts don’t publish, backups never run and Action Scheduler jobs stall? Here is how to check DISABLE_WP_CRON, set up real system cron, and fix overdue jobs.
- Intermittent 502 / 503 errors: how to catch what you can't reproduce Errors that vanish the moment you look. Causes of intermittent 502/503, why they're hard to catch by hand, and how logs and continuous checks reveal the pattern.
- Website monitoring without false alarms: how confirmation works Most monitoring tools alert on the first failed request. That is why people turn them off. Here is the method that avoids it.