Live status & reliability report

Whereby status, outages & reliability

Whereby is a browser-based video meeting service and embeddable video API from a company based in Oslo, Norway.

Data updated Nov 1, 2026 · score recalculated

Over the last 90 days Whereby had 99.95% effective uptime across 3 status page incidents (1 partial or major outage), resolving them in 54m on average.

93.8/100Reliability scoreVisit Whereby ↗

Is Whereby down right now?

No, Whereby is up and running.

  • Whereby's status page reports all systems operational. Checked .
  • All 3 Whereby pages we check are responding. Checked .

Official Whereby status page ↗

Uptime (90d)99.95%55m weighted downtime
Incidents (90d)30.7 per 30 days
Major / partial outages1
Avg time to resolve54m
Outages we detected0by our independent probes

90-day uptime

Aug 4, 2026 – Aug 31, 2026: no incidentsSep 1, 2026: 97.50% uptime, 1 incident (Major outage)Sep 2, 2026 – Sep 13, 2026: no incidentsSep 14, 2026: 99.95% uptime, 1 incident (Degraded performance)Sep 15, 2026 – Sep 21, 2026: no incidentsSep 22, 2026: 98.72% uptime, 1 incident (Degraded performance)Sep 23, 2026 – Nov 1, 2026: no incidents
90 days ago99.957% average daily uptimeToday
  • No incidents
  • Degraded
  • Partial outage
  • Major outage
  • No data

Key facts about Whereby's reliability

  • Over the past 12 months, Whereby published 10 incidents on its status page, 5 of them partial or major outages.
  • Its longest outage on record in that time was “Streaming Unavailable” on Apr 29, 2026, which lasted 55m.
  • Whereby reported 3 incidents in the last 90 days, up from 0 in the 90 days before.
  • Incidents most often began on a Tuesday (4 of 10, UTC).
  • Whereby's 90-day uptime of 99.95% is above the average for video conferencing platforms (99.67%).
  • It resolves incidents faster than the typical video conferencing platform: 54m on average, against a median of 5h 8m.

Score breakdown

Uptime · 40% weight
96
99.958% effective uptime
Incident frequency · 20% weight
85
0.67 weighted incidents per 30 days
Time to resolve · 20% weight
93
54m average
Transparency · 20% weight
100
No unreported outages detected

How the score is calculated →

Incidents per month

01234DecJan ’261 major outage incident1 partial outage incident2Feb2 degraded performance incidents2Mar1 major outage incident1Apr1 partial outage incident1MayJunJulAug1 major outage incident2 degraded performance incidents3SepOctNov
  • Major outage
  • Partial outage
  • Degraded
  • Informational

Response time

Daily average response time of Whereby's public pages, measured by our probes.

Not enough data yet — this chart fills in as our monitoring runs.

Score trend

Daily reliability score (rolling 90-day window).

Not enough data yet — this chart fills in as our monitoring runs.

Whereby incident history (last 90 days)

Source: Whereby status page · last checked

Our independent monitoring

We check these public Whereby pages every 5 minutes. An outage is recorded after two consecutive failed checks.

PageLast checkUptime (30d)Avg response
HomepageUp 100%276 ms
Sign-in / dashboardUp 100%158 ms
Embedded APIUp 100%137 ms

How Whereby compares

Most reliable Whereby alternatives →

Whereby status FAQ

Is Whereby down right now?

No, Whereby is up and running. Whereby's status page currently reports all systems operational, and all 3 of the Whereby pages we check every five minutes are responding. This page updates automatically when that changes.

How reliable is Whereby?

Whereby has a reliability score of 93.8 out of 100, ranking #3 of 7 video conferencing platforms. Over the last 90 days it had 99.95% effective uptime.

How often does Whereby have outages?

Whereby published 3 incidents on its status page in the last 90 days (1 partial or major outage) and 10 in the past 12 months.

How long do Whereby outages last?

Whereby resolves incidents in 54m on average. Its longest outage in the past year lasted 55m, on Apr 29, 2026.

Does Whereby have a status page?

Yes. Whereby's official status page is wherebystatus.com. We read it every five minutes and keep its full incident history.