User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 121 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 96 ms | 0 |
| Mon 21 | 0 | 0.0 | 200 ms | 0 |
| Tue 00 | 0 | 0.0 | 207 ms | 0 |
| Tue 02 | 0 | 0.0 | 169 ms | 0 |
| Tue 04 | 0 | 0.0 | 104 ms | 0 |
| Tue 06 | 0 | 0.0 | 405 ms | 0 |
| Tue 08 | 0 | 0.0 | 278 ms | 0 |
| Tue 10 | 0 | 0.0 | 107 ms | 0 |
| Tue 12 | 0 | 0.0 | 312 ms | 0 |
| Tue 14 | 0 | 0.0 | 132 ms | 0 |
| Tue 17 | 0 | 0.0 | 176 ms | 0 |
| Tue 19 | 0 | 0.0 | 115 ms | 0 |
| Tue 21 | 0 | 0.0 | 119 ms | 0 |
| Tue 23 | 0 | 0.0 | 127 ms | 0 |
| Wed 02 | 0 | 0.0 | 138 ms | 0 |
| Wed 04 | 0 | 0.0 | 103 ms | 0 |
| Wed 06 | 0 | 0.0 | 161 ms | 0 |
| Wed 08 | 0 | 0.0 | 389 ms | 0 |
| Wed 11 | 0 | 0.0 | 80 ms | 0 |
| Wed 13 | 0 | 0.0 | 156 ms | 0 |
| Wed 15 | 0 | 0.0 | 253 ms | 0 |
| Wed 17 | 0 | 0.0 | 160 ms | 0 |
| Wed 19 | 0 | 0.0 | 207 ms | 0 |
| Wed 21 | 0 | 0.0 | 101 ms | 0 |
| Wed 23 | 0 | 0.0 | 375 ms | 0 |
| Thu 02 | 0 | 0.0 | 163 ms | 0 |
| Thu 04 | 0 | 0.0 | 197 ms | 0 |
| Thu 06 | 0 | 0.0 | 134 ms | 0 |
| Thu 08 | 0 | 0.0 | 110 ms | 0 |
| Thu 10 | 0 | 0.0 | 124 ms | 0 |
| Thu 12 | 0 | 0.0 | 83 ms | 0 |
| Thu 14 | 0 | 0.0 | 92 ms | 0 |
| Thu 16 | 0 | 0.0 | 56 ms | 0 |
| Thu 18 | 0 | 0.0 | 84 ms | 0 |
| Thu 19 | 0 | 0.0 | 122 ms | 0 |
| Thu 21 | 0 | 0.0 | 403 ms | 0 |
| Thu 23 | 0 | 0.0 | 49 ms | 0 |
| Fri 01 | 0 | 0.0 | 130 ms | 0 |
| Fri 03 | 0 | 0.0 | 215 ms | 0 |
| Fri 05 | 0 | 0.0 | 175 ms | 0 |
| Fri 07 | 0 | 0.0 | 99 ms | 0 |
| Fri 09 | 0 | 0.0 | 94 ms | 0 |
| Fri 11 | 0 | 0.0 | 336 ms | 0 |
| Fri 13 | 0 | 0.0 | 104 ms | 0 |
| Fri 15 | 0 | 0.0 | 89 ms | 0 |
| Fri 17 | 0 | 0.0 | 166 ms | 0 |
| Fri 18 | 0 | 0.0 | 132 ms | 0 |
| Fri 20 | 0 | 0.0 | 121 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for AWeber yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when AWeber goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send AWeber alerts to Slack, Discord or a webhook — free.
We track AWeber (aweber.com) as part of the Productivity group. Looking for free email marketing software? Get started with AWeber for free today. Powerfully-simple email marketing.
AWeber publishes an official status page at status.aweber.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 136 ms average, 49–336 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public AWeber incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
136 ms on average over the last 24 hours (49–336 ms).
Yes, at https://status.aweber.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report AWeber here at once, the problem is on AWeber's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with AWeber. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.