Vade Services Outage History
22 incidents recorded over the last 365 days, 9 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Vade Services Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 28, 2026 | Vade for GWS - Incident - October 14th & 26th[French] Chers utilisateurs Vade, Nous avons rencontré des dysfonctionnements les 14 et 26 octobre liées à la synchronisation des certificats de nos serveurs de messagerie (MTA). Ces incidents ont entraîné des… | 0 min | Resolved |
| Oct 26, 2026 | VadeM365 (EU/FR/DE/ASIA) PDF reports downThe PDF reports generation is not available at the moment. It should be back very soon Other services and email flow are not affected. Thank you for your understanding. | 15h 9m | Resolved |
| Oct 21, 2026 | Maintenance filter update & IIPThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Oct 1, 2026 | Scheduled Maintenance - Providers DashboardThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jun 11, 2026 | Incident on Vade for M365 (EU/US/DE/ASIA) - Random emails not being actionned correctlyThis incident has been resolved. | 164h 40m | Resolved |
| Jun 5, 2026 | Failed attempt to login to Vade CloudThis incident has been resolved. | 97h 30m | Resolved |
| Jun 1, 2026 | SafeUnsubscribe - Error 502 suproxy.vadesecure.comThe cause of the incident has been resolved. The SafeUnsubscribe Service is again fully operational and solved sustainably. | 3h 9m | Resolved |
| May 22, 2026 | Network issue - Investigating / Incident réseau - InvestigationThis incident has been resolved. | 119h 38m | Resolved |
| May 11, 2026 | Cloud access issue - Error 500[French] Chers utilisateurs Vade, Les difficultés techniques affectant le produit Cloud ont été résolues, les services sont désormais pleinement opérationnels. Nous nous excusons pour la gêne occasionnée et vous… | 9 min | Resolved |
| Apr 22, 2026 | Scheduled Maintenance - Vade CloudThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Apr 21, 2026 | Scheduled Maintenance - Partner PortalThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Apr 15, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Mar 19, 2026 | Scheduled Maintenance - Firewall updateThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Mar 11, 2026 | Scheduled Maintenance - FilterThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Mar 9, 2026 | Firewall MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Mar 9, 2026 | Vade Cloud EU - Incident DNSThe cause of the incident has been resolved. The Vade Cloud Service is again fully operational and solved sustainably. | 1h 6m | Resolved |
| Feb 16, 2026 | Vade Cloud UIThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Feb 12, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Feb 11, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Feb 4, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Feb 3, 2026 | Network IssueThe cause of the incident has been resolved. The Filter Updates and Safe Unsubscribe services are now fully operational. | 3h 46m | Resolved |
| Jan 20, 2026 | Is It Phishing - Scheduled MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Vade Services incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Vade Services Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Vade Services acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Vade Services outage in this window ran 6d 20h, against a mean recovery of 19h 6m. If you depend on Vade Services in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.