Is IntelePeer down?

This is our latest update on PHP2Shell, the name widely used for two critical security flaws in PHP (CVE-2026-109618 and CVE-2026-109619). PHP is one of the most common programming languages for web applications. Details of the flaws were made public on October 20, earlier than planned, and the PHP development team released fixes the next day on October 21st. Where things stand today • Interim protections are in place for both vulnerabilities. Last night our engineering and operations teams updated the affected PHP components and hardened their configuration. These steps cut off the known attack methods while we finish the permanent fix. • No signs of exploitation. We have seen no indication that these vulnerabilities have been used against IntelePeer systems. We are monitoring the affected systems closely, and our teams are ready to respond right away if anything suspicious appears. • Additional access controls under review. We are evaluating more restrictions on who can reach the affected systems. Before we make any change, we are checking it against customer integrations so your service isn’t disrupted. If we need anything from you, we will reach out directly. The permanent fix The permanent fix is an upgrade to the latest patched PHP release. Our development team is completing the platform changes needed to support that upgrade, and each update will be tested for compatibility and stability before deployment. We expect to share a target completion date shortly and will update you as soon as we confirm it. Pointers for your own environment • Find any systems you run that use PHP, including third-party applications and appliances. • Apply the PHP project’s October 21 fixes, or your vendors’ patches, as soon as they’re available. • Until you can patch, limit access to affected systems where you can, and watch for unusual activity. If you have questions, please contact our support team at [email protected].

A fix has been implemented and we are monitoring the results.

Security update: PHP vulnerabilities (PHP2Shell) – October 23, 2026 This update follows our October 22 notice on PHP2Shell (CVE-2026-109618 and CVE-2026-109619). Since then we have added more protections to the IntelePeer Customer Portal and scheduled the permanent fix. What changed since our last update New protections are in place. Last night we turned on additional web security rules designed to block known PHP2Shell attack attempts. These sit on top of the protections we put in place earlier this week. Portal access is temporarily limited to known locations. To reduce exposure further, the Customer Portal now accepts connections only from internet (IP) addresses that have recently been used to access it. Connections from other addresses will see an access-denied page. No signs of exploitation. We still see no indication that these vulnerabilities have been used against IntelePeer systems, and we continue to monitor closely. If you can’t reach the portal If your team is blocked, please open a ticket with our support team at [email protected]. We apologize for the inconvenience. This restriction is temporary and will be removed once the permanent fix is in place. The permanent fix The upgrade to a patched PHP release is in final testing now. We will deploy it to production as soon as possible once testing is complete. We will confirm here once it’s deployed and the access restriction has been lifted. Pointers for your own environment Find any systems you run that use PHP, including third-party applications and appliances. Apply the PHP development team’s fixes, or your vendors’ patches, as soon as possible. Until you can patch, limit who can reach affected systems and watch for unusual activity. If you have questions, please contact [email protected].

As most of you are aware, we were impacted by an industry wide PHP vulnerability issue that affected thousands of websites and applications known as the PHP2Shell hack which allowed unauthenticated remote code execution and memory disclosure. Specifically for most of you, we locked down the portal and internal users can still get to the portal via VPN and we published status page alerts to notify customers and internal users to open a ticket and whitelist their IP’s for access. Later tonight, the portal team will be upgrading our PHP code version to mitigate this issue and all situation should normalize by then.

This incident has been resolved.

Intelepeer is investigating issues logging into its customer portal. We are aware of the issue and are investigating.

Intelepeer has mitigated the issue and is monitoring.

This issue has been resolved.

We are investigating an issue affecting some AI agents using an earlier version of the Azure-hosted GPT-4o model. Agents using newer versions are not currently known to be affected. We are working with Microsoft to resolve the issue and adjust routing to restore normal operation. We will provide updates as more information becomes available.

Service has been restored for the affected Azure-hosted GPT-4o model AI agents. We are monitoring performance and continue to work with Microsoft. We will provide further updates as more information becomes available.

Microsoft has corrected the issue affecting the impacted Azure-hosted LLM, and normal operation has been restored for the affected AI agents. This incident is now resolved.

Some customers may have experienced latency with inbound call transactions. Calls still completed but in some instances call delay could have exceeded 6secs.