helloasso Outage History
7 incidents recorded over the last 365 days, 7 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 helloasso Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 12, 2026 | Échec de paiement par carte bancaireThis incident has been resolved. | 26h 0m | Resolved |
| Sep 9, 2026 | Retards de confirmation des paiementsIncident résolu : le traitement des paiements fonctionne normalement depuis le 09/09 18h10. | 14h 48m | Resolved |
| Aug 26, 2026 | Retards de confirmation des paiementsNotre monitoring continu n'a détecté aucun nouveau retard depuis la résolution. L'incident est définitivement résolu et le service fonctionne normalement. Merci pour votre patience. | 12h 54m | Resolved |
| Apr 15, 2026 | Indisponibilité de la plateformeRésolu depuis 15h08 | 14 min | Resolved |
| Feb 25, 2026 | Interruption partielle des paiements sur la plateformeL’incident concernant l’interruption partielle des paiements (lié à notre prestataire Worldline) est désormais résolu. | 3h 25m | Resolved |
| Dec 5, 2025 | Indisponibilité du service de connexion à HelloAssoL'incident est résolu, la connexion à HelloAsso est de nouveau pleinement fonctionnelle | 3h 58m | Resolved |
| Nov 18, 2025 | Indisponibilité HelloAssoL'incident est résolu depuis le 18/11 15h45 | 18h 51m | Resolved |
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 helloasso 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 helloasso 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 helloasso 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 helloasso outage in this window ran 1d 2h, against a mean recovery of 11h 27m. If you depend on helloasso 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.