Intermittent 502 errors
Timeline · 2 updates
- investigating Mar 18, 2026, 10:54 PM UTC
We are experiencing intermittent 502 errors and are actively investigating the issue.
- resolved Mar 18, 2026, 11:12 PM UTC
This incident has been resolved
Cambly had 12 outages in the last 2 years totaling 17h 16m of downtime — averaging 0.5 incidents per month.
There were 12 Cambly outages since May 21, 2024 totaling 17h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are experiencing intermittent 502 errors and are actively investigating the issue.
This incident has been resolved
Cloudflare had an outage from about 08:56 to 09:20 UTC: https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q All of cambly.com was unavailable during this time.
We are continuing to monitor the ongoing incident with our provider, AWS. Some users may experience issues when using Cambly. AWS is actively working on a fix and our services will be restored once their systems are back online.
We are continuing to monitor for any further issues.
The incident with our provider, AWS, has been resolved, and their systems are back to normal. All Cambly services have been fully restored.
We are currently investigating this issue.
The issue has been identified and a fix has been successfully implemented. Monitoring confirms that systems are functioning as expected.
We experienced intermittent issues with web page loading timeouts. We have taken steps to address the issue and are monitoring for further issues.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Cambly experienced slow load times from 21:34 UTC 21:40 UTC.
Some students are seeing an error when visiting Cambly on Safari. We are working on a fix.
We've released a fix.
We are investigating slow load times.
We have restarted the server that was causing slow load times and errors.
We are currently investigating this issue.
The classroom is currently having issues, we are currently investigating
We have identified and deployed a fix. We will be monitoring.
This incident has been resolved
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.