User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Social
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 32 min ago. Last stored result reached it in 2425 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 1766 ms | 0 |
| Mon 20 | 0 | 0.0 | 2872 ms | 0 |
| Mon 22 | 0 | 0.0 | 4644 ms | 0 |
| Tue 00 | 0 | 0.0 | 4315 ms | 0 |
| Tue 02 | 0 | 0.0 | 599 ms | 0 |
| Tue 04 | 0 | 0.0 | 3911 ms | 0 |
| Tue 06 | 0 | 0.0 | 4760 ms | 0 |
| Tue 09 | 0 | 0.0 | 3206 ms | 0 |
| Tue 11 | 0 | 0.0 | 2823 ms | 0 |
| Tue 13 | 0 | 0.0 | 1838 ms | 0 |
| Tue 15 | 0 | 0.0 | 4913 ms | 0 |
| Tue 17 | 0 | 0.0 | 4173 ms | 0 |
| Tue 20 | 0 | 0.0 | 6368 ms | 0 |
| Tue 22 | 0 | 0.0 | — | 0 |
| Wed 00 | 0 | 0.0 | 7521 ms | 0 |
| Wed 02 | 0 | 0.0 | 4558 ms | 0 |
| Wed 05 | 0 | 0.0 | — | 0 |
| Wed 07 | 0 | 0.0 | 3815 ms | 0 |
| Wed 09 | 0 | 0.0 | 2622 ms | 0 |
| Wed 11 | 0 | 0.0 | 2136 ms | 0 |
| Wed 13 | 0 | 0.0 | 6171 ms | 0 |
| Wed 15 | 0 | 0.0 | 3586 ms | 0 |
| Wed 18 | 0 | 0.0 | 6329 ms | 0 |
| Wed 20 | 0 | 0.0 | 1118 ms | 0 |
| Wed 22 | 0 | 0.0 | 2447 ms | 0 |
| Thu 00 | 0 | 0.0 | 2045 ms | 0 |
| Thu 02 | 0 | 0.0 | 4534 ms | 0 |
| Thu 04 | 0 | 0.0 | 2116 ms | 0 |
| Thu 06 | 0 | 0.0 | 3032 ms | 0 |
| Thu 08 | 0 | 0.0 | 3187 ms | 0 |
| Thu 10 | 0 | 0.0 | 4141 ms | 0 |
| Thu 12 | 0 | 0.0 | 90 ms | 0 |
| Thu 15 | 0 | 0.0 | 2844 ms | 0 |
| Thu 17 | 0 | 0.0 | 154 ms | 0 |
| Thu 19 | 0 | 0.0 | 3015 ms | 0 |
| Thu 21 | 0 | 0.0 | 4375 ms | 0 |
| Thu 23 | 0 | 0.0 | 4489 ms | 0 |
| Fri 01 | 0 | 0.0 | 2379 ms | 0 |
| Fri 03 | 0 | 0.0 | 2096 ms | 0 |
| Fri 05 | 0 | 0.0 | 4850 ms | 0 |
| Fri 07 | 0 | 0.0 | 2499 ms | 0 |
| Fri 09 | 0 | 0.0 | 6133 ms | 0 |
| Fri 10 | 0 | 0.0 | 2282 ms | 0 |
| Fri 11 | 0 | 0.0 | 68 ms | 0 |
| Fri 12 | 0 | 0.0 | 3311 ms | 0 |
| Fri 14 | 0 | 0.0 | 2951 ms | 0 |
| Fri 16 | 0 | 0.0 | 23 ms | 0 |
| Fri 18 | 0 | 0.0 | 2425 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for AdaptlyPost 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 AdaptlyPost goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send AdaptlyPost alerts to Slack, Discord or a webhook — free.
We track AdaptlyPost (adaptlypost.com) as part of the Social group. Save hours every week with a social media scheduler that automates posts to Instagram, TikTok, YouTube, X, Facebook, LinkedIn, and more.
AdaptlyPost publishes an official status page at status.adaptlypost.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with social services: feeds not loading, posts or messages not sending, and login loops.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 2866 ms average, 23–6133 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public AdaptlyPost incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
2866 ms on average over the last 24 hours (23–6133 ms).
Yes, at https://status.adaptlypost.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For social services, watch for feeds not loading, posts or messages not sending, and login loops. If many people report AdaptlyPost here at once, the problem is on AdaptlyPost'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 AdaptlyPost. 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.