Pingvera crawler
Our robot’s User-Agent and how to exclude it from your analytics.
If you see requests from Pingvera on your site, the studio or agency maintaining it has put it under uptime monitoring. We periodically request a page from several regions to be the first to notice an outage. These requests can be excluded from your web analytics.
User-Agent
All our checks (availability, WordPress fingerprint, broken links, scan) identify themselves with a single User-Agent containing the Pingvera:
The browser-like prefix keeps protections (Cloudflare, anti-DDoS) from blocking the check. The stable marker for filtering is the Pingvera substring in the User-Agent.
How to exclude it from analytics
- Google Analytics 4: known-bot filtering is on by default; to be sure, add a filter/segment excluding User-Agents containing Pingvera (or filter server-side / via Measurement Protocol).
- Matomo / Plausible and others: add a tracker-side or server-side rule excluding User-Agents containing Pingvera.
- Server logs / WAF: exclude requests whose User-Agent contains Pingvera.
Where checks come from
Checks run from several probing regions (for example, Nuremberg and Amsterdam). IP addresses may change — filter by User-Agent rather than IP.
Load
We request a page infrequently — at the monitoring interval (typically every 1–3 minutes for availability; domain and certificate expiry once per hours/day). This creates no noticeable load and does not index your site.
Contact
Crawler questions: info@pingvera.com.