Status
Availability of each Seedance model in the Seedancee workspace, read live from the same model table that drives the model picker (the page refreshes about once a minute), and the incident history as it is recorded. Nothing here is backfilled or estimated.
Current status comes from the live model table that drives the model picker, checked Oct 23, 2026, 8:33 AM UTC. This page refreshes about once a minute.
| Model | Provider | Status | Capabilities verified |
|---|---|---|---|
| Seedance 2.5bytedance/seedance-2-5 | Kie.ai | Operational | |
| Seedance 2.0bytedance/seedance-2 | Kie.ai | Operational | |
| Seedance 2.0 Fastbytedance/seedance-2-fast | Kie.ai | Operational | |
| Seedance 2.0 Minibytedance/seedance-2-mini | Kie.ai | Operational | |
| Seedance 1.5 Probytedance/seedance-1.5-pro | Kie.ai | Operational |
Incident history
No incidents recorded
Live incident history will appear here. Status changes are recorded when an administrator marks a model degraded or unavailable, or when provider errors cross our alert threshold. Nothing is backfilled or invented.
How status is determined
- Operational: the model is selectable and recent jobs complete normally.
- Degraded: jobs complete but with elevated failure rates or long waits; an administrator has flagged it, or automated checks saw repeated provider failures and marked it degraded until a job succeeds again.
- Unavailable: the model is hidden from the picker; jobs cannot be submitted.
- Deprecated: the provider or ByteDance has retired the model; existing outputs remain in your library.
Generation depends on our provider, Kie.ai, whose documented rate limit is 20 requests per 10 seconds. Provider-side outages show here as degraded or unavailable status on the affected models. Failed jobs never consume credits; reserved credits are released automatically. If you used a model in the last 30 days, a status change on it also reaches you as a notification in the dashboard and, unless you turned e-mail notifications off, by e-mail.
Where to look for more
Platform changes are listed on the changelog. If you see a failure that is not reflected here, email support@seedancee.com with the generation ID; we investigate and record incidents that affect more than one user.