scribase
Status

Platform status

A component-by-component view of every service that makes up Scribase, grouped by data plane, platform, and web.

Operational7 of 7 probed components operational6 of 13 not probed yet

Current status

Checked live each time this page loads. Components marked "Not probed" have no public health endpoint configured, so no state is claimed for them. To report an incident, use the contact page with the Support topic.

Last checked

Operational

Data plane

  • PostgreSQL

    Database connections and the /rest data API.

    no public health endpoint configured

    Not probed
  • Authentication

    Sign-in, tokens, and the /auth endpoints.

    no public health endpoint configured

    Not probed
  • Storage

    Object uploads, downloads, and the Storage API.

    no public health endpoint configured

    Not probed
  • Realtime

    Change streams, broadcast, and presence channels.

    no public health endpoint configured

    Not probed
  • Edge Functions

    The /functions/v1 execution path.

    no public health endpoint configured

    Not probed

Platform

  • Control API & CLI

    The authenticated /v1 management API and scribase CLI.

    HTTP 204 in 353 ms

    Operational
  • End-to-end journey

    Every hour: create a branch, migrate, write and read through the REST API, a realtime round trip, delete.

    no journey result published yet

    Not probed
  • Preview branches

    Provisioning and sweeping of preview environments.

    reported by control API readiness

    Operational
  • Backups & restore

    Backup capture and verified restore.

    reported by control API readiness

    Operational
  • Import & export

    Project import and full-stack export bundles.

    reported by control API readiness

    Operational

Web

  • Console

    The Scribase web console.

    HTTP 200 in 508 ms

    Operational
  • Website

    scribase.com, including this status page.

    HTTP 200 in 560 ms

    Operational
  • Documentation

    The reference documentation site.

    HTTP 200 in 34 ms

    Operational