CHYP.ai · ORBIT // Cloudy_Day Security Suite

Hosting & PaaS

Operational Pantheon status

pantheon.io · Official status page (Statuspage-compatible JSON)

FROM ALL SOURCES

No sign of a widespread Pantheon problem right now; every source we read is quiet.

confidence: medium Vendor: operational · users: normal · routing: no data.

Vendor status vs. reality: Vendor status and outside signals roughly agree

Regions mentioned: Customer Sites

The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started31 days
Crowd clock when user reports began rising above normalnot seenn/a
Network clock when routing anomaly data first flagged itnot seenn/a
ORBIT clock when our checker first recorded the changenot seenn/a

Evidence

  • Official page: Operational (“All Systems Operational”). evidence confidence: high
  • Vendor stage: resolved on “PHP Vulnerabilities CVE-2026-109618 and CVE-2026-109619”. evidence confidence: high
  • User reports are within normal range (0 in 15 min). evidence confidence: low

What we don't know: what is happening inside Pantheon's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .

Cloudy_Day's take

Stage vs. health

The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.

Who depends on whom

We don't map other services that depend on Pantheon. Dependency chains are where single points of failure hide.

Identity & trust lens

Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.

For users

Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.

For security teams

Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Pantheon, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).

What to watch next

Any new vendor incident, a jump in user reports above baseline, or trouble at the providers Pantheon may depend on.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Pantheon. No blame or attack claims without an official source. Generated .

INCIDENT REPLAY

PHP Vulnerabilities CVE-2026-109618 and CVE-2026-109619

none resolved · started · resolved

13 updates

  1. investigating

    Pantheon is actively mitigating against the PHP security vulnerabilities announced at 14:00 UTC today. PHP environments are being patched to the following versions: 8.5.12 8.4.27 8.3.36 8.2.35 Additionally, we are patching the following heirloom PHP branches via our LTS vendor: 8.1.x 8.0.x 7.4.x 7.3.x 7.2.x 7.1.x 7.0.x 5.6.x Finally, in preparation for this event, we pre-emptively deployed configuration changes to the runtime environment to mitigate potential attack vectors, and have implemented network-level mitigations to deflect attempted exploit payloads across the platform. No action is required from customers, as all available versions of PHP on Pantheon receive security updates through our LTS vendor. However, we continue to recommend that customers running on older versions of PHP that have reached End of Sale update to a version fully supported by the PHP community in order to m

  2. investigating

    Updated PHP versions addressing CVE-2026-109618 and CVE-2026-109619 are now available, and we are beginning the process of rolling them out across our infrastructure. No action is required from customers. We will continue to update this post as the rollout progresses.

  3. investigating

    Patching work is still in progress. Environments are being updated in stages, and protective mitigations remain active across the platform while the remaining updates complete. We are not yet seeing evidence of any volumetric exploit attempts. No customer action is needed. We will provide further updates as the rollout progresses.

  4. investigating

    Patches continue rolling out across the infrastructure in stages, and protective mitigations remain active. We have not observed any volumetric exploit attempts, and no customer action is required.

  5. identified

    Patching continues to roll out across the infrastructure in stages, with protective mitigations remaining active. We have not observed any volumetric exploit attempts, and no customer action is required. We expect to provide an estimated completion time for the patching rollout within the next hour.

  6. identified

    We estimate the complete rollout for live environments on supported PHP versions (8.2 -> 8.5) within the next 20 minutes. We are also prioritizing pre-production environments for paying customers, and have preemptively patched development or mutli-dev environments that were toggled into a mutable code state (“SFTP mode”). We will provide an update on LTS versions of PHP (8.1.x through 5.6.x) once our upstream vendor has backported the patches and made updates available. That work has been in progress since 14:00 UTC. Our network-level mitigations remain effective, and are blocking a low but slowly increasing level of activity which is probing the vulnerable surface area. At this time we do not see evidence of widespread exploitation attempts, or any successful exploits. We will continue to deliver patched versions of PHP as quickly as possible, and maintain network level mitigation and c

  7. identified

    We have patched all live production sites running supported PHP versions (8.2 - 8.5).

  8. identified

    We have received LTS updates from our upstream vendor and are working to deploy the patch to older versions of PHP. We will post an update on that once it is complete or we have a clear ETA. Our network-level mitigations remain effective and we see no evidence of compromise for any sites on the platform.

  9. identified

    Patched PHP builds are now available for all supported long-term support (LTS) PHP versions, and rollout to live environments running end-of-life PHP versions is underway. Live environments running fully supported PHP versions (8.2 and later) have already been patched.

  10. identified

    We have completed patching production environments for all sites running LTS versions of PHP.

  11. identified

    Patched PHP builds have been deployed to all LTS environments, all environments in SFTP mode, and all live environments running PHP 8.2 or later. Most paid non-live environments running PHP 8.2 or later are also patched. We expect the remaining rollout to continue over the next 24 to 48 hours.

  12. monitoring

    We can now confirm that all pre-production customer environments are patched. Free/sandbox environments will be updated over the next 24-48 hours. Over the course of today, our network-level mitigations have blocked over 60,000 suspicious requests probing the vulnerability, and remain in place. This concludes our ongoing updates. We will share more analysis in the future based on what we can observe, but as of now, active mitigation work is complete.

  13. resolved

    Overnight monitoring continues to show persistent but limited probing, which is being blocked. Our rollout of updated PHP images across customer environments including LTS versions was complete as of 5pm Pacific time yesterday. We will continue to observe and may provide further analysis of our findings, but we are closing this incident.

Official incident page ↗

Community comments (0)

Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.

No approved comments yet.

How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.

Where to next