Atera Outage History

16 incidents recorded over the last 365 days, 16 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 Atera Incident

Atera incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 27, 2026Connection timeouts to app.atera.comThis incident has been resolved.52 minResolved
Oct 19, 2026Degraded Login PerformanceThis incident has been resolved.25h 7mResolved
Oct 8, 20262FA SMS Verification Delivery IssueThis incident has been resolved.138h 21mResolved
Jun 22, 2026Degraded Performance for Ticket ConversationsThis incident has been resolved3h 11mResolved
Jun 11, 2026Payment Processing Issue (Duplicate Charges)This incident has been resolved.282h 37mResolved
Jun 9, 2026Unexpected Device Availability AlertsThis incident has been resolved.4h 59mResolved
Apr 2, 2026Service Disruption Affecting US CustomersThe issue has been identified and resolved.3h 23mResolved
Mar 9, 2026Intermittent login issuesThis incident has been resolved.1h 57mResolved
Mar 9, 2026PSA Ticketing pageThis incident has been resolved.1h 22mResolved
Feb 22, 2026Auth0 Login fail issueThis incident has been resolved.2h 25mResolved
Feb 11, 2026Degraded / Slow GUI performanceThis incident has been resolved.1h 42mResolved
Jan 12, 2026Stability issues for EU & UK regionsThis incident has been resolved.3h 19mResolved
Jan 12, 2026Login issues for EU & UK regionsThis incident has been resolved.1h 10mResolved
Jan 5, 2026Splashtop Service InterruptionThis incident has been resolved.24 minResolved
Dec 5, 2025Cloudflare Outage Impacting ServicesThis incident has been resolved.1h 6mResolved
Nov 18, 2025Cloudflare Outage Impacting ServicesThis incident has been resolved.3h 56mResolved

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 Atera 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 Atera 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 Atera 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 Atera outage in this window ran 11d 18h, against a mean recovery of 1d 5h. If you depend on Atera 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.