AWeber Outage History
6 incidents recorded over the last 365 days, 1 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 AWeber Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 13, 2026 | Scheduled maintenanceWe have completed the scheduled maintenance. There was no interruption of AWeber services during the maintenance window. All services are currently operating normally. | 4h 0m | Scheduled |
| Oct 7, 2026 | Scheduled maintenanceWe have completed the scheduled maintenance. Unsubscribe links and customer logins were briefly unavailable for less than 1 minute at 8:22 PM ET during the maintenance window. All services are currently operating… | 2h 0m | Scheduled |
| Aug 28, 2026 | Signup forms outageThis incident has been resolved. | 35 min | Resolved |
| Jul 14, 2026 | Scheduled maintenanceWe have completed the scheduled maintenance. There was no interruption of AWeber services during the maintenance window. All services are currently operating normally. | 30 min | Scheduled |
| Jun 3, 2026 | Scheduled maintenanceWe have completed the scheduled maintenance. During this maintenance window, the ability to create/publish/unpublish Landing Pages and create/publish/unpublish AI Signup Forms from within AWeber was interrupted for… | 30 min | Scheduled |
| May 27, 2026 | Scheduled maintenanceWe have completed the scheduled maintenance. During this maintenance window, your ability to log in to your account was interrupted for less than 13 minutes from 9:09 PM to 9:22 PM ET. All services are now operating… | 3h 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 AWeber 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 AWeber 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 AWeber 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 AWeber outage in this window ran 4h, against a mean recovery of 1h 46m. If you depend on AWeber 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.