Archived edition ·
Blackout notice: Mastodon.social outage
Notice issued: Mastodon.social is down; a connectivity issue has been recorded and the relevant forms have become unexpectedly relevant.
Should you deploy right now?
Proceed carefully; verify dependencies before deployment.
Deployment inputs: no confirmed deployment incidents · no unconfirmed warnings.
Next few hours: Stripe maintenance for TWINT and Epic Games downtime for v43.00 Update remain in progress.
Excuse of the hour — Mastodon.social’s “Hetzner Connectivity Issues” may explain the delay; the route has been invited to submit a written apology.
Incident details →Days since last incident
All clear · 129 services
Dev
AI
Work
Consumer
Quiet · 37 community services with no reports
Forecast
Mastodon.social is down, with a connectivity issue recorded on its status notice, placing the social forecast in the black folder. Since the previous edition, Cursor has moved from clear to degraded, with its Billing and Usage Dashboard now under Service Degradation. Microsoft 365 lists Microsoft Admin Center as degraded, while Fireworks AI remains under a general service degradation notice. Plaid maintenance is in progress, and Stripe maintenance for TWINT is also in progress. Several status pages are not responding, which is less a forecast than an administrative gap in the forecast. Market mood is Fear, so the paperwork may be holding its breath. This bulletin is duly stamped and released.
Latest readings
- Fastly recovered: Osaka (ITM) with Possible Impact resolved after 6h
- Ideogram recovered: Outage on 3.0 resolved after 43m
- Ideogram API recovered: Outage on 3.0 resolved after 43m
- Coinbase recovered: Delayed Sends & Receives - DATA resolved after 33m
- Coinbase degraded: Delayed Sends & Receives - DATA
- Ideogram down: Outage on 3.0
- Ideogram API down: Outage on 3.0
- Fireworks AI incident resolved: Service Degradation for Muse Spark Open US resolved; 1 degraded incident remains
Warnings in effect
Avoid treating Mastodon.social as available; the outage has filed its own paperwork.
Advice for the day
Check affected services before pushing a change.
Keep a fallback for messages and dashboards.
Read incident titles, however much they resemble filing labels.
Leave the heroic deployment for clearer weather.