All Systems Operational

AWS Operational
Web application Operational
API Operational
Box Content Preview Operational
Braintree European Processing Operational
Azure Operational
Web application Operational
API Operational
Scaleway Operational
Web application Operational
API Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

Oct 12, 2026

No incidents reported today.

Oct 11, 2026

No incidents reported.

Oct 10, 2026

No incidents reported.

Oct 9, 2026

No incidents reported.

Oct 8, 2026

No incidents reported.

Oct 7, 2026

Resolved - On October 7, between 14:18 and 14:35 CEST, and again between 15:03 and 15:18 CEST, some users experienced errors or pages failing to load on the web platform, and part of the API requests returned errors. The cause was an overload of our internal messaging system, triggered by an unusually large volume of background tasks. The platform has been operating normally since 15:18 CEST. Some background processing, such as automatic enrollments and their notifications, is delayed and is expected to catch up by this evening. If you received API errors during these windows, please check the result of the affected requests before retrying them. We apologize for the inconvenience and are putting safeguards in place to prevent this from happening again.
Oct 7, 16:00 CEST

Oct 6, 2026

No incidents reported.

Oct 5, 2026

No incidents reported.

Oct 4, 2026

No incidents reported.

Oct 3, 2026

No incidents reported.

Oct 2, 2026

No incidents reported.

Oct 1, 2026

No incidents reported.

Sep 30, 2026

No incidents reported.

Sep 29, 2026

No incidents reported.

Sep 28, 2026

Resolved - Between Friday, September 25 at 18:00 and Monday, September 28 at 09:55 (CEST), some users on certain custom subdomains intermittently saw broken styling or features that didn't load, because some CSS/JS assets weren't delivered correctly. A deployment issue caused this, and it was fixed this morning. All affected subdomains have been working normally since then. We're making changes to our deployment process so this doesn't happen again.
Sep 28, 09:55 CEST