Appearance
Service status and help
Check Agio service status for current production availability and incident updates. For help, email [email protected] or see other ways to contact Agio.
The status page runs outside Agio's Google Cloud infrastructure. Its scheduled checks cover selected public routes; a green check does not validate every application operation. If your operation fails while status is green, please still report it.
Integrating with Agio
As a developer integrating with Agio, use status to check whether a production incident affects your integration, then contact us with enough detail to investigate.
Include:
- The API or integration and whether you use production or sandbox.
- The failing operation, HTTP status code, and sanitized error message.
- The time and time zone, plus a request or correlation ID if available.
- Safe steps to reproduce and the impact on your users.
The public status page covers production. Sandbox and development availability may differ; include your environment explicitly when asking for help.
For a new integration, start with the Cards partner quickstart or Platform API. Email us if you need help choosing an integration.
Using an Agio app
As someone visiting an Agio app, check status for a known incident. If you still need help, email us with the app name, what you were trying to do, the time and time zone, and your browser or app version. Include a sanitized screenshot or request ID if useful.
You can use the email contact above even when the app or website cannot load.
Agio developers responding to an incident
As an Agio developer, use the public status page to understand what customers can see. Follow the internal incident process and use internal logs, dependency checks, queue diagnostics, and on-call contacts to investigate.
Communicate affected customer operations and recovery progress through the incident updates. Keep internal logs, infrastructure details, credentials, and customer data in the approved internal tools.
What to leave out
Never send passwords, API keys, access tokens, card details, recovery phrases, or unredacted customer data. Redact sensitive information from screenshots and error reports before sharing.