ProtoScrape SERVICE HEALTH
A clear view of
what’s running.
Current observations, service incidents and planned maintenance. No account needed.
Subscribe with RSS ↗Loading the latest publication…
Service components
Observed health ≠ engine enablementHealth is unknown until recent observations load.
Incidents & maintenance
JSON ↗Loading incident history…
Incident history is not available yet.
How to read this page
Measured, with limits
API reachability uses recent checks from at least two monitoring locations. Website reachability uses one monitor. Neither tests account access, payments or every API operation.
Engine health samples completed jobs over 30 minutes, allowing two minutes for telemetry. At least 10 observations and a completion within 15 minutes are needed. A failure share of 20% or more is degraded; all failures is an outage. Smaller samples are unknown. “Operational” does not guarantee every query succeeds.
Freshness comes first
The collector runs every two minutes. Observations expire after five minutes. Missing or stale data is unknown; we do not infer uptime from silence. An engine marked paused is disabled for new requests.
This page uses a separate static origin and collector. It shares Google Cloud and the public load balancer with our service. It is not an uptime guarantee or an SLA.
Public updates are published by authorized staff. Active incidents stay visible; resolved incidents are displayed for 90 days. Scheduled maintenance requires explicit resolution, even after its window ends. RSS updates can lag publication by two minutes. RSS does not send automatic emails or SMS.
Need help with a specific job?
Support: Monday–Friday, 09:00–18:00 France time (Europe/Paris). First-response target: one business day. Failed, cancelled and expired jobs use no credits.