Availability, incidents and service levels

How YesWeCheck monitors its email address validation API, console and batch processing, how to follow incidents, and which best-efforts commitments YesWeCheck makes. This English version is provided for convenience. The French version prevails in the event of any discrepancy. Read the French version.

YesWeCheck uses its best efforts to keep its services available and to inform its customers in the event of an incident. The commitments described on this page are best-efforts commitments: they concern what YesWeCheck does, not a guaranteed result. Unless a specific written agreement provides otherwise, this page does not constitute a contractual availability guarantee.

1. Observed availability

Availability measured over the last 90 days, recorded on 12 November 2026, by automatic probes every 5 minutes (public history at https://status.yeswecheck.fr/uk):

These figures describe the past availability of the services. They do not promise future availability and do not, on their own, constitute a contractual commitment.

2. Availability target

YesWeCheck sets itself the target of maintaining 99% availability over a rolling 90-day period, excluding scheduled maintenance, using its best efforts.

This target is not a contractual availability guarantee. It gives no right to any service credit or automatic compensation if it is not met, and does not constitute an obligation of result. Measurement is performed by automatic probes every 5 minutes.

The following do not count as unavailability: announced scheduled maintenance, force majeure, outages attributable to third parties (DNS providers, networks, mail providers), and interruptions caused by attacks or malicious acts targeting the Service.

3. Monitored services

YesWeCheck monitors in particular its email address validation API, its application (web console) and its batch processing. An automatic check runs every 5 minutes. The public page https://status.yeswecheck.fr/uk shows their status, ongoing incidents and a history covering the last 90 days.

The status page is a technical information tool. It may be affected by delays in detection, consolidation or display; its metrics do not, on their own, constitute a contractual guarantee.

4. Status definitions

5. What constitutes a degradation of the Service

Unavailability of the engine or the console may be a YesWeCheck incident. However, a receiving SMTP server that does not respond is not necessarily unavailability of YesWeCheck; it may lead to an unknown result according to the documented technical rules. Likewise, disruptions of an external integration are assessed according to the service actually affected and the responsibilities of each party.

6. Our commitments

In the event of an incident, YesWeCheck undertakes to:

These commitments concern detection, information and communication. They do not promise any maximum resolution time.

7. Monitoring and backups

The availability of the API, the console and batch processing is checked automatically every 5 minutes, with an immediate alert when an interruption is detected. Service data is backed up daily.

8. Maintenance

Maintenance, security fixes and technical changes may cause occasional interruptions. As far as reasonably possible, operations likely to significantly affect access are announced in advance, without compromising security. Announced scheduled maintenance does not count as unavailability when calculating the target in section 2.

9. No quantified availability guarantee in the standard offer

In the absence of a specific written agreement, YesWeCheck promises no contractual availability rate, no maximum resolution time and no automatic service credit in the event of an incident. This clarification does not allow YesWeCheck to evade its essential commitments or its obligation to deliver a conforming service.

No YesWeCheck plan currently includes a service level agreement (SLA). Specific commitments may be agreed in writing with certain Customers, setting out their measurement scope, observation period, legitimate exclusions, complaint procedure and any compensation.

10. Inherent limits of verification

Results also depend on third parties (mail providers, DNS, anti-abuse rules, networks). The Service cannot guarantee the lasting existence of a mailbox, its future ability to receive a message or the deliverability of a campaign. Statuses and scores are decision-support elements at the time of verification.

11. Complaints

In the event of a persistent anomaly, the Customer may contact [email protected], specifying the period, the service concerned, the effect observed and any useful technical references, without sending API keys in plain text. Legal and contractual remedies remain applicable. See also the Terms of use.