Incidents reported on status page for Yield.xyz https://status.yield.xyz/ en https://status.yield.xyz/incident/965876 Thu, 16 Jul 2026 09:34:50 -0000 https://status.yield.xyz/incident/965876#c202cab2c5c051c5386b3a50c6bb17cf38f8d28df3ce7e20a866e0e5f0ee396e Resolved. The upstream Morpho API is available again and Borrow API requests for Morpho markets are returning normally. Follow-up: we are still rolling out a change to remove the Morpho API dependency on hot paths, expected live later today. https://status.yield.xyz/incident/965876 Thu, 16 Jul 2026 09:29:16 -0000 https://status.yield.xyz/incident/965876#f72a63b52c57c3bebfa5e7687c8588405078ff8dcc5d890abd6a29ce0f695e2b We are experiencing degraded performance on the Borrow API affecting Morpho markets. An upstream Morpho API dependency is currently down, causing errors when fetching Morpho Blue borrow positions. Our team is working on a solution to bypass this dependency on hot paths. Started: 08:14 UTC (Jul 16). https://status.yield.xyz/incident/948129 Thu, 09 Jul 2026 09:34:00 -0000 https://status.yield.xyz/incident/948129#073840663da42a0a48a9dca50b5b86009008858a3fd35a5da4b2e589bf9e4f7b We experienced elevated 5xx errors affecting some API requests. The issue has been mitigated and services are operating normally. We're actively investigating the root cause and will provide further updates as we learn more. https://status.yield.xyz/ Fri, 03 Jul 2026 16:32:00 +0000 https://status.yield.xyz/#6395124cc2d72735903e501f6d6090111b787928f75af3245a8f3e4096b106c8 Response time recovered https://status.yield.xyz/ Fri, 03 Jul 2026 16:30:00 +0000 https://status.yield.xyz/#6395124cc2d72735903e501f6d6090111b787928f75af3245a8f3e4096b106c8 Response time went down https://status.yield.xyz/ Fri, 03 Jul 2026 13:39:00 +0000 https://status.yield.xyz/#e803db7e05a9ef31504dc60f0829aaca864b51155270c3102d5e055974c11611 Response time recovered https://status.yield.xyz/ Fri, 03 Jul 2026 13:38:00 +0000 https://status.yield.xyz/#e803db7e05a9ef31504dc60f0829aaca864b51155270c3102d5e055974c11611 Response time went down https://status.yield.xyz/ Fri, 03 Jul 2026 12:03:00 +0000 https://status.yield.xyz/#2e1190e81af2fd3ccb78ae6565c3983e0ea563f6555e3e20fe4d2820abcc0d44 Availability recovered https://status.yield.xyz/ Fri, 03 Jul 2026 12:02:00 +0000 https://status.yield.xyz/#2e1190e81af2fd3ccb78ae6565c3983e0ea563f6555e3e20fe4d2820abcc0d44 Availability went down https://status.yield.xyz/ Fri, 03 Jul 2026 10:39:00 +0000 https://status.yield.xyz/#3fa1837bc39580b660f509b94307c886b288b8c11acd1f564ad01c6c27d66a5d Availability recovered https://status.yield.xyz/ Fri, 03 Jul 2026 10:37:00 +0000 https://status.yield.xyz/#3fa1837bc39580b660f509b94307c886b288b8c11acd1f564ad01c6c27d66a5d Availability went down https://status.yield.xyz/incident/898885 Mon, 25 May 2026 06:30:00 -0000 https://status.yield.xyz/incident/898885#0ae24800d3067288021b1cde71545d318c3f4c583ef21bcdbb91ba50f11dd5e6 Service Incident Postmortem Summary On May 19, 2026, between approximately 16:11 and 16:46 UTC, Yield API 2.0 and the Legacy API experienced elevated latency and an increased rate of request failures (HTTP 5xx errors) following a routine production deployment. Service was fully restored within roughly 35 minutes. We have not identified any failed customer write actions during the window. Impact - Window: ~16:11–16:46 UTC (approximately 35 minutes) - Affected services: Yield API 2.0, Legacy API - Symptoms: increased response times, intermittent request timeouts, and elevated 5xx errors - Synthetic monitoring probes timed out during the window; no customer write/POST operations were confirmed to have failed. Root cause The deployment included a routine database schema migration. That migration required a brief exclusive lock on a heavily-used table. Because the table was simultaneously serving a high volume of concurrent activity, the migration could not acquire the lock and instead created lock contention. This backed up queries and produced the timeouts and elevated error rates seen across both APIs. Resolution Our team opened incident response within minutes of the first alert. We canceled the in-progress release, rolled the deployment back across all regions, and cleared the contending database activity. Once contention was relieved, the migration completed near-instantly and all services recovered, with monitoring alerts auto-resolving by ~16:46 UTC. The release was subsequently re-applied successfully with the migration handled separately. Preventative actions Enforce a strict timeout on deployment-time database migrations so a blocked migration fails fast rather than holding locks. Move schema migrations into a dedicated, isolated release step instead of running them inline with application deployments. Fix automated rollback so a canceled release reverts without manual intervention. Expand monitoring coverage (database metrics and logs, deployment events) for faster detection and diagnosis. Strengthen incident-response and customer-notification procedures. We apologize for any disruption. If you have questions about how this incident may have affected your integration, please reach out to your Yield.xyz contact. https://status.yield.xyz/incident/903078 Fri, 22 May 2026 20:46:25 -0000 https://status.yield.xyz/incident/903078#d697790ff03ca7a7cab5c139b9e04b7a2175c7425f3af58eb09db49854b6a7e3 Service has fully recovered. Response times returned to normal at 20:08 UTC. Total incident duration ~14 minutes. https://status.yield.xyz/incident/903078 Fri, 22 May 2026 20:46:18 -0000 https://status.yield.xyz/incident/903078#a2845a0de1282c8952609f30e8f55aeb4b19664aea6f33d9a2395f0d91c50bc6 Between 19:54 and 20:08 UTC, the Yield API experienced elevated response times due to upstream RPC provider degradation. Some requests took 3–9 seconds to complete. The issue auto-resolved at 20:08 UTC and all services are operating normally. https://status.yield.xyz/incident/898885 Mon, 18 May 2026 16:35:00 -0000 https://status.yield.xyz/incident/898885#821b40d9e7255c7ce95a0600fa3f7e165d8a21da7088704dad7c260224d16c23 Error rates on our API have returned to normal. The incident was automatically resolved. Duration: 7 minutes. https://status.yield.xyz/incident/898885 Mon, 18 May 2026 16:28:00 -0000 https://status.yield.xyz/incident/898885#91e64f1a8f280bd6c1f9c8036835174be9d99938495a2ba5a0e3993979127701 We are investigating elevated error rates on our API. Some requests may experience failures or degraded performance. Our team is actively monitoring the situation. Started at 16:28 UTC.