User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
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 891 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 1012 ms | 0 |
| Tue 00 | 0 | 0.0 | 573 ms | 0 |
| Tue 02 | 0 | 0.0 | 1077 ms | 0 |
| Tue 05 | 0 | 0.0 | 793 ms | 0 |
| Tue 07 | 0 | 0.0 | 922 ms | 0 |
| Tue 09 | 0 | 0.0 | 911 ms | 0 |
| Tue 11 | 0 | 0.0 | 1028 ms | 0 |
| Tue 13 | 0 | 0.0 | 1000 ms | 0 |
| Tue 15 | 0 | 0.0 | 1671 ms | 0 |
| Tue 18 | 0 | 0.0 | 1069 ms | 0 |
| Tue 20 | 0 | 0.0 | 627 ms | 0 |
| Tue 22 | 0 | 0.0 | 906 ms | 0 |
| Wed 00 | 0 | 0.0 | 821 ms | 0 |
| Wed 03 | 0 | 0.0 | 1040 ms | 0 |
| Wed 05 | 0 | 0.0 | 949 ms | 0 |
| Wed 07 | 0 | 0.0 | 939 ms | 0 |
| Wed 09 | 0 | 0.0 | 916 ms | 0 |
| Wed 12 | 0 | 0.0 | 954 ms | 0 |
| Wed 14 | 0 | 0.0 | 924 ms | 0 |
| Wed 16 | 0 | 0.0 | 1062 ms | 0 |
| Wed 18 | 0 | 0.0 | 867 ms | 0 |
| Wed 20 | 0 | 0.0 | 1055 ms | 0 |
| Wed 22 | 0 | 0.0 | 737 ms | 0 |
| Thu 00 | 0 | 0.0 | 1028 ms | 0 |
| Thu 03 | 0 | 0.0 | 930 ms | 0 |
| Thu 05 | 0 | 0.0 | 1008 ms | 0 |
| Thu 07 | 0 | 0.0 | 1059 ms | 0 |
| Thu 09 | 0 | 0.0 | 856 ms | 0 |
| Thu 11 | 0 | 0.0 | 985 ms | 0 |
| Thu 13 | 0 | 0.0 | 980 ms | 0 |
| Thu 15 | 0 | 0.0 | 985 ms | 0 |
| Thu 17 | 0 | 0.0 | 1123 ms | 0 |
| Thu 19 | 0 | 0.0 | 416 ms | 0 |
| Thu 20 | 0 | 0.0 | 976 ms | 0 |
| Thu 22 | 0 | 0.0 | 992 ms | 0 |
| Fri 00 | 0 | 0.0 | 754 ms | 0 |
| Fri 02 | 0 | 0.0 | 871 ms | 0 |
| Fri 04 | 0 | 0.0 | 914 ms | 0 |
| Fri 06 | 0 | 0.0 | 819 ms | 0 |
| Fri 08 | 0 | 0.0 | 864 ms | 0 |
| Fri 10 | 0 | 0.0 | 864 ms | 0 |
| Fri 11 | 0 | 0.0 | 467 ms | 0 |
| Fri 13 | 0 | 0.0 | 896 ms | 0 |
| Fri 15 | 0 | 0.0 | 933 ms | 0 |
| Fri 17 | 0 | 0.0 | 947 ms | 0 |
| Fri 18 | 0 | 0.0 | 1044 ms | 0 |
| Fri 20 | 0 | 0.0 | 906 ms | 0 |
| Fri 22 | 0 | 0.0 | 891 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 Asaas 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 Asaas goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Asaas alerts to Slack, Discord or a webhook — free.
We track Asaas (asaas.com) as part of the Cloud & developer group. Ofereça diferentes formas de pagamento, gerencie cobranças, emita notas, antecipe recebíveis e pague fornecedores. Tudo em um só lugar.
Asaas publishes an official status page at status.asaas.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 837 ms average, 400–1044 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Asaas incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
837 ms on average over the last 24 hours (400–1044 ms).
Yes, at https://status.asaas.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Asaas here at once, the problem is on Asaas'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 Asaas. 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.