Skip to content

Outage tracker / Packagist

Is Packagist down?

I'm having a problem

Checks passingchecked 2 minutes ago

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

As of Oct 23, 2026, 5:39 PM UTC, RealUptime's checks of Packagist passed in all 10 regions that returned a reading.

Front-door and live API checks

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

our check readinglive · checked Oct 23, 2026, 5:39 PM UTC
US-East878 msChecks passing
US-West1318 msChecks passing
Europe556 msChecks passing
Asia-Pacific1578 msChecks passing
US-Central431 msChecks passing
Canada366 msChecks passing
UK54 msChecks passing
Southeast Asia452 msChecks passing
Australia2523 msChecks passing
South America785 msChecks passing
their status pagetheir claim, not our reading

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

Packagist 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-09-24 UTC: p95 547ms2026-09-25 UTC: p95 336ms2026-09-26 UTC: p95 356ms2026-09-27 UTC: p95 269ms2026-09-28 UTC: p95 456ms2026-09-29 UTC: p95 293ms2026-09-30 UTC: p95 333ms2026-10-01 UTC: p95 426ms2026-10-02 UTC: p95 344ms2026-10-03 UTC: p95 356ms2026-10-04 UTC: p95 377ms2026-10-05 UTC: p95 453ms2026-10-06 UTC: p95 389ms2026-10-07 UTC: p95 319ms2026-10-08 UTC: p95 375ms2026-10-09 UTC: p95 412ms2026-10-10 UTC: p95 445ms2026-10-11 UTC: p95 472ms2026-10-12 UTC: p95 356ms2026-10-13 UTC: p95 614ms2026-10-14 UTC: p95 392ms2026-10-15 UTC: p95 464ms2026-10-16 UTC: p95 493ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.2s
Sep 24Oct 8Oct 23
US-West
1.4sp95 · 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-09-24 UTC: p95 473ms2026-09-25 UTC: p95 502ms2026-09-26 UTC: p95 536ms2026-09-27 UTC: p95 451ms2026-09-28 UTC: p95 454ms2026-09-29 UTC: p95 412ms2026-09-30 UTC: p95 391ms2026-10-01 UTC: p95 400ms2026-10-02 UTC: p95 475ms2026-10-03 UTC: p95 493ms2026-10-04 UTC: p95 526ms2026-10-05 UTC: p95 534ms2026-10-06 UTC: p95 654ms2026-10-07 UTC: p95 593ms2026-10-08 UTC: p95 591ms2026-10-09 UTC: p95 605ms2026-10-10 UTC: p95 467ms2026-10-11 UTC: p95 531ms2026-10-12 UTC: p95 488ms2026-10-13 UTC: p95 566ms2026-10-14 UTC: p95 542ms2026-10-15 UTC: p95 513ms2026-10-16 UTC: p95 562ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.6s2026-10-23 UTC: p95 1.4s
Sep 24Oct 8Oct 23
Europe
821msp95 · 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-09-24 UTC: p95 505ms2026-09-25 UTC: p95 508ms2026-09-26 UTC: p95 511ms2026-09-27 UTC: p95 453ms2026-09-28 UTC: p95 619ms2026-09-29 UTC: p95 421ms2026-09-30 UTC: p95 408ms2026-10-01 UTC: p95 386ms2026-10-02 UTC: p95 450ms2026-10-03 UTC: p95 534ms2026-10-04 UTC: p95 422ms2026-10-05 UTC: p95 430ms2026-10-06 UTC: p95 437ms2026-10-07 UTC: p95 390ms2026-10-08 UTC: p95 366ms2026-10-09 UTC: p95 334ms2026-10-10 UTC: p95 343ms2026-10-11 UTC: p95 302ms2026-10-12 UTC: p95 320ms2026-10-13 UTC: p95 329ms2026-10-14 UTC: p95 316ms2026-10-15 UTC: p95 307ms2026-10-16 UTC: p95 282ms2026-10-17 UTC: p95 441ms2026-10-18 UTC: p95 650ms2026-10-19 UTC: p95 802ms2026-10-20 UTC: p95 581ms2026-10-21 UTC: p95 791ms2026-10-22 UTC: p95 779ms2026-10-23 UTC: p95 821ms
Sep 24Oct 8Oct 23
Asia-Pacific
2.3sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 726ms2026-09-25 UTC: p95 792ms2026-09-26 UTC: p95 816ms2026-09-27 UTC: p95 713ms2026-09-28 UTC: p95 818ms2026-09-29 UTC: p95 589ms2026-09-30 UTC: p95 626ms2026-10-01 UTC: p95 945ms2026-10-02 UTC: p95 939ms2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 953ms2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 929ms2026-10-09 UTC: p95 975ms2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 976ms2026-10-12 UTC: p95 934ms2026-10-13 UTC: p95 966ms2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.2s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 2.3s2026-10-21 UTC: p95 2.2s2026-10-22 UTC: p95 2.2s2026-10-23 UTC: p95 2.3s
Sep 24Oct 8Oct 23
US-Central
782msp95 · 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-24 UTC: p95 664ms2026-09-25 UTC: p95 673ms2026-09-26 UTC: p95 781ms2026-09-27 UTC: p95 810ms2026-09-28 UTC: p95 612ms2026-09-29 UTC: p95 621ms2026-09-30 UTC: p95 790ms2026-10-01 UTC: p95 854ms2026-10-02 UTC: p95 802ms2026-10-03 UTC: p95 936ms2026-10-04 UTC: p95 945ms2026-10-05 UTC: p95 781ms2026-10-06 UTC: p95 829ms2026-10-07 UTC: p95 795ms2026-10-08 UTC: p95 728ms2026-10-09 UTC: p95 671ms2026-10-10 UTC: p95 754ms2026-10-11 UTC: p95 789ms2026-10-12 UTC: p95 824ms2026-10-13 UTC: p95 788ms2026-10-14 UTC: p95 776ms2026-10-15 UTC: p95 934ms2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 736ms2026-10-18 UTC: p95 689ms2026-10-19 UTC: p95 777ms2026-10-20 UTC: p95 720ms2026-10-21 UTC: p95 745ms2026-10-22 UTC: p95 744ms2026-10-23 UTC: p95 782ms
Sep 24Oct 8Oct 23
Canada
705msp95 · 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-24 UTC: p95 569ms2026-09-25 UTC: p95 698ms2026-09-26 UTC: p95 646ms2026-09-27 UTC: p95 614ms2026-09-28 UTC: p95 585ms2026-09-29 UTC: p95 601ms2026-09-30 UTC: p95 773ms2026-10-01 UTC: p95 818ms2026-10-02 UTC: p95 841ms2026-10-03 UTC: p95 732ms2026-10-04 UTC: p95 745ms2026-10-05 UTC: p95 781ms2026-10-06 UTC: p95 897ms2026-10-07 UTC: p95 766ms2026-10-08 UTC: p95 764ms2026-10-09 UTC: p95 756ms2026-10-10 UTC: p95 646ms2026-10-11 UTC: p95 710ms2026-10-12 UTC: p95 730ms2026-10-13 UTC: p95 753ms2026-10-14 UTC: p95 657ms2026-10-15 UTC: p95 863ms2026-10-16 UTC: p95 688ms2026-10-17 UTC: p95 686ms2026-10-18 UTC: p95 805ms2026-10-19 UTC: p95 686ms2026-10-20 UTC: p95 890ms2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 761ms2026-10-23 UTC: p95 705ms
Sep 24Oct 8Oct 23
UK
88msp95 · latest
500ms250ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 110ms2026-09-25 UTC: p95 95ms2026-09-26 UTC: p95 90ms2026-09-27 UTC: p95 97ms2026-09-28 UTC: p95 260ms2026-09-29 UTC: p95 96ms2026-09-30 UTC: p95 118ms2026-10-01 UTC: p95 192ms2026-10-02 UTC: p95 148ms2026-10-03 UTC: p95 108ms2026-10-04 UTC: p95 150ms2026-10-05 UTC: p95 277ms2026-10-06 UTC: p95 317ms2026-10-07 UTC: p95 109ms2026-10-08 UTC: p95 93ms2026-10-09 UTC: p95 150ms2026-10-10 UTC: p95 104ms2026-10-11 UTC: p95 97ms2026-10-12 UTC: p95 153ms2026-10-13 UTC: p95 170ms2026-10-14 UTC: p95 97ms2026-10-15 UTC: p95 100ms2026-10-16 UTC: p95 298ms2026-10-17 UTC: p95 129ms2026-10-18 UTC: p95 133ms2026-10-19 UTC: p95 139ms2026-10-20 UTC: p95 269ms2026-10-21 UTC: p95 208ms2026-10-22 UTC: p95 406ms2026-10-23 UTC: p95 88ms
Sep 24Oct 8Oct 23
Southeast Asia
754msp95 · 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-24 UTC: p95 826ms2026-09-25 UTC: p95 755ms2026-09-26 UTC: p95 768ms2026-09-27 UTC: p95 733ms2026-09-28 UTC: p95 837ms2026-09-29 UTC: p95 695ms2026-09-30 UTC: p95 666ms2026-10-01 UTC: p95 722ms2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 897ms2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 834ms2026-10-07 UTC: p95 810ms2026-10-08 UTC: p95 815ms2026-10-09 UTC: p95 803ms2026-10-10 UTC: p95 753ms2026-10-11 UTC: p95 821ms2026-10-12 UTC: p95 756ms2026-10-13 UTC: p95 750ms2026-10-14 UTC: p95 806ms2026-10-15 UTC: p95 753ms2026-10-16 UTC: p95 832ms2026-10-17 UTC: p95 772ms2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 873ms2026-10-22 UTC: p95 1s2026-10-23 UTC: p95 754ms
Sep 24Oct 8Oct 23
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-09-24 UTC: p95 837ms2026-09-25 UTC: p95 971ms2026-09-26 UTC: p95 827ms2026-09-27 UTC: p95 912ms2026-09-28 UTC: p95 864ms2026-09-29 UTC: p95 873ms2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.7s2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 763ms2026-10-06 UTC: p95 674ms2026-10-07 UTC: p95 716ms2026-10-08 UTC: p95 756ms2026-10-09 UTC: p95 720ms2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 993ms2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 2.2s2026-10-18 UTC: p95 2.8s2026-10-19 UTC: p95 2.9s2026-10-20 UTC: p95 2.8s2026-10-21 UTC: p95 2.6s2026-10-22 UTC: p95 2.7s2026-10-23 UTC: p95 2.7s
Sep 24Oct 8Oct 23
South America
1.6sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 131ms2026-09-25 UTC: p95 517ms2026-09-26 UTC: p95 458ms2026-09-27 UTC: p95 442ms2026-09-28 UTC: p95 547ms2026-09-29 UTC: p95 368ms2026-09-30 UTC: p95 304ms2026-10-01 UTC: p95 288ms2026-10-02 UTC: p95 140ms2026-10-03 UTC: p95 212ms2026-10-04 UTC: p95 620ms2026-10-05 UTC: p95 242ms2026-10-06 UTC: p95 422ms2026-10-07 UTC: p95 561ms2026-10-08 UTC: p95 332ms2026-10-09 UTC: p95 310ms2026-10-10 UTC: p95 818ms2026-10-11 UTC: p95 675ms2026-10-12 UTC: p95 887ms2026-10-13 UTC: p95 808ms2026-10-14 UTC: p95 850ms2026-10-15 UTC: p95 790ms2026-10-16 UTC: p95 982ms2026-10-17 UTC: p95 687ms2026-10-18 UTC: p95 740ms2026-10-19 UTC: p95 623ms2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 1.8s2026-10-23 UTC: p95 1.6s
Sep 24Oct 8Oct 23

Check your own site while you wait on Packagist

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 Packagist. It cannot diagnose Packagist's own systems.

What we measured, function by function

Packagist answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Get an email when our checks of Packagist 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 Packagist 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 Packagist'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: 878msstatus code: 200checked: Oct 23, 2026, 5:22 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Packagist normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1318msstatus code: 200checked: Oct 23, 2026, 5:27 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Packagist normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 431msstatus code: 200checked: Oct 23, 2026, 5:25 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Packagist normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 366msstatus code: 200checked: Oct 23, 2026, 5:39 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Packagist normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 785msstatus code: 200checked: Oct 23, 2026, 4:53 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Packagist 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: 556msstatus code: 200checked: Oct 23, 2026, 5:20 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Packagist normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 54msstatus code: 200checked: Oct 23, 2026, 5:02 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Packagist 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: 1578msstatus code: 200checked: Oct 23, 2026, 5:37 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Packagist normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 452msstatus code: 200checked: Oct 23, 2026, 5:27 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Packagist normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 2523msstatus code: 200checked: Oct 23, 2026, 5:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Packagist 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 Packagist, 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 Packagist yet, which is not evidence that nothing is wrong.

Recent probe events

No probe events on record yet for Packagist.

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

We have been measuring Packagist 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 Packagist covering any window you pick, with our check readings and Packagist's own claim at the time, side by side.

Full check history for Packagist: 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

Put this badge in your README

Packagist uptime by RealUptime's checksLive, from this page's own readings.
[![Packagist uptime by RealUptime's checks](https://realuptime.io/outages/packagist/badge.svg?days=30)](https://realuptime.io/outages/packagist)
<a href="https://realuptime.io/outages/packagist"><img src="https://realuptime.io/outages/packagist/badge.svg?days=30" alt="Packagist uptime by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

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

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

How our checks compare with Packagist's stated SLA

At or above your target

Our checks of Packagist 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 Packagist'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://repo.packagist.org/p2/monolog/monolog.json
secondary
https://packagist.org/

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: repo.packagist.org

RealUptime is not affiliated with Packagist; the name identifies what we checked, and nothing here speaks for Packagist's own team. We send a single web request to Packagist from 10 regions on our own schedule and time the response. We do not see inside Packagist's systems, do not use an account or real transaction, and are not the same signal Packagist's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Packagist 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.