liveworkspace

Status of liveworkspace and every app

Checking every service…

The first answers are on their way.

Every check runs live from your browser, every minute while this page is open. Beside them, liveworkspace checks every service from Cloudflare each hour and keeps 90 days.

Answering
0 of 35
services checked here
Median answer
—
this round
Last checked
—
waiting for the first answers
Next check
—

liveworkspace

Shared by every app: one account, one Explorer, one home for media and numbers.

Checking

  • Website

    Checking

    liveworkspace.app: sign-in, the Explorer, the dashboard and this page.

    From your browser:—HEAD /robots.txt
    No checks yet.

  • Accounts & sign-in

    Checking

    One account for every app: signing in, signing up and the tokens apps trust.

    From your browser:—GET /.well-known/openid-configuration
    No checks yet.

  • Explorer index

    Checking

    Every app’s items, folders, sharing and Inbox, in one Explorer.

    From your browser:—GET /api/index/jwks
    No checks yet.

  • Community

    Checking

    The public galleries of shared work behind each app’s Community pages.

    From your browser:—GET /api/community/facets
    No checks yet.

  • Telemetry

    Checking

    Every app’s anonymous events, and the public dashboard they feed.

    From your browser:—OPTIONS /api/telemetry/events
    No checks yet.

  • Media & previews

    Checking

    Uploaded images, and the picture of every item, for every app.

    From your browser:—GET /api/previews
    No checks yet.

livediagram

Diagram and draw together.

Checking

  • API

    Checking

    Saves and loads your work, and runs sharing, teams and tokens.

    From your browser:—GET /api/capabilities
    No checks yet.

  • Realtime rooms

    Checking

    Live cursors and edits between everyone in the same piece of work.

    The rooms run inside the API Worker, so the API’s check stands for them.

    From your browser:—Through the API

  • Editor

    Checking

    The app itself, where the work is made.

    From your browser:—HEAD /icon.svg
    No checks yet.

  • Marketing site

    Checking

    livediagram’s home page, features, comparisons and FAQ.

    From your browser:—HEAD /robots.txt
    No checks yet.

  • Help centre

    Checking

    Guides, how-tos and the developer docs.

    From your browser:—HEAD /help/robots.txt
    No checks yet.

  • Community pages

    Checking

    The public gallery of shared canvases.

    From your browser:—HEAD /community/
    No checks yet.

  • MCP server

    Checking

    Lets AI assistants read and make your work, with your permission.

    From your browser:—GET /health
    No checks yet.

  • Router

    Checking

    Puts every part of livediagram on one address.

    Every request to the app passes through the router, so it is up when any of them answers.

    From your browser:—0 of 5 checks answered

liveplanner

Plan the work together.

Checking

  • API

    Checking

    Saves and loads your work, and runs sharing, teams and tokens.

    From your browser:—GET /api/capabilities
    No checks yet.

  • Realtime rooms

    Checking

    Live cursors and edits between everyone in the same piece of work.

    The rooms run inside the API Worker, so the API’s check stands for them.

    From your browser:—Through the API

  • Editor

    Checking

    The app itself, where the work is made.

    From your browser:—HEAD /icon.svg
    No checks yet.

  • Marketing site

    Checking

    liveplanner’s home page, features, comparisons and FAQ.

    From your browser:—HEAD /robots.txt
    No checks yet.

  • Help centre

    Checking

    Guides, how-tos and the developer docs.

    From your browser:—HEAD /help/robots.txt
    No checks yet.

  • MCP server

    Checking

    Lets AI assistants read and make your work, with your permission.

    From your browser:—GET /health
    No checks yet.

  • Router

    Checking

    Puts every part of liveplanner on one address.

    Every request to the app passes through the router, so it is up when any of them answers.

    From your browser:—0 of 4 checks answered

livedocuments

Write and present together.

Checking

  • API

    Checking

    Saves and loads your work, and runs sharing, teams and tokens.

    From your browser:—GET /api/capabilities
    No checks yet.

  • Realtime rooms

    Checking

    Live cursors and edits between everyone in the same piece of work.

    The rooms run inside the API Worker, so the API’s check stands for them.

    From your browser:—Through the API

  • Editor

    Checking

    The app itself, where the work is made.

    From your browser:—HEAD /icon.svg
    No checks yet.

  • Marketing site

    Checking

    livedocuments’s home page, features, comparisons and FAQ.

    From your browser:—HEAD /robots.txt
    No checks yet.

  • Help centre

    Checking

    Guides, how-tos and the developer docs.

    From your browser:—HEAD /help/robots.txt
    No checks yet.

  • MCP server

    Checking

    Lets AI assistants read and make your work, with your permission.

    From your browser:—GET /health
    No checks yet.

  • Router

    Checking

    Puts every part of livedocuments on one address.

    Every request to the app passes through the router, so it is up when any of them answers.

    From your browser:—0 of 4 checks answered

livedesign

Design logos, wireframes and photos together.

Checking

  • API

    Checking

    Saves and loads your work, and runs sharing, teams and tokens.

    From your browser:—GET /api/capabilities
    No checks yet.

  • Realtime rooms

    Checking

    Live cursors and edits between everyone in the same piece of work.

    The rooms run inside the API Worker, so the API’s check stands for them.

    From your browser:—Through the API

  • Editor

    Checking

    The app itself, where the work is made.

    From your browser:—HEAD /icon.svg
    No checks yet.

  • Marketing site

    Checking

    livedesign’s home page, features, comparisons and FAQ.

    From your browser:—HEAD /robots.txt
    No checks yet.

  • Help centre

    Checking

    Guides, how-tos and the developer docs.

    From your browser:—HEAD /help/robots.txt
    No checks yet.

  • MCP server

    Checking

    Lets AI assistants read and make your work, with your permission.

    From your browser:—GET /health
    No checks yet.

  • Router

    Checking

    Puts every part of livedesign on one address.

    Every request to the app passes through the router, so it is up when any of them answers.

    From your browser:—0 of 4 checks answered

How to read this page

Operational
Answered as it should, in good time.
Reached
Another site answered. Browsers keep its reply private, so this says it is there, not what it said.
Slow
Answered, but took more than 1.5 seconds.
Down
No answer in 10 seconds, or an answer it shouldn’t give.
Checking
The first check is on its way.
Not checked
Not checked from this address; the row says why.

Your browser’s checks. The first line of each service, by the person icon: a request your browser makes to an address the service already answers, timed from here. A service down for you may be up for others, and the other way round. Its strip holds the checks since you opened this page, at most 30, and forgets them when you leave.

liveworkspace’s hourly checks. The second line, by the cloud: the same check, made from Cloudflare every hour, which can read every answer, so it never needs to say Reached. Under it, a bar per day for the last 90 days: taller and green when the service was up all day, shorter and amber or red for its worst slow or down check, a stub for a day without checks. Hover, tap or focus the bars for the day.