Bulk HTTP Latency & TTFB Monitor
Pricing
from $1.00 / 1,000 url checks
Bulk HTTP Latency & TTFB Monitor
Measure website response times, Time-to-First-Byte, and status codes across thousands of URLs for uptime monitoring and performance audits.
Pricing
from $1.00 / 1,000 url checks
Rating
0.0
(0)
Developer

Andok
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
HTTP Latency Monitor
Verify SLA compliance with bulk TTFB and response time checks across hundreds of endpoints in a single run. Slow response times directly impact user experience, search rankings, and uptime commitments — yet most monitoring tools only check one URL at a time. Measure latency at scale with structured, API-ready results.
Features
- Response time measurement — captures total HTTP request latency in milliseconds for each URL
- Bulk monitoring — check hundreds of endpoints concurrently in a single run
- HTTP status tracking — reports the status code returned by each endpoint
- Flexible HTTP method — use HEAD for lightweight checks or GET for full-response timing
- Redirect detection — captures the final URL after any redirects
- Structured output — JSON results ready for dashboards, alerts, or SLA reports
Input
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
urls | array | Yes | — | List of URLs to measure (e.g., https://example.com). Also accepts objects with a url field |
url | string | No | — | Single URL to check (use urls for bulk monitoring) |
method | string | No | HEAD | HTTP method to use. HEAD measures server response time; GET includes full body transfer |
timeoutSeconds | integer | No | 15 | Request timeout per URL in seconds (1-60) |
concurrency | integer | No | 10 | Number of URLs to check in parallel (1-50) |
Input Example
{"urls": ["https://example.com","https://api.example.com/health","https://cdn.example.com/assets/main.js"],"method": "HEAD","concurrency": 20}
Output
Each URL produces one dataset record with the measured latency, HTTP status, and any errors encountered.
Key output fields:
inputUrl(string) — the URL as submittedfinalUrl(string) — the URL after any redirectsstatus(number) — HTTP status codelatencyMs(number) — total response time in millisecondsmethod(string) — HTTP method used for the checkerror(string | null) — error message if the request failedcheckedAt(string) — ISO 8601 timestamp
Output Example
{"inputUrl": "https://example.com","finalUrl": "https://example.com/","status": 200,"latencyMs": 142,"method": "HEAD","error": null,"checkedAt": "2026-03-09T12:00:00.000Z"}
Pricing
| Event | Cost |
|---|---|
| URL Check | $0.001 |
Pay only for URLs successfully checked. Respects your per-run spending limit.
Use Cases
- SLA verification — measure response times across all client endpoints to confirm uptime and latency commitments
- CDN performance audits — compare response times across CDN edge locations and origin servers
- Deployment validation — check response times before and after deployments to catch performance regressions
- Competitive benchmarking — measure competitor site speeds alongside your own for executive reporting
- Scheduled health checks — run periodic latency sweeps and feed results into alerting pipelines
Related Actors
| Actor | What it adds |
|---|---|
| DNS Propagation Checker | Verify DNS resolution alongside response time to isolate network vs. server latency |
| Broken Links Checker | Crawl sites for broken links — pair with latency data to prioritize slow and broken pages |
| SSL Certificate Monitor | Monitor certificate expiry to prevent downtime that latency checks alone won't catch |