Skip to main content

Is Kaltura Down?

No — Kaltura is up

Reachable from all 8 checked regions

Average response time: 177ms

Last checked · checks run every 6 hours

Official status page: https://status.kaltura.com

Kaltura uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
145ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 19 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

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

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
28ms
DNS 0ms TCP 0ms TLS 3ms TTFB 21ms
arn
45ms
DNS 0ms TCP 0ms TLS 2ms TTFB 37ms
lhr
45ms
DNS 0ms TCP 2ms TLS 4ms TTFB 34ms
nrt
332ms
DNS 1ms TCP 1ms TLS 6ms TTFB 263ms
ord
49ms
DNS 0ms TCP 2ms TLS 14ms TTFB 40ms
sin
193ms
DNS 0ms TCP 8ms TLS 4ms TTFB 185ms
sjc
313ms
DNS 1ms TCP 20ms TLS 22ms TTFB 240ms
syd
272ms
DNS 1ms TCP 1ms TLS 6ms TTFB 267ms
yyz
184ms
DNS 1ms TCP 8ms TLS 10ms TTFB 156ms

What Kaltura does

Kaltura hosts, transcodes and delivers video for universities and large enterprises, usually embedded inside something else. Lecture capture in a learning management system, an internal town hall, a webinar platform and a media portal can all be Kaltura underneath, which is why an incident tends to surface as a broken player in another vendor's product rather than as a Kaltura page failing.

What an outage looks like

Embedded players show a spinner or an error where a lecture should be, while the surrounding course page loads normally. Uploads accept a file and then stall, or complete and never appear, because upload and transcoding are separate components. Live sessions fail to start or drop viewers mid-stream. Automatic captions stop arriving, since REACH is reported on its own, and the management console may be unreachable while playback still works.

What to do about it

Check status.kaltura.com, which reports Playback, Upload, Import, Transcoding, Live, Analytics, the API, the Management Console, MediaSpace, Webinars, REACH captioning, Pitch and the Zoom integration separately. Confirm which cloud you are on first: Kaltura maintains distinct status pages for its Australia, EU, Germany, Singapore and Canada regional clouds, so the main page may be green while yours is not. Stalled uploads generally need re-submitting.

Is it down for everyone, or just you?

If this page says Kaltura is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Zoom
Zoom
V
Vimeo
W
Webex
C
Canvas

Kaltura outage FAQ

Why is the video broken but the course page fine?
Because the course page comes from your learning management system and the video comes from Kaltura. The two are separate services and fail independently, so a green Canvas or Blackboard says nothing about playback. This is the most common shape of a Kaltura incident from a student's point of view, and it is why reporting it to the LMS help desk often produces a confused first response.
Does the main status page cover my region?
Not necessarily. Kaltura runs separate regional clouds for Australia, the EU, Germany, Singapore and Canada, each with its own status page linked from the main one. An institution hosted on the EU cloud should read the EU page, because the main page describes a different deployment. Establishing which cloud your account sits on before an incident saves the most time during one.
Will my upload finish or do I need to start again?
It depends which component failed. Upload and Transcoding are listed separately: a file that reached Kaltura but has not processed will usually finish on its own once transcoding recovers, while an upload that stalled partway generally needs re-submitting. Give a stuck entry an hour after the status page clears before re-uploading, since a duplicate creates two entries you then have to reconcile in the media portal.
Do recorded lectures disappear during an outage?
No. Stored media is not lost by a playback or console incident; what fails is reaching it. The risk sits at the edges of the pipeline rather than in storage: a live session that never recorded because Live was down, or an upload that never completed. After recovery, check that anything captured during the incident actually exists rather than assuming the catalogue is complete.
Does a Kaltura outage affect Zoom recordings?
It can, if your institution routes Zoom recordings into Kaltura, which is a common setup and is why the Zoom integration is its own component. Zoom itself may be entirely healthy while the handoff fails, leaving recordings in Zoom that never appear in the media portal. They are generally still retrievable from Zoom directly, so check there before treating a session as lost.

How we measure this

  • We request Kaltura's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • 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. We only change the 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 Kaltura publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Kaltura goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required