Is Kaltura Down?

No — Kaltura is up

Kaltura's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 415 ms

Right now

The verdict is the worse of these two. How we decide

Kaltura's status page

status.kaltura.com · read 3 minutes ago · checked every 3 minutes

Operational

Kaltura's components, as its status page reports them
Component	Status
Analytics	Operational
Kaltura API	Operational
Import	Operational
Transcoding	Operational
Live	Operational
Playback	Operational
Kaltura Management Console (KMC)	Operational
Kaltura MediaSpace	Operational
Pitch	Operational
Zoom Integration	Operational
Documentation and Customer Care Platforms	Operational
Quality of caption services	Operational

9 more, all operational · show all 21

All of Kaltura's components
Component	Status
Analytics	Operational
Kaltura API	Operational
Import	Operational
Transcoding	Operational
Live	Operational
Playback	Operational
Kaltura Management Console (KMC)	Operational
Kaltura MediaSpace	Operational
Pitch	Operational
Zoom Integration	Operational
Documentation and Customer Care Platforms	Operational
Kaltura REACH (captioning service)
Quality of caption services	Operational
Processing Speed	Operational
Upload
Upload Speed	Operational
Upload Process	Operational
Kaltura Webinars, Virtual Classroom and Meetings
Platform Access	Operational
Video Conferencing Features	Operational
File Upload	Operational
Recording	Operational
Analytics	Operational
Kaltura Meetings	Operational

Open their status page

FlareWarden checks

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

Reachable

Regions up: 8 of 8
Response: 415 ms
Checked: 2 hours ago

By region

Ashburn reachable, 898 ms
Chicago reachable, 164 ms
Frankfurt reachable, 71 ms
Johannesburg reachable, 873 ms
London reachable, 118 ms
Los Angeles reachable, 76 ms
São Paulo reachable, 593 ms
Tokyo reachable, 530 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	173 ms	1 ms	14 ms	224 ms
Chicago	145 ms	1 ms	3 ms	157 ms
Frankfurt	53 ms	1 ms	5 ms	65 ms
Johannesburg	310 ms	0 ms	5 ms	493 ms
London	92 ms	2 ms	4 ms	110 ms
Los Angeles	54 ms	2 ms	4 ms	68 ms
São Paulo	361 ms	1 ms	5 ms	581 ms
Tokyo	256 ms	2 ms	5 ms	511 ms

We check that corp.kaltura.com loads, not every feature behind it. Test it yourself

History

Incidents Kaltura reported

Since Oct 22, 1 day · from status.kaltura.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Kaltura website availability

Measured by FlareWarden · corp.kaltura.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 302ms

Last 30 days

79-day clean streak

Sep 23 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of corp.kaltura.com from multiple regions every 6 hours. Kaltura's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 79 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

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 — 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 Kaltura 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 Kaltura 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 Kaltura goes down

We check Kaltura 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