PROS incident

Production | Degraded performance | May 07, 2026

Notice Ongoing View vendor source →

PROS is currently experiencing a notice incident affecting EU4 and EU4, which began 2h ago. The vendor's full update timeline is below.

Started
May 07, 2026, 02:45 PM UTC
Resolved
Ongoing
Duration
● 1h 52m
Detected by Pingoru
May 07, 2026, 02:45 PM UTC

Affected components

EU4EU4

Update timeline

  1. investigating May 07, 2026, 02:45 PM UTC

    Dear partners, We managed to shift a portion of the affected traffic to the alternative locations and were able to mitigate impact for some of our partners. The remaining transfer efforts continue. In parallel, we are assessing the capabilities of our hosting provider to provision the required resources to fully resolve the situation and exploring alternative options depending on their readiness. Individual partners where we believe the issue has been resolved will be contacted directly. Kindly expect a progress update in the next 30-60 minutes. Sincerely, PROS Support

  2. investigating May 07, 2026, 04:03 PM UTC

    Dear partners, We successfully restored part of the affected traffic with additional resources in our alternative region. We are working with our cloud provider to procure the full capacity needed to restore the service in full . The available compute resources will not be sufficient to deliver 100% of the usual service performance; however, it will be sufficient to bring back the service in a reduced capacity, while we await a permanent solution. We have filed the necessary requisitions for a significant increase of the compute resources; however, they will be able to provide this in a matter of days. Based on the provisioning speed of the cloud provider so far, we are looking at 6-12 hours in which all services should be restored with limited capacity. The process itself will consist of loops of: Configure compute resources Shift a portion of the traffic Assure traffic volumes are manageable and existing operational service is not degrading Performance, while not optimal is sufficient Proceed with the next "batch" We will continue to provide regular updates on our progress or in case there are changes. Sincerely, PROS Support

  3. investigating May 07, 2026, 04:09 PM UTC

    Dear partners, We successfully restored part of the affected traffic with additional resources in our alternative region. We are working with our cloud provider to procure the full capacity needed to restore the service in full . The available compute resources will not be sufficient to deliver 100% of the usual service performance; however, it will be sufficient to bring back the service in a reduced capacity, while we await a permanent solution. We have filed the necessary requisitions for a significant increase of the compute resources; however, they will be able to provide this in a matter of days. Based on the provisioning speed of the cloud provider so far, we are looking at 6-12 hours in which all services should be restored with limited capacity. The process itself will consist of loops of: Configure compute resources Shift a portion of the traffic Assure traffic volumes are manageable and existing operational service is not degrading Performance, while not optimal is sufficient Proceed with the next "batch" We will continue to provide regular updates on our progress or in case there are changes. Sincerely, PROS Support

  4. investigating May 07, 2026, 04:12 PM UTC

    Dear partners, We successfully restored part of the affected traffic with additional resources in our alternative region. We are working with our cloud provider to procure the full capacity needed to restore the service in full. The available compute resources will not be sufficient to deliver 100% of the usual service performance; however, it will be sufficient to bring back the service in a reduced capacity, while we await a permanent solution. We have filed the necessary requisitions for a significant increase of the compute resources; however, they will be able to provide this in a matter of days. Based on the provisioning speed of the cloud provider so far, we are looking at 6-12 hours in which all services should be restored with limited capacity. The process itself will consist of loops of: Configure compute resources Shift a portion of the traffic Assure traffic volumes are manageable and existing operational service is not degrading Performance, while not optimal is sufficient Proceed with the next "batch" We will continue to provide regular updates on our progress or in case there are changes. Sincerely, PROS Support

Looking to track PROS downtime and outages?

Pingoru polls PROS's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when PROS reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track PROS alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring PROS for free

5 free monitors · No credit card required