Skip to main content
Buffer logo

Is Buffer Down?

No — Buffer is up

Reachable from all 8 checked regions

Average response time: 968ms

Last checked · checks run every 6 hours

Official status page: https://status.buffer.com

Buffer uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
1188ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 1 day measured so far. A dash means we have no measurement for that window.

30-day history

Jun 29: no data
Jun 30: no data
Jul 1: no data
Jul 2: no data
Jul 3: no data
Jul 4: no data
Jul 5: no data
Jul 6: no data
Jul 7: no data
Jul 8: no data
Jul 9: no data
Jul 10: no data
Jul 11: no data
Jul 12: no data
Jul 13: no data
Jul 14: no data
Jul 15: no data
Jul 16: no data
Jul 17: no data
Jul 18: no data
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: 100.00% uptime, 16 checks
Jun 29 Today
No downtime Partial Downtime Not measurable No data

Reachability 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.

ams
498ms
DNS 0ms TCP 4ms TLS 14ms TTFB 317ms
arn
414ms
DNS 0ms TCP 1ms TLS 12ms TTFB 306ms
lhr
877ms
DNS 0ms TCP 1ms TLS 13ms TTFB 716ms
nrt
2610ms
DNS 0ms TCP 0ms TLS 16ms TTFB 2275ms
ord
404ms
DNS 0ms TCP 1ms TLS 10ms TTFB 370ms
sin
679ms
DNS 0ms TCP 0ms TLS 10ms TTFB 439ms
sjc
683ms
DNS 0ms TCP 0ms TLS 15ms TTFB 548ms
syd
2081ms
DNS 0ms TCP 13ms TLS 9ms TTFB 1658ms
yyz
382ms
DNS 0ms TCP 0ms TLS 10ms TTFB 335ms

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 all 18 regions to find out where it breaks.

Test it yourself

Related services

Hootsuite
Hootsuite
Bitly
Bitly
Patreon
Patreon
HubSpot
HubSpot

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 — 8 of them answered the most recent check.
  • 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. 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, and let it override us in both directions.

Get alerted when Buffer goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required