Skip to content

Outage tracker / Homebrew

Is Homebrew down?

I'm having a problem

Operationalchecked 2 minutes ago

We reached Homebrew from all 10 regions we check.

Functional endpoints verified

No outage recorded in the 14 days we have measured Homebrew (since Aug 22, 2026).

our independent probeslive · checked Sep 5, 2026, 2:06 AM UTC
US-East904 msOperational
US-West315 msOperational
Europe211 msOperational
Asia-Pacific306 msOperational
US-Central862 msOperational
Canada546 msOperational
UK524 msOperational
Southeast Asia862 msOperational
Australia598 msOperational
South America289 msOperational
their status pagetheir claim, not our reading

Homebrew publishes no status feed we can read, so the only independent reading here is ours on the left.

Homebrew response time, by region

US-East
769msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 993ms2026-08-23 UTC: p95 1.0s2026-08-24 UTC: p95 959ms2026-08-25 UTC: p95 1.5s2026-08-26 UTC: p95 1.3s2026-08-27 UTC: p95 1.4s2026-08-28 UTC: p95 1.5s2026-08-29 UTC: p95 1.3s2026-08-30 UTC: p95 1.1s2026-08-31 UTC: p95 1.3s2026-09-01 UTC: p95 1.2s2026-09-02 UTC: p95 1.4s2026-09-03 UTC: p95 1.3s2026-09-04 UTC: p95 772ms2026-09-05 UTC: p95 769ms
Aug 7Aug 21Sep 5
US-West
414msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 672ms2026-08-23 UTC: p95 871ms2026-08-24 UTC: p95 551ms2026-08-25 UTC: p95 653ms2026-08-26 UTC: p95 685ms2026-08-27 UTC: p95 890ms2026-08-28 UTC: p95 701ms2026-08-29 UTC: p95 823ms2026-08-30 UTC: p95 1.0s2026-08-31 UTC: p95 647ms2026-09-01 UTC: p95 651ms2026-09-02 UTC: p95 626ms2026-09-03 UTC: p95 737ms2026-09-04 UTC: p95 593ms2026-09-05 UTC: p95 414ms
Aug 7Aug 21Sep 5
Europe
385msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 402ms2026-08-23 UTC: p95 686ms2026-08-24 UTC: p95 613ms2026-08-25 UTC: p95 633ms2026-08-26 UTC: p95 703ms2026-08-27 UTC: p95 463ms2026-08-28 UTC: p95 582ms2026-08-29 UTC: p95 556ms2026-08-30 UTC: p95 433ms2026-08-31 UTC: p95 623ms2026-09-01 UTC: p95 685ms2026-09-02 UTC: p95 597ms2026-09-03 UTC: p95 772ms2026-09-04 UTC: p95 610ms2026-09-05 UTC: p95 385ms
Aug 7Aug 21Sep 5
Asia-Pacific
653msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 442ms2026-08-23 UTC: p95 688ms2026-08-24 UTC: p95 810ms2026-08-25 UTC: p95 1.1s2026-08-26 UTC: p95 834ms2026-08-27 UTC: p95 842ms2026-08-28 UTC: p95 726ms2026-08-29 UTC: p95 802ms2026-08-30 UTC: p95 733ms2026-08-31 UTC: p95 804ms2026-09-01 UTC: p95 898ms2026-09-02 UTC: p95 1.4s2026-09-03 UTC: p95 1.2s2026-09-04 UTC: p95 683ms2026-09-05 UTC: p95 653ms
Aug 7Aug 21Sep 5
US-Central
851msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.2s2026-09-04 UTC: p95 1.2s2026-09-05 UTC: p95 851ms
Aug 7Aug 21Sep 5
Canada
519msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.2s2026-09-04 UTC: p95 739ms2026-09-05 UTC: p95 519ms
Aug 7Aug 21Sep 5
UK
516msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 525ms2026-09-04 UTC: p95 517ms2026-09-05 UTC: p95 516ms
Aug 7Aug 21Sep 5
Southeast Asia
832msp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.4s2026-09-04 UTC: p95 1.0s2026-09-05 UTC: p95 832ms
Aug 7Aug 21Sep 5
Australia
1.1sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.6s2026-09-04 UTC: p95 1.4s2026-09-05 UTC: p95 1.1s
Aug 7Aug 21Sep 5
South America
305msp95 · latest
1s500ms0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 982ms2026-09-04 UTC: p95 881ms2026-09-05 UTC: p95 305ms
Aug 7Aug 21Sep 5

Is it Homebrew, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Homebrew -- it cannot diagnose Homebrew's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 904msstatus code: 200checked: Sep 5, 2026, 2:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Homebrew normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 315msstatus code: 200checked: Sep 5, 2026, 2:06 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Homebrew normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 862msstatus code: 200checked: Sep 5, 2026, 2:01 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Homebrew normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 546msstatus code: 200checked: Sep 5, 2026, 2:02 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Homebrew normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 289msstatus code: 200checked: Sep 5, 2026, 2:03 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Homebrew normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 211msstatus code: 200checked: Sep 5, 2026, 1:42 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Homebrew normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 524msstatus code: 200checked: Sep 5, 2026, 2:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Homebrew normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 306msstatus code: 200checked: Sep 5, 2026, 1:54 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Homebrew normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 862msstatus code: 200checked: Sep 5, 2026, 2:00 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Homebrew normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 598msstatus code: 200checked: Sep 5, 2026, 2:03 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Homebrew normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Homebrew, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Homebrew yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for Homebrew.

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Homebrew since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Homebrew covering any window you pick, with our measurements and Homebrew's own claim at the time, side by side.

Full availability history for Homebrew: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Homebrew, and again when they can reach it again. That is our own measurement from ten regions, not Homebrew's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Homebrew uptime measured by RealUptimeLive, from this page's own readings.
[![Homebrew uptime measured by RealUptime](https://realuptime.io/outages/homebrew/badge.svg?days=30)](https://realuptime.io/outages/homebrew)
<a href="https://realuptime.io/outages/homebrew"><img src="https://realuptime.io/outages/homebrew/badge.svg?days=30" alt="Homebrew uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Homebrew's SLA implies, from our measurement

At or above your target

We measured none of downtime for Homebrew over the 338h 8m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Homebrew's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://formulae.brew.sh/api/formula/wget.json
RealUptime is not affiliated with Homebrew; the name identifies what we measured, and nothing here speaks for Homebrew's own team. We send a single web request to Homebrew from 10 regions on our own schedule and time the response. We do not see inside Homebrew's systems, do not use an account or real transaction, and are not the same signal Homebrew's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Homebrew is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.