Skip to content

Outage tracker / Packagist

Is Packagist down?

I'm having a problem

Operationalchecked 10 minutes ago

We reached Packagist from all 10 regions we check.

As of Oct 5, 2026, 8:07 PM UTC, Packagist answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

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

our independent probeslive · checked Oct 5, 2026, 8:07 PM UTC
US-East260 msOperational
US-West401 msOperational
Europe232 msOperational
Asia-Pacific509 msOperational
US-Central517 msOperational
Canada407 msOperational
UK166 msOperational
Southeast Asia330 msOperational
Australia462 msOperational
South America66 msOperational
their status pagetheir claim, not our reading

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

Packagist response time, by region

US-East
459msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 355ms2026-09-07 UTC: p95 206ms2026-09-08 UTC: p95 254ms2026-09-09 UTC: p95 270ms2026-09-10 UTC: p95 214ms2026-09-11 UTC: p95 257ms2026-09-12 UTC: p95 238ms2026-09-13 UTC: p95 264ms2026-09-14 UTC: p95 277ms2026-09-15 UTC: p95 261ms2026-09-16 UTC: p95 369ms2026-09-17 UTC: p95 314ms2026-09-18 UTC: p95 329ms2026-09-19 UTC: p95 346ms2026-09-20 UTC: p95 296ms2026-09-21 UTC: p95 315ms2026-09-22 UTC: p95 320ms2026-09-23 UTC: p95 292ms2026-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 459ms
Sep 6Sep 20Oct 5
US-West
535msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 462ms2026-09-07 UTC: p95 456ms2026-09-08 UTC: p95 425ms2026-09-09 UTC: p95 566ms2026-09-10 UTC: p95 423ms2026-09-11 UTC: p95 426ms2026-09-12 UTC: p95 410ms2026-09-13 UTC: p95 396ms2026-09-14 UTC: p95 380ms2026-09-15 UTC: p95 389ms2026-09-16 UTC: p95 412ms2026-09-17 UTC: p95 427ms2026-09-18 UTC: p95 438ms2026-09-19 UTC: p95 413ms2026-09-20 UTC: p95 415ms2026-09-21 UTC: p95 443ms2026-09-22 UTC: p95 448ms2026-09-23 UTC: p95 460ms2026-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 535ms
Sep 6Sep 20Oct 5
Europe
390msp95 · 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-06 UTC: p95 408ms2026-09-07 UTC: p95 326ms2026-09-08 UTC: p95 363ms2026-09-09 UTC: p95 341ms2026-09-10 UTC: p95 346ms2026-09-11 UTC: p95 365ms2026-09-12 UTC: p95 359ms2026-09-13 UTC: p95 353ms2026-09-14 UTC: p95 424ms2026-09-15 UTC: p95 440ms2026-09-16 UTC: p95 411ms2026-09-17 UTC: p95 395ms2026-09-18 UTC: p95 375ms2026-09-19 UTC: p95 399ms2026-09-20 UTC: p95 434ms2026-09-21 UTC: p95 389ms2026-09-22 UTC: p95 452ms2026-09-23 UTC: p95 396ms2026-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 390ms
Sep 6Sep 20Oct 5
Asia-Pacific
940msp95 · 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-09-06 UTC: p95 686ms2026-09-07 UTC: p95 915ms2026-09-08 UTC: p95 685ms2026-09-09 UTC: p95 512ms2026-09-10 UTC: p95 651ms2026-09-11 UTC: p95 686ms2026-09-12 UTC: p95 611ms2026-09-13 UTC: p95 517ms2026-09-14 UTC: p95 764ms2026-09-15 UTC: p95 689ms2026-09-16 UTC: p95 633ms2026-09-17 UTC: p95 822ms2026-09-18 UTC: p95 872ms2026-09-19 UTC: p95 642ms2026-09-20 UTC: p95 789ms2026-09-21 UTC: p95 737ms2026-09-22 UTC: p95 726ms2026-09-23 UTC: p95 701ms2026-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 940ms
Sep 6Sep 20Oct 5
US-Central
705msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 582ms2026-09-07 UTC: p95 578ms2026-09-08 UTC: p95 682ms2026-09-09 UTC: p95 584ms2026-09-10 UTC: p95 679ms2026-09-11 UTC: p95 660ms2026-09-12 UTC: p95 703ms2026-09-13 UTC: p95 687ms2026-09-14 UTC: p95 760ms2026-09-15 UTC: p95 570ms2026-09-16 UTC: p95 625ms2026-09-17 UTC: p95 720ms2026-09-18 UTC: p95 721ms2026-09-19 UTC: p95 634ms2026-09-20 UTC: p95 641ms2026-09-21 UTC: p95 828ms2026-09-22 UTC: p95 655ms2026-09-23 UTC: p95 928ms2026-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 705ms
Sep 6Sep 20Oct 5
Canada
766msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 579ms2026-09-07 UTC: p95 544ms2026-09-08 UTC: p95 557ms2026-09-09 UTC: p95 660ms2026-09-10 UTC: p95 618ms2026-09-11 UTC: p95 569ms2026-09-12 UTC: p95 607ms2026-09-13 UTC: p95 578ms2026-09-14 UTC: p95 625ms2026-09-15 UTC: p95 691ms2026-09-16 UTC: p95 547ms2026-09-17 UTC: p95 711ms2026-09-18 UTC: p95 603ms2026-09-19 UTC: p95 594ms2026-09-20 UTC: p95 581ms2026-09-21 UTC: p95 687ms2026-09-22 UTC: p95 640ms2026-09-23 UTC: p95 620ms2026-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 766ms
Sep 6Sep 20Oct 5
UK
243msp95 · 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-06 UTC: p95 103ms2026-09-07 UTC: p95 109ms2026-09-08 UTC: p95 171ms2026-09-09 UTC: p95 88ms2026-09-10 UTC: p95 88ms2026-09-11 UTC: p95 112ms2026-09-12 UTC: p95 95ms2026-09-13 UTC: p95 91ms2026-09-14 UTC: p95 118ms2026-09-15 UTC: p95 87ms2026-09-16 UTC: p95 203ms2026-09-17 UTC: p95 89ms2026-09-18 UTC: p95 133ms2026-09-19 UTC: p95 92ms2026-09-20 UTC: p95 91ms2026-09-21 UTC: p95 173ms2026-09-22 UTC: p95 156ms2026-09-23 UTC: p95 86ms2026-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 243ms
Sep 6Sep 20Oct 5
Southeast Asia
943msp95 · 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-06 UTC: p95 362ms2026-09-07 UTC: p95 363ms2026-09-08 UTC: p95 321ms2026-09-09 UTC: p95 418ms2026-09-10 UTC: p95 337ms2026-09-11 UTC: p95 975ms2026-09-12 UTC: p95 572ms2026-09-13 UTC: p95 615ms2026-09-14 UTC: p95 946ms2026-09-15 UTC: p95 563ms2026-09-16 UTC: p95 627ms2026-09-17 UTC: p95 702ms2026-09-18 UTC: p95 758ms2026-09-19 UTC: p95 626ms2026-09-20 UTC: p95 690ms2026-09-21 UTC: p95 828ms2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 852ms2026-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 943ms
Sep 6Sep 20Oct 5
Australia
791msp95 · 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-06 UTC: p95 937ms2026-09-07 UTC: p95 886ms2026-09-08 UTC: p95 876ms2026-09-09 UTC: p95 705ms2026-09-10 UTC: p95 650ms2026-09-11 UTC: p95 836ms2026-09-12 UTC: p95 984ms2026-09-13 UTC: p95 847ms2026-09-14 UTC: p95 828ms2026-09-15 UTC: p95 908ms2026-09-16 UTC: p95 770ms2026-09-17 UTC: p95 843ms2026-09-18 UTC: p95 942ms2026-09-19 UTC: p95 847ms2026-09-20 UTC: p95 924ms2026-09-21 UTC: p95 945ms2026-09-22 UTC: p95 857ms2026-09-23 UTC: p95 886ms2026-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 791ms
Sep 6Sep 20Oct 5
South America
256msp95 · 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-06 UTC: p95 267ms2026-09-07 UTC: p95 179ms2026-09-08 UTC: p95 265ms2026-09-09 UTC: p95 248ms2026-09-10 UTC: p95 330ms2026-09-11 UTC: p95 300ms2026-09-12 UTC: p95 145ms2026-09-13 UTC: p95 132ms2026-09-14 UTC: p95 341ms2026-09-15 UTC: p95 286ms2026-09-16 UTC: p95 128ms2026-09-17 UTC: p95 298ms2026-09-18 UTC: p95 237ms2026-09-19 UTC: p95 162ms2026-09-20 UTC: p95 155ms2026-09-21 UTC: p95 125ms2026-09-22 UTC: p95 174ms2026-09-23 UTC: p95 309ms2026-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 256ms
Sep 6Sep 20Oct 5

Is it Packagist, 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 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: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see Packagist go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Packagist, and again when they can reach it again. That is our own measurement from ten regions, not Packagist'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.

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: 260msstatus code: 200checked: Oct 5, 2026, 7:50 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
      Operationallatency: 401msstatus code: 200checked: Oct 5, 2026, 8:07 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
      Operationallatency: 517msstatus code: 200checked: Oct 5, 2026, 7:20 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
      Operationallatency: 407msstatus code: 200checked: Oct 5, 2026, 7:32 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
    Operationallatency: 66msstatus code: 200checked: Oct 5, 2026, 7:30 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 232msstatus code: 200checked: Oct 5, 2026, 7:51 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
      Operationallatency: 166msstatus code: 200checked: Oct 5, 2026, 7:53 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 509msstatus code: 200checked: Oct 5, 2026, 8:06 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
      Operationallatency: 330msstatus code: 200checked: Oct 5, 2026, 7:20 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
      Operationallatency: 462msstatus code: 200checked: Oct 5, 2026, 7:56 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 outages

No outages on record yet for Packagist.

measured 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 measurements and Packagist's own claim at the time, side by side.

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

Put this badge in your README

Packagist uptime measured by RealUptimeLive, from this page's own readings.
[![Packagist uptime measured by RealUptime](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 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 Packagist's SLA implies, from our measurement

At or above your target

We measured none of downtime for Packagist over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 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 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/
RealUptime is not affiliated with Packagist; the name identifies what we measured, 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 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.