Is Buffer Down?

No — Buffer is up

Buffer's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 444 ms

Right now

The verdict is the worse of these two. How we decide

Buffer's status page

status.buffer.com · read 4 minutes ago · checked every 3 minutes

Operational

Buffer's components, as its status page reports them
Component	Status
Login	Operational
Channel connections	Operational
Publishing	Operational
Analytics	Operational
Community	Operational
Settings	Operational
Instagram	Operational
Facebook	Operational
Threads	Operational
LinkedIn	Operational
X	Operational
Bluesky	Operational

7 more, all operational · show all 19

All of Buffer's components
Component	Status
Login	Operational
Channel connections	Operational
Publishing	Operational
Analytics	Operational
Community	Operational
Settings	Operational
Instagram	Operational
Facebook	Operational
Threads	Operational
LinkedIn	Operational
X	Operational
Bluesky	Operational
Youtube	Operational
TikTok	Operational
Mastodon	Operational
Pinterest	Operational
Google Business profile	Operational
Buffer API	Operational
Buffer MCP	Operational

Open their status page

FlareWarden checks

buffer.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 444 ms
Checked: 1 hour ago

By region

Amsterdam reachable, 519 ms
Chicago reachable, 110 ms
Paris reachable, 448 ms
San Jose reachable, 349 ms
Singapore reachable, 376 ms
Stockholm reachable, 194 ms
Sydney reachable, 1317 ms
Toronto reachable, 242 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	54 ms	3 ms	13 ms	454 ms
Chicago	26 ms	1 ms	13 ms	104 ms
Paris	20 ms	2 ms	11 ms	372 ms
San Jose	57 ms	2 ms	20 ms	281 ms
Singapore	75 ms	1 ms	12 ms	370 ms
Stockholm	26 ms	2 ms	12 ms	188 ms
Sydney	103 ms	1 ms	12 ms	1080 ms
Toronto	77 ms	1 ms	11 ms	225 ms

We check that buffer.com loads, not every feature behind it. Test it yourself

History

Incidents Buffer reported

Since Oct 22, 15 days · from status.buffer.com

Incidents: 3
Major or critical: 3
Median to resolve: 11m

Issue with "Publish Now" action.
major · Nov 2
lasted 55m
Issue with [Feature]
major · Nov 2
lasted 10m
Degraded Performance
major · Oct 22
lasted 11m

Buffer website availability

Measured by FlareWarden · buffer.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 684ms

Last 30 days

91-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of buffer.com from multiple regions every 6 hours. Buffer's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Buffer outage FAQ

Did my scheduled post publish during the outage?

Check the social network directly rather than Buffer's queue, because the two can disagree. A post may publish successfully while the queue still shows it pending, and the reverse also happens. Missed posts are not always retried automatically, so anything tied to a campaign date is worth confirming at the source.

Is Buffer down or has a channel disconnected?

Social networks expire access tokens periodically, and a disconnected channel is far more common than a Buffer incident. It shows as one network failing while others publish normally, with a prompt to reconnect. Check status.buffer.com, then reconnect the affected channel rather than waiting for a status page that will stay green.

Do failed posts retry automatically?

Not dependably. A post that failed at its scheduled time may sit in the queue marked as failed rather than being re-attempted, and the timing that made it worth scheduling has usually passed anyway. Review the queue after any incident and decide which items are still worth publishing rather than assuming they went out late.

Why is my queue empty when I had posts scheduled?

An empty dashboard during an incident is usually a loading failure rather than deleted content. The queue is stored server-side and reappears when the service recovers. Avoid rebuilding the schedule from scratch while the dashboard is unreliable, since the original posts return and you end up publishing everything twice.

Does a Buffer outage affect posts already published?

No. Once a post reaches a social network it belongs to that network, and Buffer has no further role in serving it. Anything already live stays live and visible to your audience regardless of Buffer's state. What an incident affects is scheduling, publishing and the analytics gathered afterwards.

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Buffer itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Buffer goes down

We check Buffer every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required