dataplicity
Updated 19:58 UTC

All systems operational

Service health

Up api.dataplicity.com HTTP 200 • 41 ms
Up dataplicity.com HTTP 200 • 86 ms
Up Wormhole HTTP 200 • 69 ms

Heartbeats

Scheduler monitor

Last check received

Up

Slow scheduler

Last check received

Up

Fast scheduler

Last check received

Up

Incidents history

  • Database issue

    Started 07:45 UTC  — Closed 08:07 UTC  · Lasted 22 m

    Resolved
    • 07:45 UTC

      There is an issue with an internal database proxy which is causing a high error rate. Engineers have identified the fault and are presently implementing the repair.

    • 08:07 UTC

      During a migration, the deployment process used destroy and then create instead of create before destroy in relation to a database proxy. This caused an impairment to traffic for some key services while the proxy was reestablished. Systems are processing backlogs which should clear soon.