Is api.video Down?
- api.video's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 369 ms
Right now
The verdict is the worse of these two. How we decide
api.video's status page
status.api.video · read · checked every 3 minutes
| Component | Status |
|---|---|
| Web services | Operational |
| Video Player | Operational |
| Video On Demand | Operational |
| User space | Operational |
| Live Streaming | Operational |
FlareWarden checks
api.video from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 369 ms
- Checked
By region
- Ashburn reachable, 306 ms
- Dallas reachable, 409 ms
- Frankfurt reachable, 231 ms
- Johannesburg reachable, 642 ms
- Newark reachable, 362 ms
- Paris reachable, 354 ms
- Stockholm reachable, 137 ms
- São Paulo reachable, 516 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Ashburn | 258 ms | 3 ms | 12 ms | 299 ms |
| Dallas | 288 ms | 1 ms | 53 ms | 384 ms |
| Frankfurt | 180 ms | 6 ms | 12 ms | 220 ms |
| Johannesburg | 455 ms | 1 ms | 78 ms | 606 ms |
| Newark | 281 ms | 10 ms | 17 ms | 343 ms |
| Paris | 64 ms | 9 ms | 16 ms | 313 ms |
| Stockholm | 98 ms | 1 ms | 10 ms | 130 ms |
| São Paulo | 339 ms | 1 ms | 6 ms | 511 ms |
History
Incidents api.video reported
Since Oct 29, 8 days · from status.api.video
- Incidents
- 0
- Major or critical
- 0
- Median to resolve
- —
No incidents reported in this window.
api.video website availability
Measured by FlareWarden · api.video
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 421ms
Last 30 days
8-day clean streakMeasured by FlareWarden's own checks of api.video from multiple regions every 6 hours. api.video's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 8 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What api.video does
api.video is a video API for developers: an app uploads a file or starts a live stream through the API, api.video encodes it and serves it through its own player or a player the developer builds. Software companies use it to put on-demand and live video inside their product without running encoding and delivery themselves, so an outage shows up inside someone else's app.
What an outage looks like
Uploads fail and new encoding jobs never start, while existing videos still play but slowly or with intermittent errors, as on October 7, 2026 when api.video's object storage at OVHcloud failed. Live streams buffer, drop or will not start (July 6 and 7). Database incidents slow the whole service (July 19), and the Analytics feature can stop returning data afterwards (July 20).
What to do about it
Check status.api.video, which reports Web services, Video Player, Video On Demand, User space and Live Streaming separately. During the October 7 storage incident api.video said existing videos were not affected and asked customers to retry any upload that failed once service returned, so queue retries rather than deleting and recreating videos. For live events, keep a backup stream destination ready if the event cannot slip.
Is it down for everyone, or just you?
If this page says api.video is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
api.video outage FAQ
Is api.video down for everyone or just my app?
Do existing videos stop playing during an api.video outage?
Does an OVHcloud outage affect api.video?
What happens to uploads that failed during the incident?
Does live streaming fail separately from on-demand video?
How we measure this
- We request api.video's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where api.video publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of api.video itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when api.video goes down
We check api.video every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring