Skip to main content
Brightcove logo

Is Brightcove Down?

No — Brightcove is up
Brightcove's status page
Not available · we could not read it
FlareWarden checks
Website reachable · 8 of 8 regions · 1087 ms

Right now

We could not read Brightcove's status page, so the verdict rests on our checks. Check it yourself How we decide

FlareWarden checks

brightcove.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
1087 ms
Checked

By region

  • Ashburn reachable, 465 ms
  • Frankfurt reachable, 877 ms
  • Johannesburg reachable, 2332 ms
  • London reachable, 927 ms
  • Los Angeles reachable, 656 ms
  • Newark reachable, 397 ms
  • São Paulo reachable, 1313 ms
  • Tokyo reachable, 1735 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Ashburn68 ms1 ms3 ms423 ms
Frankfurt43 ms94 ms96 ms403 ms
Johannesburg265 ms245 ms247 ms1104 ms
London48 ms99 ms101 ms427 ms
Los Angeles59 ms58 ms59 ms363 ms
Newark205 ms7 ms10 ms354 ms
São Paulo206 ms120 ms122 ms711 ms
Tokyo174 ms184 ms186 ms809 ms
We check that brightcove.com loads, not every feature behind it. Test it yourself

History

Brightcove website availability

Measured by FlareWarden · brightcove.com

Last 7 days
98.21%
Last 30 days
99.57%
Last 90 days
99.82%
Avg response, 30 days
1554ms

Last 30 days

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

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

What Brightcove does

Brightcove hosts and delivers video for broadcasters, publishers and enterprises. It ingests and transcodes uploaded files, stores the resulting renditions and serves playback through its own players, with server-side ad insertion and live streaming alongside. Media companies embed those players in their own sites, so an incident interrupts video on somebody else's property.

What an outage looks like

Videos fail to start or stall mid-playback on sites using Brightcove players, often with the player frame loading but no content in it. Publishers see uploads that never finish processing, and newly ingested videos stay unavailable. Ad breaks may be missing where server-side ad insertion is used, and live streams drop or fail to start.

What to do about it

Check Brightcove's status page, which breaks components out per region across Americas, EMEA, Japan and two Asia Pacific rows, and read the region your audience sits in. Playback and ingestion are separate: viewers can be fine while uploads are stuck, and the reverse. Studio, CMS API and Live are further components. Avoid re-uploading videos still processing.

Is it down for everyone, or just you?

If this page says Brightcove 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

Brightcove outage FAQ

Viewers cannot play video but my uploads work. Is that Brightcove?
It fits their component split. VOD Playback and VOD Ingestion are reported separately and fail independently, so delivery to viewers can break while the publishing side stays healthy. Check the Playback row for your viewers' region rather than the overall headline, which stays green when a single region is affected.
Does an outage in one region affect viewers elsewhere?
Usually not. Brightcove reports players, playback, ingestion and ad insertion per region across Americas, EMEA, Japan and Asia Pacific, so an incident is often geographically contained. Viewers in an unaffected region keep watching normally. This is also why reports from your audience may conflict with what you see yourself.
My upload has been processing for hours. Should I re-upload?
Wait first. An ingestion incident leaves jobs queued rather than failed, and they generally complete once the component recovers. Re-uploading during the incident adds work to a backed-up queue and can leave duplicate assets to clean up afterwards. Check the VOD Ingestion row for your region before deciding.
Are ads affected separately from video?
Yes. VOD SSAI, which stitches ads into the stream server-side, is its own component per region. It can fail while playback is fine, in which case video plays but ad breaks are missing or empty. For ad-funded publishers that is a revenue incident even though nothing looks broken to the viewer.

How we measure this

  • We request Brightcove'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 Brightcove 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 Brightcove 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. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.

Get alerted when Brightcove goes down

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