Is PHP down? User reports show no current problems with PHP

Is PHP Down Right Now?

PHP is the server language behind WordPress and a large share of the web. A PHP status check spans several parts: php.net for downloads and news, Packagist for packages, and your own server runtime. Each can break on its own. This page tracks the PHP problems users and developers report.

Composer installs pull from Packagist on nearly every deploy. When Packagist has an incident, builds and deploys fail together worldwide. Version upgrades cause the other big wave of reports. Sites built for an old PHP version often break on a newer one.

Is PHP Down for Me or Everyone?

Review the reports above before digging through your server. If Composer failures spike across teams, Packagist is likely struggling. Packagist shares incident notes on its own site and social channels. If reports are calm, your code or server config holds the issue. A white page with errors hidden is the classic local case. Deploy teams tend to call that pattern a PHP outage.

Why Can’t Composer Reach Packagist?

Packagist serves the metadata and downloads for almost every PHP package. During incidents, Composer stalls or errors on every project at once. These events are rare but very visible. Retrying after recovery works, since the metadata cache refreshes itself.

Server networks cause private versions of this failure. Firewalls can block outbound package downloads from your host. Then Composer works on your laptop but not in production. Testing the same install command locally isolates the network quickly.

Why Did My Site Break After a PHP Upgrade?

Each PHP version removes old features and tightens rules. Hosts often upgrade PHP on a schedule with little warning. Code written for the old version can then throw fatal errors. Removed functions and changed defaults lead the list of breakage.

The fix path starts with the error log. The first fatal error names a file and line. Updating the offending library or theme usually clears many errors at once. Checking library support for your new PHP version matters before you upgrade.

Why Do I See a Blank White Page?

The famous white screen usually means a fatal error with display turned off. Production servers hide errors on purpose for security. The error still lands in the server’s PHP error log. That log line is your real starting point, not the blank page.

Memory limits trigger white pages too. A heavy page can blow past the allowed memory and die silently. The log shows the allowed memory size message in that case. Raising the limit or cutting the heavy work both help.

Common PHP Problems and Fixes

Composer downloads time out

Composer downloads time out: Check whether Packagist reports an incident before changing anything. Clear the Composer cache and retry the install. On hosted servers, confirm outbound connections to Packagist are allowed. A blocked firewall shows up as endless timeouts on every package.

Allowed memory size exhausted

Allowed memory size exhausted: Read how big the limit is in the error message. Raise the PHP memory limit in your config if the work is truly heavy. Also check for runaway loops or giant queries in the named file. Memory errors often point at one bad query.

Deprecated warnings flood the logs

Deprecated warnings flood the logs: Deprecation notices warn about code the next PHP version will reject. Update the library or code that triggers them. Hiding warnings without fixing the cause only delays the breakage. Track which plugin or file repeats most and fix that first.

Extensions missing on the server

Extensions missing on the server: Name the missing extension from the error text. Common needs are mbstring, intl, and the database drivers. Install the extension through your host panel or package manager. Then restart PHP so the new extension loads.

php.net will not load

php.net will not load: The manual and download site can slow during big release days. Try again later or use your local PHP docs copy. Many editors bundle the manual for offline reading. If only your network fails, test from a second connection.