Skip to content
ScaledPapers

Website down checker / couchbase.com

Is couchbase.com down right now?

ScaledPapers is not affiliated with Couchbase.

couchbase.com (Couchbase) is up and reachable from all 16 locations as of October 23, 2026 at 21:08 UTC (median response time 72 ms).

Status
Online
Reachability
16 of 16 online
Median response
72 ms
Last checked

Probes this hostname from 16 locations.

Americas

Ashburn (us-east-1)

Online

78ms

403 Forbidden

Columbus (us-east-2)

Online

62ms

403 Forbidden

San Francisco (us-west-1)

Online

59ms

403 Forbidden

Portland (us-west-2)

Online

72ms

403 Forbidden

Montreal (ca-central-1)

Online

66ms

403 Forbidden

São Paulo (sa-east-1)

Online

60ms

403 Forbidden

Europe

Dublin (eu-west-1)

Online

106ms

403 Forbidden

London (eu-west-2)

Online

59ms

403 Forbidden

Paris (eu-west-3)

Online

86ms

403 Forbidden

Frankfurt (eu-central-1)

Online

109ms

403 Forbidden

Stockholm (eu-north-1)

Online

130ms

403 Forbidden

Asia Pacific

Tokyo (ap-northeast-1)

Online

91ms

403 Forbidden

Seoul (ap-northeast-2)

Online

49ms

403 Forbidden

Osaka (ap-northeast-3)

Online

42ms

403 Forbidden

Singapore (ap-southeast-1)

Online

65ms

403 Forbidden

Oceania

Sydney (ap-southeast-2)

Online

77ms

403 Forbidden

How to read a regional check

All 16 regions failing
The hostname is failing from every probe location. That usually means the origin is down, the TLS certificate has expired, or authoritative DNS is not answering. It is not a problem on one network path.
One region or continent failing
When a single city or one continent is offline and the rest return HTTP 200, the origin is up. The failure is usually a CDN or anycast edge route, or a regional cloud impairment between that probe and the site.
All 16 regions return 200, but it fails in your browser
The site is reachable from our probes. A local failure is usually a stale ISP DNS cache, a corporate firewall or VPN, or a browser extension blocking the request.
HTTP 403 or 429 from the probes
A 403 or 429 from many cloud probes often means a WAF or Cloudflare bot challenge is blocking AWS IP ranges. That is not the same as an application outage. Compare the status code with what your browser receives.

Need to know when something goes down?

Monitor any endpoint on a schedule and get Slack, Discord, PagerDuty, or webhook alerts. Free checks run every 5 minutes. Pro can check every 60 seconds.