Updated Pingdom API

Status.io

Pingdom recently updated their API to version 3.1. This update is security focused and requires all current Pingdom metrics to be updated in your Status.io account.

Pingdom accounts are now connected using a read-only API token instead of the legacy username and password credentials.

To complete the update, your Pingdom API token must be added to each of your Status.io metrics. Please review our Knowledge Base article for instructions.

Tip: Connect multiple Pingdom accounts by using multiple API tokens.

If you do not perform this change before September 1st, your metrics will stop working.

Learn more about the Pingdom API improvements in Pingdom’s official announcement.

Version 1.4.3

Status.io

[Feature] (BETA) Added Vonage (previously Nexmo) as an alternate SMS gateway

[Improvement] Added self-serve functionality to disconnect a Twilio account and delete the Twilio number

[Improvement] Added setting for location maps to disable auto zoom on mouse scroll

[Improvement] Improved response messages for new subscriber signups

Version 1.4.2

Status.io

[Improvement] Add new Azure data center location (Madrid Spain)

[Improvement] Enhanced webhook notification payload to include start/stop timestamps

[Improvement] Improved handling of Pingdom monitoring alerts that are received out of order

[Fix] Display correct service dates on invoices for annual subscriptions

[Fix] Subscribers added via the Developer API with a blank granular array are subscribed to all components

[Fix] reCAPTCHA fixed for situations where webhook notifications were disabled

Version 1.4.1

Status.io

[Improvement] Add new AWS regions (Milan, Cape Town)

[Improvement] Decrease limit for Developer API methods: incident/list and maintenance/list (both methods will be deprecated in future versions)

[Fix] Fix team member view where using a tab can remove a team member

[Fix] Fix possible clickjacking vulnerability

[Fix] Fix history limits and sorting for main page history