Is Buffer Down?
Reachable from all 8 checked regions
Average response time: 1011ms
Last checked · checks run every 6 hours
Official status page: https://status.buffer.com
Buffer uptime
Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 55 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
30-day history
42-day clean streakReachability by region
Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.
What Buffer does
Buffer schedules posts to social networks from a single queue, aimed at small teams and individual creators rather than large enterprises. Users load a week of content at once and stop thinking about it, so an outage tends to be discovered days later through a gap in a posting schedule nobody was watching.
What an outage looks like
Scheduled posts do not publish at their set time, and the queue shows them as pending or failed afterwards. Connected channels appear disconnected and ask to be reauthorised. The dashboard fails to load or shows an empty queue, which is alarming but usually a display problem. Analytics stop updating and the publishing API returns errors.
What to do about it
Check status.buffer.com, which groups components into Core Buffer, Social Networks and the Developer Platform, so a failure affecting one network does not mean the whole queue is stuck. Verify on the social network itself whether a post published, rather than trusting the queue, and avoid rescheduling anything that may already have gone out.
Is it down for everyone, or just you?
If this page says Buffer is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.
Related services
Buffer outage FAQ
Did my scheduled post publish during the outage?
Is Buffer down or has a channel disconnected?
Do failed posts retry automatically?
Why is my queue empty when I had posts scheduled?
Does a Buffer outage affect posts already published?
How we measure this
- We request Buffer's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Buffer publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.
Get alerted when Buffer goes down
This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring