Skip to main content
Brightcove logo

Is Brightcove Down?

No — Brightcove is up

Reachable from all 8 checked regions

Average response time: 993ms

Last checked · checks run every 6 hours

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

Brightcove uptime

95.83%
Last 7 days
98.14%
Last 30 days
98.14%
Last 90 days
1200ms
Avg response, 30 days

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

30-day history

4-day clean streak
Aug 12: no data
Aug 13: no data
Aug 14: no data
Aug 15: no data
Aug 16: no data
Aug 17: no data
Aug 18: no data
Aug 19: no data
Aug 20: no data
Aug 21: no data
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: 100.00% uptime, 16 checks
Aug 27: 100.00% uptime, 32 checks
Aug 28: 100.00% uptime, 32 checks
Aug 29: 100.00% uptime, 32 checks
Aug 30: 96.88% uptime, 32 checks
Aug 31: 100.00% uptime, 32 checks
Sep 1: 100.00% uptime, 32 checks
Sep 2: 100.00% uptime, 31 checks
Sep 3: 100.00% uptime, 24 checks
Sep 4: 95.83% uptime, 24 checks
Sep 5: 100.00% uptime, 29 checks
Sep 6: 78.57% uptime, 28 checks
Sep 7: 100.00% uptime, 31 checks
Sep 8: 100.00% uptime, 16 checks
Sep 9: 100.00% uptime, 32 checks
Sep 10: 100.00% uptime, 8 checks
Aug 12 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.

iad
192ms
DNS 142ms TCP 1ms TLS 3ms TTFB 169ms
jnb
1921ms
DNS 3ms TCP 237ms TLS 239ms TTFB 966ms
lax
512ms
DNS 33ms TCP 57ms TLS 59ms TTFB 280ms
lhr
676ms
DNS 45ms TCP 76ms TLS 78ms TTFB 367ms
nrt
1607ms
DNS 203ms TCP 173ms TLS 175ms TTFB 910ms
ord
211ms
DNS 31ms TCP 20ms TLS 21ms TTFB 125ms
sin
2262ms
DNS 451ms TCP 224ms TLS 225ms TTFB 1361ms
sjc
565ms
DNS 3ms TCP 66ms TLS 68ms TTFB 290ms

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 18 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.
  • 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 Brightcove 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 Brightcove goes down

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

Start Free Monitoring
Free plan available No credit card required