Notifications
Clear all
Topic starter
23/06/2026 7:03 pm
TL;DR: Tiggee’s acquisition of PerfOps combines DNS, CDN, cloud performance, and benchmarking capabilities, while retaining the PerfOps team and expanding troubleshooting features such as DNS checks over TCP or UDP, including DNSSEC, according to DigiCert. For practitioners, the lesson is that network observability and root-cause tooling are becoming part of the same operational and governance problem.
NHIMG editorial — what this means for NHI practitioners
By the numbers:
- After taking over as CEO in 2020, Filip Bujas and his team managed to grow monthly revenues by 500% in just over 12 months.
Questions worth separating out
A: Security teams should validate DNS resolution, transport behaviour, and endpoint reachability before concluding that IAM, token, or service-account controls failed.
Q: When should teams treat observability data as part of governance rather than operations?
A: Teams should treat observability data as governance evidence whenever service access, workload trust, or incident attribution depends on proving where a failure occurred.
Q: What do organisations get wrong about multi-cloud performance monitoring?
A: Organisations often compare environments using inconsistent measurements, which makes the data hard to trust.
Practitioner guidance
- Map access failures to telemetry layers Separate DNS resolution issues, transport issues, and upstream service failures before you label an incident as identity-related.
- Standardize benchmark baselines across environments Use the same latency, routing, and resolution metrics across multi-cloud and multi-CDN paths so teams can compare behaviour consistently.
- Treat DNSSEC validation as a trust signal Include DNSSEC-aware checks in service monitoring where integrity matters, especially for externally resolved dependencies.
What's in the full announcement
DigiCert's full article covers the operational detail this post intentionally leaves for the source:
- The acquisition context around Tiggee, PerfOps, and the retained team structure that shaped the deal.
- The specific product changes already planned for PerfOps, including expanded DNS checking options and new troubleshooting tools.
- The named customer and market references used to illustrate PerfOps' benchmarking footprint across DNS, CDN, and cloud performance.
- The company statements on long-term development direction and the role of transparency in the platform's future.
👉 Read DigiCert's coverage of the Tiggee and PerfOps acquisition →
DNS telemetry consolidation: what it means for network teams?
Explore further
25/06/2026 2:50 am
Telemetry consolidation is becoming a governance issue, not just a tooling issue. When DNS, CDN, and cloud performance data move under one operational umbrella, teams can connect availability signals to trust decisions faster. That matters for identity programmes because service access failures often look like authentication or authorization problems until telemetry proves otherwise. Practitioners should treat observability ownership as part of service trust governance.
A few things that frame the scale:
- 1.5 out of 10 organisations are highly confident in their ability to secure NHIs, compared to nearly 1 in 4 for securing human identities, according to The State of Non-Human Identity Security.
- Only 85% of organisations lack full visibility into third-party vendors connected via OAuth apps, with 38% having no or low visibility and 47% only partial visibility.
A question worth separating out:
Q: Who should own root-cause evidence when DNS and access issues overlap?
A: Ownership should sit jointly with platform operations and identity governance because the same incident can involve routing, resolution, workload access, and service trust. Clear ownership prevents teams from stopping at the first visible symptom and helps them preserve evidence for both recovery and post-incident review.
👉 Read our full editorial: Tiggee and PerfOps show why DNS telemetry consolidation matters
