buckerStatus

Bucker uptime history

Results of the reachability checks this page makes against Bucker’s own public endpoints, recorded since 2026-09-08. Current status.

Each percentage is the share of recorded checks that passed, not a share of time — these are point-in-time requests on a schedule, so they cannot measure how long anything lasted. One cell is one day. A hatched cell is a day with no recorded check: not an outage, and not a healthy day either — grey covers both, including days still to come. There is no backfill before 2026-09-08, and Bucker publishes no SLA and no uptime commitment.

December 1979 to February 1980

No incidents are listed against these squares. Bucker does not publish incident records for its own services through this product, so an unmarked day here means only that nothing was recorded against it — not that nothing happened.

  • Event ingest
    The hostname in your DSNs, and the process behind it.
    99.86%
    4,852 checks over 52 recorded days, in the last 90 days
    December 1979no data
    January 1980no data
    February 1980no data
  • API
    Control-plane reads and writes, and the database behind them.
    99.84%
    4,852 checks over 52 recorded days, in the last 90 days
    December 1979no data
    January 1980no data
    February 1980no data
  • Web application
    The dashboard at app.bucker.io loads.
    100.00%
    4,852 checks over 52 recorded days, in the last 90 days
    December 1979no data
    January 1980no data
    February 1980no data
  • Agent (MCP) endpoint
    The endpoint agents and MCP clients connect to.
    99.94%
    4,852 checks over 52 recorded days, in the last 90 days
    December 1979no data
    January 1980no data
    February 1980no data
  • Background processing
    Alerts, digests, snapshots and scheduled jobs.
    No record
    No record no externally reachable endpoint to check
    December 1979no data
    January 1980no data
    February 1980no data

The checks run from this page’s own infrastructure, which is separate from the services it reports on. There is no incident narrative, no maintenance calendar and no subscriber notification for Bucker’s own services.