Library · Payment orchestration · How to run this
Outage attempts are still attempt share
A gateway outage still leaves attempts on the book. Outage share = outage attempts ÷ total attempts × 100. Type both counts.
Pair: Gateway outage share on Orchestration. Token hop: network token fallback. Failover: failover auth count.
What you type
Outage attempts — attempts the vault / gateway tags in the outage window (or your outage clock).
Total attempts — all attempts on that gateway path in the same reporting window.
Outage share = outage ÷ total × 100. Route around or pause the gateway when share is material — do not invent an outage chip.
What not to do
Do not invent outage %. Do not mix soft declines into outage attempts. Do not treat failover hops as outage without a tag. Do not average every gateway when one owns the outage pile.
Related: Orchestration, network token fallback, failover auth count, cascade pollution.
Procedure
- Type outage attempts and total attempts.
- Read outage share %.
- Route around or pause the gateway when share is material.
Failure modes
- Inventing outage %.
- Mixing soft declines into outage attempts.
- Treating failover hops as outage without a tag.
Worked example
None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.
Glossary
- Gateway outage share
- Attempts tagged in a gateway outage window ÷ total attempts on that path × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this network token fallback?
- Sibling hop. [Network token fallback](/manuals/spreedly-network-token-fallback) is token fail → PAN. This page is attempts stamped during a gateway outage ÷ total attempts.
- Is this failover auth count?
- Related hops. [Failover auth count](/manuals/failover-auth-count) is auths per order on failover. This page is outage-window attempt share on one gateway.
- What outage % should I invent?
- None. Type outage-tagged attempts and total attempts from the vault / gateway for the same window.