Degraded performance – Assistant and Flows using OpenAI models (Azure OpenAI, Sweden Central)
Last updateresolvedSep 29 · 19:34 UTC
This incident has been resolved
Reported by Jylo on their status page.
checked Oct 25, 2026 12:22 PM UTC · Jylo's official status page
Jylo is up and running.
Jylo is currently operational with all systems functioning normally.
All components operational
Be the first to know
Statusfield watches Jylo alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.
Jylo incident history
2 reports published by Jylo in the last 30 days · 1 still open
When Jylo breaks, it is typically resolved in 2h 28m — median across 1 resolved incidents over 30 days.
September 29, 2026
Degraded performance – Assistant and Flows using OpenAI models (Azure OpenAI, Sweden Central)
Ongoing · last updateUpdateSep 29 · 13:42 UTC
Status: InvestigatingMicrosoft has confirmed they detected the issue through automated monitoring, which showed an increase in failed requests, higher latency and HTTP 5XX errors from the Azure OpenAI Service in Sweden Central. They are still validating the root cause and are working on mitigation to restore full service.Assistant and Flows using OpenAI models remain degraded. Other model providers and core platform functions are unaffected. Where possible, switch to a non-OpenAI model until service is restored.Next update: Within 120 minutes, or sooner if the situation changes.
Reported by Jylo on their status page.