Screencastify Outage History
7 incidents recorded over the last 365 days, 4 of them resolved, 1 still open. 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 Screencastify Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 2, 2026 | Subscription and Billing Updates DelayedThe subscription access issue has been addressed, and affected users' access has been restored. We are continuing to monitor the system to ensure normal functionality. | — | Investigating |
| Sep 14, 2026 | Google Authorization Error Preventing AccessThis incident has been resolved. | 1174h 53m | Resolved |
| Sep 14, 2026 | Webcam Not Appearing During Full Screen Recordings.The fix for the webcam not appearing during full screen recordings is now available for both Chrome and Microsoft Edge users. Users should ensure they are using the latest version of the Screencastify extension to… | 95h 21m | Resolved |
| Aug 6, 2026 | Verification Email Delivery IssuesThis incident has been resolved. | 711h 42m | Resolved |
| Jul 17, 2026 | Scheduled Platform Maintenance (Possible Temporary Service Interruptions)The scheduled maintenance has been completed. | 30 min | Scheduled |
| Jul 14, 2026 | Resolved: Service Disruption Affecting Login, Recording, and Video PlaybackWe have resolved an incident that affected login, video playback, and recording. During this incident, some users were unable to sign in, access existing recordings, or create new recordings. Our engineering team… | -2754 min | Resolved |
| Feb 14, 2026 | Scheduled Maintenance- Temporary Service InterruptionThe 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 Screencastify 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 Screencastify 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 Screencastify 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 Screencastify outage in this window ran 48d 22h, against a mean recovery of 16d 12h. If you depend on Screencastify 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.