Amplify Outage History

29 incidents recorded over the last 365 days, 28 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.

Live Amplify status100.00% uptime history

Every Recorded Amplify Incident

Amplify incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 1, 2026mCLASS Lectura - Student Online AssessmentsThis incident has been resolved.171h 56mResolved
Sep 16, 2026Salesforce Services DisruptionThe Salesforce Technology Team has resolved this issue! All functionality tied to Salesforce has been fully restored and working as expected. Thank you so much!6h 16mResolved
Sep 11, 2026Brief Clever Login IssuesThis incident has been resolved.16h 31mResolved
Sep 9, 2026mCLASS Student Assessments: Brief Service DisruptionThis incident has been resolved.11h 31mResolved
Aug 17, 2026Customer Support ChatThis incident has been resolved.533h 47mResolved
Aug 3, 2026Web Form Support TicketsThis incident has been resolved.17h 10mResolved
Jul 30, 2026Phone Support Service IssueThis incident has been resolved.1h 52mResolved
Jul 7, 2026Phone Support Service IssueThis incident has been resolved. All phone lines are now open. Thank you again for your patience!49h 4mResolved
May 9, 2026Scheduled Maintenance WindowThe scheduled maintenance has been completed.2h 0mScheduled
Apr 30, 2026Amplify PD Site Accessibility IssueOur Engineering team was able to identify the root cause of this issue and have implemented a fix. Our PD site is now working as expected. Thank you again for your patience!27 minResolved
Apr 27, 2026Scheduled Maintenance WindowOur scheduled maintenance has been completed. Thank you so much for your patience!11h 54mResolved
Apr 21, 2026Scheduled Maintenance WindowThis incident has been resolved.122h 41mResolved
Apr 2, 2026Scheduled Maintenance WindowYesterday evening’s scheduled maintenance was successful.13h 25mResolved
Mar 10, 2026Science and ELA - Intermittent Activity DisruptionThis incident has been resolved.559h 58mResolved
Mar 10, 2026Amplify Home Page - Intermittent Error MessagesThis incident has been resolved.1h 5mResolved
Feb 25, 2026Classwork and Other Curriculum Application IssuesThis incident has been resolved.1h 43mResolved
Feb 13, 2026mCLASS Assessment - Unexpected Error MessagesWe are setting this incident to Resolved. If you are still experiencing error messages in mCLASS Assessment, please contact our Support team for further assistance: https://service.amplify.com/support Thank you so much!2h 19mResolved
Feb 10, 2026Amplify Service DisruptionThis incident has been resolved.64h 41mResolved
Feb 10, 2026mCLASS Assessment Loading IssuesThis incident has been resolved.189h 22mResolved
Feb 4, 2026Loading Issues in Science and ELAThis incident has been resolved.2h 53mResolved
Jan 22, 2026Scheduled Maintenance WindowThis incident has been resolved.700h 38mResolved
Jan 13, 20266-8 Science and ELA: Student Activity DisruptionThis incident has been resolved.10h 35mResolved
Jan 12, 2026Login and Navigation Service DisruptionThis incident has been resolved.532h 30mResolved
Dec 18, 2025CKLA Hub Accessibility IssuesThis incident has been resolved.24 minResolved
Dec 10, 2025Login and Navigation Service DisruptionThis incident has been resolved.141h 12mResolved
Dec 8, 2025Amplify Classroom Assignment Generation IssueThis incident has been resolved.19 minResolved
Dec 1, 2025Login and Navigation Service DisruptionThis incident has been resolved.92h 51mResolved
Nov 17, 2025Login and Navigation Service DisruptionThis issue has been officially resolved. We thank you so much for your patience!50h 43mResolved
Nov 12, 2025mCLASS Instruction PageThis incident has been resolved.50h 10mResolved

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 Amplify 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 Amplify 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 Amplify 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 Amplify outage in this window ran 29d 4h, against a mean recovery of 4d 19h. If you depend on Amplify 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.