Cloud Performance Monitoring
Measure the cloud resources your site depends on — from the outside.
Your website is only as fast as the cloud resources behind it: the APIs it calls, the serverless functions that answer them, the CDN in front, the storage serving its files. NetTests checks each of them the way a customer reaches them — over the public internet — and tells you which one is slow, and which part of the request is slow.
Inside-out dashboards miss what customers feel
Cloud consoles report what a resource sees from the inside: CPU, invocations, error counts. They cannot see the DNS lookup that takes 300 ms, the TLS handshake at an overloaded load balancer, the CDN that stopped caching, or the third-party API that answers 200 with an error in the body. Those are exactly the problems a customer feels — and they sit between your resources and your users, outside every console.
Outside-in measurement closes that gap. It asks the same question a visitor's browser asks — how long until this endpoint answers, and is the answer right? — and records the parts of that time separately, so a slowdown points at its owner.
What NetTests measures
APIs and serverless endpoints. Scheduled HTTP checks with any method, headers, body and authentication. Every response's time is split into DNS lookup, TCP connect, TLS handshake and server wait; JSON field checks assert the response itself. API Monitoring →
CDNs and edges. Every check records which CDN answered, from which edge, and whether it was a cache hit, so the hit rate is graphed and alertable. The CDN Check compares the CDN with your origin. CDN Monitoring →
DNS and certificates. Record changes, propagation across public resolvers, DNSSEC, and certificate expiry and configuration for every endpoint. DNS Monitoring → SSL / TLS Monitoring →
Network path. Ping, MTR and traceroute to the hosts behind your resources, and TCP port checks for non-HTTP services.
Checks run on a schedule from our monitoring location and feed the same incidents, alerts, status pages and reports as website monitoring — one place for the site and the cloud resources behind it.
Key features
DNS · TCP · TLS · server time
Every request's latency split into the phases with different owners — graphed and alertable one by one.
JSON response checks
Assert JSON paths exist, equal a value, match a pattern or stay within a number.
CDN edge and cache
Provider, edge location and cache result on every check; cache-hit rate over time.
CDN vs origin
What your CDN actually saves, in milliseconds to first byte.
Incidents and alerting
Email, Slack, Teams, PagerDuty, Opsgenie and signed webhooks; incidents with history.
Site monitoring included
The same reports cover pages, synthetic journeys and real-user data — website and cloud side by side.
Free tools
Measure a cloud endpoint by hand — then put it on a schedule.
Any request, with DNS, TCP, TLS and server time and the CDN edge and cache result.
Which CDN served a URL, whether it was cached, and what it saves over the origin.
Your records as about 30 public resolvers around the world see them.
Per-hop latency and loss on the path to a host.
Frequently asked questions
How is this different from my cloud provider's monitoring?
Cloud monitoring (CloudWatch, Azure Monitor, Google Cloud Monitoring) measures resources from the inside: CPU, memory, invocations, internal errors. NetTests measures from the outside, over the public internet, the way your customers reach those resources — DNS, network, TLS, the CDN and the response itself. The two answer different questions; outside-in is the one that matches what a customer experiences.
Does NetTests connect to my AWS, Azure or Google Cloud account?
No. There are no credentials to grant and no agent to install: NetTests reaches your endpoints exactly as the public does. That also means it measures only what is publicly reachable.
Where do the checks run from?
From our monitoring location. Results describe the network path and the CDN edge that location reaches. For every visitor's location, add Real User Monitoring.
Can I monitor serverless functions?
Yes — any function reachable over HTTP or HTTPS (AWS Lambda function URLs or API Gateway, Azure Functions, Google Cloud Functions, Vercel or Netlify functions). Server wait shows the function's own time, including a cold start, separately from DNS, connect and TLS.
See your cloud the way your customers do
NetTests checks your APIs, CDNs and endpoints on a schedule, splits every delay into DNS, TCP, TLS and server time, and opens an incident the moment something breaks.
Start monitoring free →