payments
Is E2E Test Provider down right now?
Our independent multi-region reading is: unreachable.
Independently measured by StackWitness. We ping each service host ourselves (reachability) and also read its status page. The strong signal is when a host is unreachable while the vendor claims operational.
Current status
Vendor under-report signal
We measured UNREACHABLE; E2E Test Provider reports operational
Independent probes could not reach the service host from multiple regions while the vendor status page claims operational.
Incident timeline
-
- Start
- End
- Regions
- 3
Probe latency (this week)
Probe round-trip time and reachability outcomes only. Not full product health or a vendor SLA.
1 disruption · baseline probe p50 · scale fits this week’s range (not a fixed 0-100ms axis)
Line / fill = successful probe p50 · Bands = disruption windows · Floor ticks = fail share in bucket
- Reachability failures in 100% of probes (9/9) between 2026-07-23T06:00:00.000Z and 2026-07-23T12:00:00.000Z.
Recorded disagreements
Times when independent probes measured unreachable while the vendor status page reported operational. A measurement record, not a verdict.
reachable = the service host answered our probe; not a guarantee the product is fully healthy
A status-code response within 8 seconds counts as reachable.
-
Self-reported operational while we measured unreachable from 3 regions (9 samples)
- Start
- End
- still open
- Regions
- 3 (apac, weur, wnam)
- Samples
- 9
How to read this page
StackWitness shows two columns for E2E Test Provider: independent multi-region reachability (our probes of the service host) and the vendor's own status page (self-report). Divergence matters most when we cannot reach a host the vendor still calls operational. Reachable means the host answered our probe; it is not a promise every feature works, and we never issue a compliance verdict.
Questions
Is E2E Test Provider down?
StackWitness independently pings the E2E Test Provider service host for reachability from multiple regions and also reads the vendor status page. Reachable means the host answered our probe; it is not a claim that every product feature is healthy. We never issue a compliance verdict.
How does StackWitness know if E2E Test Provider is down?
We ping the E2E Test Provider service host for reachability from multiple regions and read the vendor status page. The signal worth acting on is when we cannot reach a host the vendor still calls operational.
What does "reachable" mean here?
The host answered our probe from our regions. It is not a claim every E2E Test Provider feature is healthy, and we never issue a compliance verdict.
Measurement window: → .
We independently ping this service host (reachability) and also read its vendor status page. The strong signal is when we cannot reach a host that still claims to be operational. We never invent calm green or issue a compliance verdict.