Whereby logo

Is Whereby Down?

CommunicationLive status, outages, and incident history

No. Whereby is up right now.

Every monitored Whereby system is operational as of November 10, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 2m agoLive · every 60s

Know the moment Whereby breaks

Whereby is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Whereby status page
How we know: the official Whereby status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Whereby Status Summary

As of 13:50 UTC on 10 November 2026, Whereby is operational. PulsAPI checked Whereby's official status page and found 4 of 4 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for Whereby, counting degraded performance as up. The latest incident, "Customer insights (dashboard and api) - degraded performance", was on Sep 22, 2026 and lasted 2h 4m.

Cite as: PulsAPI, “Whereby status”, checked 10 November 2026, 13:50 UTC. https://www.pulsapi.com/services/whereby

Whereby Component Status

The main Whereby systems on this page. All 4 are operational right now.

4operational
Admin dashboard
Operational
Embedded API
Operational
Meeting rooms
Operational

1 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking whereby.com.

See all of them free

Component statuses may change independently during partial outages.

Recent Whereby Outages & Incidents

Incident history from the official Whereby status page, including resolution updates.

Customer insights (dashboard and api) - degraded performanceResolved Sep 22, 2026 · 2h 4mResolved

Whereby Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Whereby incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 12100.00% average · 1 day with incidentsNov 10

Going further back: Whereby uptime by month and every recorded Whereby outage.

Live Whereby Outage Reports

Problems reported by engineers using Whereby. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Whereby problems reported yet.

Something wrong with Whereby on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Whereby

Whereby maintains a public status page at wherebystatus.com reporting overall service health. Follow Whereby downtime, degraded performance and resolved incidents here, with uptime history alongside your other communications services.

Over the past 30 days, PulsAPI has measured Whereby uptime at 100.00%. Response times, incident history, and SLA tracking for Whereby are available on the PulsAPI dashboard.

Whereby Status FAQ

Is Whereby down right now?

The verdict at the top of this page comes from the latest poll of the official Whereby status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Whereby is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Whereby recovers.

How do I check Whereby uptime history?

PulsAPI tracks Whereby uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Whereby changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Whereby outages?

PulsAPI reads the official Whereby status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Whereby components?

Yes. PulsAPI monitors 4 individual Whereby components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Whereby goes down?

Yes. Create a free account and subscribe to Whereby: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Whereby to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Whereby problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Whereby?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Whereby plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Whereby with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services