Is brew down?

Last checked 4m ago
Current status
brew is up

No incidents right now.

brew is operational right now. Last checked 4m ago, with no incidents reported in the last 90 days.

Real-time brew status, recent outages, and incident history: pulled directly from brew's official status page at status.statusbrew.com every 5 minutes. Pingoru tracks 27 brew services and has captured 0 incidents in the last 90 days (100.00% uptime). Get email, Slack, Discord, or webhook alerts the moment brew reports a new incident, free for 3 monitors, no credit card.

Users who monitor brew also follow these Marketing services: Mailgun Klaviyo Iterable Braze Brevo Customer.io ZoomInfo Optimizely SurveyMonkey Yotpo View all 8,000+ providers
brew uptime 100.00% uptime · past 90 days
Mon Wed Fri
JulAugSepOct
Less More

Recent outages & incidents

No incidents reported for brew in the last 90 days.

Quiet provider, but we'll still email you the instant something changes.

Incident record

Since April 2026 · Statuspage by Atlassian · 27 components checked every 5 minutes
36incidents recorded
10last 12 months
0last 90 days
42 hourstypical duration, 12 months

The longest incident in the last year, META Profile Connection on February 4, 2026, ran for 5 days. 1 maintenance window announced in the same period.

Most affected components, last 12 months

  • Content Publishing7
  • Content Scheduling3
  • Facebook DMs and Comments3
  • Facebook Reports3
  • Instagram Comments3

Latest incidents

  • Undergoing Maintenance July 30, 2026 · 3 minutes · notice

    We are performing a database update and login is temporarily unavailable; we will update this page as soon as service is restored.

  • META API Down June 12, 2026 · 23 minutes · major outage

    Meta is having an outage that's affecting Facebook and Instagram features in Statusbrew. The issue is on Meta's side. We're monitoring and will update as it…

  • Publishing Disruption – May 30 (Resolved) May 31, 2026 · 108 minutes · notice

    We had a service disruption yesterday (May 30) between 15:32–17:20 UTC during which posts scheduled for publishing were not sent out. The issue has now been…