dataplicityService status

Service health

A clear view of what’s happening.

All times in UTC

Current status

Some services need attention

Check the affected services and latest incident updates below.

6 of 6 monitored checks operational1 active incident

Active incidents

1
Ongoing

P1

6 h ago · Started

Latest update

Me and you affected

Service health

3 checks

api.dataplicity.com

Endpoint check·HTTP 200 • 190 ms

Last checked · Every 60s

Operational

dataplicity.com

Endpoint check·HTTP 200 • 195 ms

Last checked · Every 60s

Operational

Wormhole

Endpoint check·HTTP 200 • 219 ms

Last checked · Every 60s

Operational

Background services

Scheduler and heartbeat checks

Operational

Heartbeats

Scheduler monitor

Heartbeat

Last received · Every 300s

Operational

Slow scheduler

Heartbeat

Last received · Every 60s

Operational

Fast scheduler

Heartbeat

Last received · Every 60s

Operational

Incident history

Latest 1 published

Database issue

1 mo ago·07:45 UTC — 28 Jul 08:07 UTC·22 m

Resolved

2 updates · Newest first

  1. 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.

  2. 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.

Published incidents only. Absence of an incident is not a measure of uptime.