How we handle incidents
Routing already absorbs most upstream trouble: a degraded route is scored down and requests retry elsewhere before they reach you. We open an incident here when the platform itself is affected — the gateway, the job queue, webhook delivery, or the console — not every time a single upstream provider has a bad hour.
During an incident we post an initial note quickly, update at least hourly, and publish a written post-mortem for anything that caused sustained request failures.
Subscribe
Email hello@infro.io to be added to incident notifications, or configure a webhook in the console to receive them programmatically alongside your job events.
This page reflects the launch configuration. Once the platform is serving production traffic it will be driven by live probes on an independent host.