Uptime.com incident
Vault items not resolving on select monitoring locations
Uptime.com experienced a minor incident on June 8, 2026, lasting 2d 1h. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Jun 08, 2026, 05:20 PM UTC
We are investigating an issue affecting checks using vault items on select monitoring locations recently updated as part of our Global Probe Server Expansion. Vault-backed values are not currently being resolved correctly on the affected locations. This may cause checks that rely on vault items, such as custom headers, credentials, or other check configuration fields, to fail incorrectly. The currently identified affected locations are: - Australia-Sydney - Chile-Santiago - Japan-Osaka - Japan-Tokyo - South Africa-Johannesburg - US-CA-Fremont Checks running from other monitoring locations are not currently known to be affected. As a temporary workaround, affected customers can select alternative monitoring locations where suitable. Our engineering team has identified the issue and is working on a fix. We will provide further updates as remediation progresses.
- identified Jun 09, 2026, 05:49 PM UTC
We have identified the issue affecting vault item resolution on select monitoring locations. A fix has been prepared and is pending deployment. Once deployed, checks using vault-backed values should resume working as expected from the affected locations. As a temporary workaround, affected customers can continue to use alternative monitoring locations where suitable. We will provide a further update once the fix has been deployed and validated.
- resolved Jun 10, 2026, 07:10 PM UTC
A fix has been deployed and validated. Checks using vault-backed values are now resolving correctly on the affected monitoring locations. We will continue to monitor for any further issues. Thank you for your patience while we worked to resolve this.