Initialising observation
Requesting the current observation, the aggregated windows and the incident history from the measurement API. No figure is drawn until it has been read - this page never shows a placeholder value.
Public infrastructure observatoryRecord stripe
External dependency intelligence. RELIASTRA observes Stripe's public payments endpoint from 2 regions and publishes the measurements without reference to any status page the vendor operates.
No completed observation has been recorded for this dependency yet, so no state can be reported.
No observation has been recorded yet, so there is no elapsed time to count and no interval to measure against.
No observation has been recorded for this dependency.Stripe is a payments dependency under continuous observation by RELIASTRA. Requests are issued to its public endpoints from eu-west, us-east, and every response is stored with its latency, status code and timestamp. The last observation recorded was no observation.
Over the last 24 hours RELIASTRA recorded 0 observations, an availability of insufficient data and a mean response of no data ms; over 30 days, insufficient data. No incident has been opened against this dependency. Availability, latency and incident history below are measured, not reported by the vendor.
A region reporting no response is not automatically an outage: RELIASTRA opens an incident only when at least two regions fail inside the same 60-second window.
Every window is computed by the measurement API over stored observations at read time. Latency figures are milliseconds; a mean of zero means no successful response was recorded in the window and is printed as no data.
Initialising observation series…
Requesting aggregated observations from the measurement API. No values are shown until they arrive.
Viewing 24 hours from eu-west. Other ranges: 7 days, 30 days, 90 days.
Cadence is measured from the density of observations in the last hour, not read from a configured schedule: the public API does not expose the check interval, so this record reports the interval it can verify.
No incidents observed
No published evidence for this dependency
Evidence records appear here when an organization monitoring stripe on RELIASTRA publishes the report for an incident. Until then the incident history above is the public record, and the underlying observations remain in the accounts that collected them.
An independent measurement of what Stripe's public endpoints returned to a request from a specific region at a specific second. It can disagree with the vendor's own status page, and a regional failure the vendor does not classify as an outage still appears here as observed failures.
A statement published by Stripe about its own services. RELIASTRA does not ingest, mirror or reconcile it, so no comparison between the two is shown on this page. If the vendor publishes a status page, read it alongside this record rather than instead of it.
https://status.stripe.comHTTPS · host status.stripe.com · path /Your own record
RELIASTRA observes the specific external services your product calls - including the ones no public index tracks - attributes your incidents to the dependency that caused them, and produces the evidence record you need when a vendor disputes it.
Or read how dependency monitoring works before you create anything.
No historical observations in this window
RELIASTRA has not recorded a completed observation for this dependency over the last 24 hours from eu-west. Nothing is drawn here rather than a flat line, because a flat line would assert an availability that was never measured. Once observations begin, each bucket appears here at the resolution the API aggregates to, and any failure or incident window is marked on the same axis.