provider_unavailable
The verification provider itself could not answer
The partner infrastructure that runs the mailbox handshake was unreachable, returned an error, or was held off by Spaw's circuit breaker. The lookup was answered from the free signals.
- appears in
- smtp_reason
- credits
- Billed by the verdict it produced: a deliverable answer with smtp_checked false is 1 credit. The settling re-checks are free.
What it means
After repeated provider failures Spaw stops sending probes for a few minutes and answers every mailbox check as unverified, so a provider incident never turns into a queue of slow requests. Such answers are never cached: the next lookup probes again as soon as the provider recovers.
smtp_checked is false and mailbox_exists is null; the verdict comes from syntax, DNS, the open lists and the domain signals.
What to do
Retry later, or pass callback_url so the settled verdict is pushed to you. If you see it across many lookups, quote a request_id to [email protected].
Example response
{
"deliverable": "deliverable",
"smtp_checked": false,
"smtp_reason": "provider_unavailable",
"mailbox_exists": null
}Abbreviated: a real answer carries all 27 fields, listed in the verify-email reference.
Related
- mailbox_full · the mailbox is over its storage quota
- no_mailbox · the server answered that the mailbox does not exist
- disabled · the server reported the mailbox as disabled or suspended
- greylisted · the server deferred the handshake and asked the sender to come back later
- timeout · the mail server did not answer within the probe's time limit
- no_connect · no mail server accepted a connection on port 25
- mx_unreachable · the mail exchangers could not be reached from the verification network
- delivered_recently · your own delivery report confirmed this mailbox
- All verdict reasons
- Verdicts and the risk score
- API reference
markdown version: /docs/reasons/provider_unavailable.md