Developer Tools & CI/CDpackagist.org

Is Packagist (PHP Composer) Down Right Now?

Live global uptime status, multi-region edge latency, official incident reports, and automated monitoring for Packagist (PHP Composer).

P

Packagist (PHP Composer)

packagist.org

Main Composer repository for PHP packages and libraries.

Operational
Edge Latency
209 ms

Primary edge roundtrip

24h Global Uptime
99.98%

Edge consensus

Vantage Points
7 Regions

NA, EU, APAC Edge DOs

Last Checked
11:49:49 AM

Edge consensus mesh

Telemetry verified by SteadyStack Autonomous Edge Network
Official Status
Automated Developer Alerting

Stop checking manually.

When Packagist (PHP Composer) goes down or suffers silent latency degradation, you shouldn't be refreshing status pages, searching social feeds, or waiting for angry user reports. Get alerted the exact second Packagist (PHP Composer) fails.

Monitor Packagist (PHP Composer) in 1 Click

Free 50 monitors • 3m standard (1m for first 10) • 2-of-3 Edge Quorum • No credit card required

10-Second Edge Intervals

Continuous HTTP, WebSocket & DNS checks from 15+ global edge nodes.

4-of-7 Quorum Verification

Multi-region consensus verification prevents 3 AM wakeups from transient routing blips.

Multi-Channel Escalation

Instant alerts to Slack, Discord, Telegram, SMS, PagerDuty & Webhooks.

steadystack.config.ts
Auto-provisioned Monitor
import { defineMonitor } from "@steadystack/core";

export default defineMonitor({
  name: "Packagist (PHP Composer) API & Health",
  target: "https://packagist.org",
  interval: "10s",
  consensus: { requiredRegions: 3 },
  alerts: ["slack-dev-ops", "pagerduty-p1", "discord-incidents"],
});

Global Edge Reachability & Regional Latency

Synthetic probe response times tested from SteadyStack worldwide vantage points.

🇺🇸
US-East (N. Virginia)
us-east
105 ms
UP
🇺🇸
US-West (Oregon)
us-west
125 ms
UP
🇩🇪
EU-Central (Frankfurt)
eu-central
164 ms
UP
🇯🇵
AP-Tokyo (Tokyo)
ap-northeast
227 ms
UP
🇧🇷
SA-East (São Paulo)
sa-east
248 ms
UP
🇿🇦
AF-South (Cape Town)
af-south
292 ms
UP

Downtime Impact Analysis

What happens when Packagist (PHP Composer) degrades

composer install and composer update fail across PHP / Laravel deployments.

Common HTTP Error Codes Observed

500 Server Error504 Timeout

Critical Monitored Subsystems

Components tracked on packagist.org

Composer Metadata API
Synthetic Active
Package Web UI
Synthetic Active
GitHub Webhook Sync
Synthetic Active

Engineering Resilience Guide: Surviving Packagist (PHP Composer) Outages

Defensive software architecture patterns to prevent third-party cascade failures.

Immediate Tactical Steps

  • 1Check status.packagist.org.
  • 2Use Composer mirror.

Recommended Resiliency Patterns

Circuit Breaker Pattern: Automatically trip and fallback to cache when Packagist (PHP Composer) error rates exceed 15% in a 30s rolling window.

Idempotent Background Retries: Push failed API events into an asynchronous dead-letter queue with exponential backoff and jitter.

Multi-Region Edge Synthetic Consensus: Rely on SteadyStack to alert your team before end-users notice degradation.

Frequently Asked Questions: Packagist (PHP Composer) Availability & Monitoring

Everything you need to know about tracking Packagist (PHP Composer) outages and SLA reliability.

Our real-time global edge probes continuously test Packagist (PHP Composer) (packagist.org) across multiple worldwide locations. You can check the live status badge and latency meter at the top of this page. If you are seeing errors while the global status is operational, it may be due to localized ISP routing, local DNS caching, or account-specific rate limiting.
Related Developer Tools & CI/CD Dependencies