PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if api.video is down?

PulseWatch evaluates user reports and replay-approved automated evidence for api.video. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported api.video issues today?

As of Oct 12, 2026 18:46 UTC, 0 users had reported issues with api.video in the previous 24 hours.

How can I report a api.video outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Streaming

Is api.video down right now?

UnknownOfficial status last polled Oct 12, 2026 16:28 UTCapi.video Official status page

Are you on the api.video team and see something inaccurate? Report it to us. We respond within one business day.

Is api.video down right now?

Unknown. api.video does not have a conclusive current status. A single-runtime HTTP reachability check succeeded; no fresh official status confirms whole-service health.

Status as of Oct 12, 2026 18:46 UTC

Unknown

api.video: status unknown

As of Oct 12, 2026 18:46 UTC

No product check is currently qualified to corroborate an incident for this service. Overall service status has not been established.

Reports 24h

Last incident

Oct 7, 2026 14:51 UTC

Trend

0/15m

Monitoring

Coverage gap

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for api.video.

Incident days

No recorded incident

1h 30m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for api.video. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

1 incident

Busiest day

1h 30m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

api.video: vendor-reported major incident on October 7 (tracked 1h 29m)

Oct 7, 01:21 PM → Oct 7, 02:51 PM · 1h 29m · high

api.video reported a major-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked this incident for 1h 29m, closing it on 2026-10-07T14:51:39.985Z.

Duration

1h 29m

tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident and therefore cannot describe what users experienced. The incident is known from api.video's status page.

Incident timeline

Oct 7, 01:21 PM
The vendor reported a major-impact incident on its own status page; PulseWatch began tracking it
Oct 7, 01:21 PM
Status updated: possible issue
Oct 7, 02:51 PM
PulseWatch closed the incident

Official updates

Oct 7, 01:21 PM
api.video reported the incident on its status page.
View official source

Reliability

Not measured

30-day uptime

n/a

90-day uptime

n/a

Not calculated: api.video is unknown, so there is no incident history to measure and no uptime figure is shown.

Other streaming services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →

ResolvedHigh

api.video: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch api.video or have an alert rule on it can be alerted, labelled vendor-reported.

10/7/2026, 1:21:50 PM · 1h 29m

01:21 PM02:51 PM

Detection10/7/2026, 1:21:50 PM · 5d ago

Detected — high severity

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment api.video enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

0 reports aggregated in last 24h
Crowdsourced baseline detection
Official status page

Live signal

Status: Unknown
Monitoring: A single-runtime HTTP reachability check succeeded; no fresh official status confirms whole-service health.
Coverage: Verified against the vendor's own incident history
Reports (24h): 0
Baseline / hour: 5
Open threshold: 3x

Official site

api.video

Related services

100ms

Streaming

Normal

Agora

Streaming

Unknown

Amazon Music

Streaming

Unknown