Product · Synthetic checks

14 global edges, fail-quorum, and assertions worth their weight.

A DevFlow synthetic check describes one request, one set of assertions, and one frequency. It runs from your choice of edges. The default fail-quorum mode means a check is only counted as failed when more than half of the configured edges agree — which kills most of the noise that single-region checks generate.

Edge fleet

We run 14 edges of our own across three independent cloud providers. The probe binary is the same in every region; we deploy weekly. We do not lease our probe network — see Priya’s post on why we built our own rather than reseating someone else’s edge.

HTTP and gRPC

HTTP monitors handle the common case. gRPC monitors load your protos once, dial each region, send the request, and assert on the response field. mTLS supported on both. Code samples are in the docs.

yaml

name: payments-grpc-charge
type: grpc
target: payments-api.example.com:443
service: payments.v1.PaymentsService
method: CreateCharge
proto: payments
request: { amount_cents: 100, currency: usd }
deadline_ms: 4000
tls: { enabled: true, verify: true }
assertions:
  - response_field_eq: { path: status, eq: SUCCEEDED }
  - latency_lt_ms: 600

For the full request shape and assertion vocabulary, head to the HTTP monitor basics and gRPC monitor basics docs.