AI service incidents · Daily incidents

AI incidents: Fireworks GLM 5.3 disruptions and Microsoft 365 recovery — 15 November 2026

Fireworks closed three GLM 5.3 inference incidents. Microsoft confirmed full restoration for remaining Microsoft 365 customers and regions.

Publisher disclosure: MUVO offers competing music, remix, and video tools. This report summarizes public sources and provider documentation; it is not an independent product test or a claim that MUVO is free of similar issues. Read our reporting method.

Fireworks resolved three GLM 5.3 inference incidents

Fireworks reported degraded performance twice on hosted GLM 5.3 and once on GLM 5.3 Flash. It marked all three incidents resolved by 06:13 Istanbul on 15 November. These notices apply to the named Fireworks endpoints. The notices give no root cause.

Fireworks endpoint Reported degradation began Marked resolved Approximate interval
GLM 5.3 14 Nov 15:42 14 Nov 15:56 14 minutes
GLM 5.3 Flash 14 Nov 16:37 14 Nov 18:02 1 hour 25 minutes
GLM 5.3 15 Nov 05:30 15 Nov 06:13 43 minutes

The intervals use Fireworks’ component start and end timestamps. Times are Istanbul (UTC+3). Fireworks did not publish an error rate or give a breakdown of affected requests. The Flash incident on 14 November has its own incident ID, separate from the Flash degradation recorded the previous evening.

Scheduled serverless maintenance ended at 03:27 Istanbul

Fireworks began network maintenance with a North American infrastructure provider at 03:00 on 15 November and reported serverless traffic back to normal at 03:27. During maintenance, it warned that some requests could see errors, higher latency or timeouts and recommended retrying failed requests with exponential backoff. The 27 minutes describe the maintenance window through completion. Fireworks did not give a measured period of elevated errors. Fireworks maintenance notice.

Microsoft confirmed restoration for remaining customers and regions

Microsoft’s public update on 14 November said it had restored service to the remaining customers and regions affected by Microsoft 365 incident MO1550821, which included Exchange-dependent Copilot features. The earlier tenant update at 07:17 Istanbul said the underlying issue had been addressed while some restoration work continued. The public update gave no separate timestamp for when the last affected service recovered. Microsoft statement reproduced by Digital Trends · Associated Press report.

The current tenant record lists a formal impact interval of 13:05 Istanbul on 12 November to 19:10 on 13 November. That recorded end and the later service-restoration announcements describe different milestones. The 13 November report now reflects the tenant record’s revised end time. The 14 November report includes Microsoft’s full-restoration statement. Microsoft tenant record reproduced by Penn IT.

Claude iOS sign-up and OpenAI cost reporting remained open

Update, 16 November: OpenAI reported the affected service operating normally at 03:17 Istanbul. This was the resolution of the organization cost-data delay. OpenAI incident notice · 16 November incident roundup.

Sources

The Fireworks incident archive, Microsoft tenant record reproduced by Penn IT, Claude status history and OpenAI incident history provide the incident records. Public reviews did not yield corroborated customer allegations for this edition. Some review platforms restricted access. Reporting methodology.

Update timeline