Skip to main content
api.video logo

Is api.video Down?

No — api.video is up
api.video's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 265 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

Operational
api.video's components, as its status page reports them
ComponentStatus
Web servicesOperational
Video PlayerOperational
Video On DemandOperational
User spaceOperational
Live StreamingOperational

FlareWarden checks

api.video from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
265 ms
Checked

By region

  • Amsterdam reachable, 113 ms
  • Dallas reachable, 475 ms
  • Frankfurt reachable, 84 ms
  • Newark reachable, 279 ms
  • Paris reachable, 210 ms
  • Stockholm reachable, 262 ms
  • São Paulo reachable, 339 ms
  • Toronto reachable, 362 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Amsterdam37 ms5 ms19 ms100 ms
Dallas298 ms25 ms29 ms399 ms
Frankfurt42 ms2 ms7 ms75 ms
Newark201 ms3 ms19 ms267 ms
Paris136 ms9 ms19 ms190 ms
Stockholm205 ms1 ms18 ms257 ms
São Paulo308 ms1 ms8 ms330 ms
Toronto237 ms11 ms29 ms327 ms
We check that api.video loads, not every feature behind it. Test it yourself

History

Incidents api.video reported

Since Oct 29, 21 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
418ms

Last 30 days

21-day clean streak
Oct 20: no data
Oct 21: no data
Oct 22: no data
Oct 23: no data
Oct 24: no data
Oct 25: no data
Oct 26: no data
Oct 27: no data
Oct 28: no data
Oct 29: 100.00% uptime, 14 checks
Oct 30: 100.00% uptime, 32 checks
Oct 31: 100.00% uptime, 31 checks
Nov 1: 100.00% uptime, 32 checks
Nov 2: 100.00% uptime, 31 checks
Nov 3: 100.00% uptime, 31 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 32 checks
Nov 6: 100.00% uptime, 32 checks
Nov 7: 100.00% uptime, 31 checks
Nov 8: 100.00% uptime, 32 checks
Nov 9: 100.00% uptime, 32 checks
Nov 10: 100.00% uptime, 32 checks
Nov 11: 100.00% uptime, 32 checks
Nov 12: 100.00% uptime, 32 checks
Nov 13: 100.00% uptime, 32 checks
Nov 14: 100.00% uptime, 32 checks
Nov 15: 100.00% uptime, 30 checks
Nov 16: 100.00% uptime, 32 checks
Nov 17: 100.00% uptime, 32 checks
Nov 18: 100.00% uptime, 8 checks
Oct 20 Today
No downtime Partial Downtime Not measurable No data

Measured 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 — 21 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.

Test it yourself

Related services

api.video outage FAQ

Is api.video down for everyone or just my app?
Compare the region table on this page with status.api.video. If both show api.video healthy, the failure is more likely in your integration: an expired API key, a quota, or your own server timing out on uploads. api.video's incidents usually name the part affected, such as ingest, delivery or live streaming, which tells you whether your symptom matches.
Do existing videos stop playing during an api.video outage?
Not usually. In the October 7, 2026 incident, uploads and new encoding stopped completely while existing videos stayed available, with slower starts and some playback errors. A full outage of the web services or player would stop playback too, so check which component the status page marks before telling your own users what to expect.
Does an OVHcloud outage affect api.video?
It can. api.video named OVHcloud S3 object storage as the cause of its October 7, 2026 incident, when video ingest was unavailable for about half an hour and delivery was degraded. If OVHcloud reports an object storage problem, watch status.api.video for uploads and encoding.
What happens to uploads that failed during the incident?
Retry them. After the October 7, 2026 storage incident api.video asked customers to retry any upload that failed and to contact support if uploads or playback still failed. An app that uploads on behalf of its users should retry its failed jobs once ingest is back.
Does live streaming fail separately from on-demand video?
Yes, it has. Live Streaming is its own component on status.api.video, and on July 6 and 7, 2026 api.video posted incidents for livestream encoding and delivery only, with broadcasters and viewers seeing buffering, interruptions or streams that would not start. On-demand video was not named in those incidents.

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 403 or 429 means 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
Free plan available No credit card required