Issue creating new Pingdom automations

Uptime Impact: 23 hours, 24 minutes, and 31 seconds
Resolved
Resolved

We have completed testing the new functionality using the latest Pingdom API, and all tests passed. We have now deployed this to production.

Customers are now able to configure new Pingdom automation using an API key.

Click here for a helpful guide on setting up Sorry™ with Pingdom.

Avatar for Nic Coates
Nic Coates
Updated

Thanks for your patience with this issue. We continue working on a permanent fix and have completed the development tasks needed to move to the latest API version.

It is now in QA, so we can test it before deploying it to production. Once QA has passed, we will deploy this and update this notice.

Avatar for Nic Coates
Nic Coates
Identified

We have identified an issue with our Pingdom Integration. For customers who create or configure a new Pingdom integration via monitoring automation, an error is presented stating the credentials need to be corrected.

The issue is caused by Sorry™ using an older version of the Pingdom API, which requires a username and password. Pingdom no longer accepts this form of authentication.

We are changing the integration setup to use a newer version of the API, which will require an API key and allow customers to continue setting up the integration.

Note that most existing Pingdom integrations are still working; however, we advise only making configuration changes once we have implemented the new API.

Please standby for further updates.

Avatar for Nic Coates
Nic Coates
Began at:

Affected components
  • Monitoring Automation
    • Pingdom Sync