Skip to content

Outage tracker / Homebrew

Is Homebrew down?

I'm having a problem

Checks passingchecked 4 minutes ago

Our checks of Homebrew pass from all 10 regions we check.

As of Nov 5, 2026, 3:20 PM UTC, RealUptime's checks of Homebrew passed in all 10 regions that returned a reading.

Front-door and live API checks

Our checks of Homebrew did not fail from two or more distant regions in the 75 days we have checked it (since Aug 22, 2026). This does not show Homebrew works for users.

our check readinglive · checked Nov 5, 2026, 3:20 PM UTC
US-East217 msChecks passing
US-West1022 msChecks passing
Europe660 msChecks passing
Asia-Pacific1273 msChecks passing
US-Central498 msChecks passing
Canada788 msChecks passing
UK310 msChecks passing
Southeast Asia995 msChecks passing
Australia502 msChecks passing
South America1292 msChecks passing
their status pagetheir claim, not our reading

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

Homebrew response time, by region

US-East
1.2sp95 · 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-10-07 UTC: p95 960ms2026-10-08 UTC: p95 694ms2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 753ms2026-10-11 UTC: p95 761ms2026-10-12 UTC: p95 601ms2026-10-13 UTC: p95 691ms2026-10-14 UTC: p95 625ms2026-10-15 UTC: p95 686ms2026-10-16 UTC: p95 652ms2026-10-17 UTC: p95 861ms2026-10-18 UTC: p95 964ms2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.1s2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 887ms2026-10-29 UTC: p95 939ms2026-10-30 UTC: p95 907ms2026-10-31 UTC: p95 750ms2026-11-01 UTC: p95 895ms2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
US-West
2.6sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 654ms2026-10-08 UTC: p95 660ms2026-10-09 UTC: p95 644ms2026-10-10 UTC: p95 690ms2026-10-11 UTC: p95 607ms2026-10-12 UTC: p95 802ms2026-10-13 UTC: p95 804ms2026-10-14 UTC: p95 870ms2026-10-15 UTC: p95 983ms2026-10-16 UTC: p95 658ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 948ms2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.8s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.7s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.0s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 2.6s
Oct 7Oct 21Nov 5
Europe
1.3sp95 · latest
2.5s1.3s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 537ms2026-10-08 UTC: p95 490ms2026-10-09 UTC: p95 597ms2026-10-10 UTC: p95 514ms2026-10-11 UTC: p95 544ms2026-10-12 UTC: p95 476ms2026-10-13 UTC: p95 458ms2026-10-14 UTC: p95 398ms2026-10-15 UTC: p95 421ms2026-10-16 UTC: p95 412ms2026-10-17 UTC: p95 867ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.0s2026-10-24 UTC: p95 1.0s2026-10-25 UTC: p95 1.0s2026-10-26 UTC: p95 980ms2026-10-27 UTC: p95 831ms2026-10-28 UTC: p95 867ms2026-10-29 UTC: p95 875ms2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 574ms2026-11-01 UTC: p95 479ms2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
Asia-Pacific
1.9sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 876ms2026-10-08 UTC: p95 916ms2026-10-09 UTC: p95 894ms2026-10-10 UTC: p95 797ms2026-10-11 UTC: p95 777ms2026-10-12 UTC: p95 971ms2026-10-13 UTC: p95 939ms2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 840ms2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.6s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.3s2026-10-25 UTC: p95 1.3s2026-10-26 UTC: p95 1.5s2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.0s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 935ms2026-11-01 UTC: p95 926ms2026-11-02 UTC: p95 2.6s2026-11-03 UTC: p95 2.2s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
US-Central
841msp95 · 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-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 1.0s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 975ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 922ms2026-10-24 UTC: p95 1.0s2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 970ms2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 887ms2026-10-29 UTC: p95 875ms2026-10-30 UTC: p95 911ms2026-10-31 UTC: p95 1.0s2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 939ms2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 841ms
Oct 7Oct 21Nov 5
Canada
1.1sp95 · 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-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 927ms2026-10-12 UTC: p95 954ms2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 934ms2026-10-18 UTC: p95 887ms2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 916ms2026-10-21 UTC: p95 972ms2026-10-22 UTC: p95 964ms2026-10-23 UTC: p95 953ms2026-10-24 UTC: p95 974ms2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.5s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
UK
503msp95 · 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-10-07 UTC: p95 401ms2026-10-08 UTC: p95 428ms2026-10-09 UTC: p95 462ms2026-10-10 UTC: p95 419ms2026-10-11 UTC: p95 428ms2026-10-12 UTC: p95 423ms2026-10-13 UTC: p95 457ms2026-10-14 UTC: p95 420ms2026-10-15 UTC: p95 366ms2026-10-16 UTC: p95 579ms2026-10-17 UTC: p95 602ms2026-10-18 UTC: p95 652ms2026-10-19 UTC: p95 616ms2026-10-20 UTC: p95 675ms2026-10-21 UTC: p95 643ms2026-10-22 UTC: p95 675ms2026-10-23 UTC: p95 519ms2026-10-24 UTC: p95 531ms2026-10-25 UTC: p95 611ms2026-10-26 UTC: p95 714ms2026-10-27 UTC: p95 506ms2026-10-28 UTC: p95 480ms2026-10-29 UTC: p95 543ms2026-10-30 UTC: p95 523ms2026-10-31 UTC: p95 497ms2026-11-01 UTC: p95 639ms2026-11-02 UTC: p95 799ms2026-11-03 UTC: p95 772ms2026-11-04 UTC: p95 593ms2026-11-05 UTC: p95 503ms
Oct 7Oct 21Nov 5
Southeast Asia
1.6sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 737ms2026-10-08 UTC: p95 720ms2026-10-09 UTC: p95 727ms2026-10-10 UTC: p95 761ms2026-10-11 UTC: p95 753ms2026-10-12 UTC: p95 763ms2026-10-13 UTC: p95 671ms2026-10-14 UTC: p95 610ms2026-10-15 UTC: p95 701ms2026-10-16 UTC: p95 654ms2026-10-17 UTC: p95 944ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 943ms2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.0s2026-10-24 UTC: p95 616ms2026-10-25 UTC: p95 943ms2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 788ms2026-10-28 UTC: p95 1.8s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 691ms2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 804ms2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 1.6s
Oct 7Oct 21Nov 5
Australia
2.7sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.6s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 902ms2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 1.0s2026-10-25 UTC: p95 962ms2026-10-26 UTC: p95 821ms2026-10-27 UTC: p95 984ms2026-10-28 UTC: p95 1.8s2026-10-29 UTC: p95 2.0s2026-10-30 UTC: p95 1.0s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.9s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 2.7s
Oct 7Oct 21Nov 5
South America
1.5sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 831ms2026-10-09 UTC: p95 731ms2026-10-10 UTC: p95 728ms2026-10-11 UTC: p95 667ms2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 937ms2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 781ms2026-10-21 UTC: p95 759ms2026-10-22 UTC: p95 1.0s2026-10-23 UTC: p95 8.8s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.4s2026-10-27 UTC: p95 2.6s2026-10-28 UTC: p95 1.6s2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 2.2s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 1.5s
Oct 7Oct 21Nov 5

Check your own site while you wait on Homebrew

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.

Get an email when our checks of Homebrew fail from two or more distant regions, and again when they pass

Get an email when our checks change

We will email you when our checks of Homebrew fail from two or more distant regions, and again when they pass. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when our checks fail from two or more distant regions, one when they pass, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is our own reading from outside. It is not Homebrew's official status.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 217msstatus code: 200checked: Nov 5, 2026, 3:04 PM 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
      Checks passinglatency: 1022msstatus code: 200checked: Nov 5, 2026, 3:20 PM 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
      Checks passinglatency: 498msstatus code: 200checked: Nov 5, 2026, 2:37 PM 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
      Checks passinglatency: 788msstatus code: 200checked: Nov 5, 2026, 2:44 PM 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
    Checks passinglatency: 1292msstatus code: 200checked: Nov 5, 2026, 3:10 PM 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 660msstatus code: 200checked: Nov 5, 2026, 2:44 PM 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
      Checks passinglatency: 310msstatus code: 200checked: Nov 5, 2026, 2:46 PM 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1273msstatus code: 200checked: Nov 5, 2026, 2:23 PM 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
      Checks passinglatency: 995msstatus code: 200checked: Nov 5, 2026, 3:00 PM 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
      Checks passinglatency: 502msstatus code: 200checked: Nov 5, 2026, 2:27 PM 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 probe events

No probe events on record yet for Homebrew.

check 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 check readings and Homebrew's own claim at the time, side by side.

Full check history for Homebrew: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Homebrew uptime by RealUptime's checksLive, from this page's own readings.
[![Homebrew uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Homebrew down?", https://realuptime.io/outages/homebrew. The readings change with every check, so give the date you read them.

How our checks compare with Homebrew's stated SLA

At or above your target

Our checks of Homebrew failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, 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

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: formulae.brew.sh

RealUptime is not affiliated with Homebrew; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.