BioCE Status
All Systems OperationalUpdated 2026-08-28 04:34 (+07)

Components

Uptime over the past 90 days
Course & public sites
bioce.cloud - estate landingOperational
90 days ago99.28 % uptimeToday
course.bioce.cloud - course hubOperational
90 days ago99.28 % uptimeToday
pgce.bioce.cloud - PG-CE LMS portalOperational
90 days ago99.28 % uptimeToday
pgcs.bioce.cloud - PG-CS siteOperational
90 days ago99.28 % uptimeToday
trials.bioce.cloud - clinical trials siteOperational
90 days ago99.28 % uptimeToday
Apps & services
pgce.bioce.cloud/api - PG-CE LMS APIOperational
90 days ago99.23 % uptimeToday
consult.bioce.cloud - BioCE ConsoleOperational
90 days ago99.05 % uptimeToday
webapps.bioce.cloud - clinical epidemiology apps hubOperational
90 days ago98.9 % uptimeToday
herobioce.uniqcret.com - HEROs CTMSOperational
90 days ago99.28 % uptimeToday
Infrastructure
bioce-console.bioce.workers.dev - Console WorkerOperational
90 days ago99.28 % uptimeToday
VPS HERO (72.60.74.175) - heartbeatOperational
90 days ago100 % uptimeToday
OperationalDegraded PerformancePartial OutageMajor OutageMaintenance⚠ flappingchanging status too often to alert on — Telegram is paused for it until it settles, while incidents and history keep recording

Past Incidents

Aug 28, 2026
bioce-console.bioce.workers.dev - Console Worker — Major outage
bioce-console.bioce.workers.dev - Console Worker
  1. Resolved — Recovered automatically after 4m 59s (http 200).2026-08-28 03:58 (+07)
  2. Investigating — Automatic detection: timeout after 10000ms after 3 consecutive failures.2026-08-28 03:53 (+07)
herobioce.uniqcret.com - HEROs CTMS — Major outage
herobioce.uniqcret.com - HEROs CTMS
  1. Resolved — Recovered automatically after 4m 59s (http 200).2026-08-28 03:58 (+07)
  2. Investigating — Automatic detection: timeout after 10000ms after 3 consecutive failures.2026-08-28 03:53 (+07)
webapps.bioce.cloud - clinical epidemiology apps hub — Major outage
webapps.bioce.cloud - clinical epidemiology apps hub
  1. Resolved — Recovered automatically after 4m 59s (http 200).2026-08-28 03:58 (+07)
  2. Investigating — Automatic detection: timeout after 10000ms after 3 consecutive failures.2026-08-28 03:53 (+07)
consult.bioce.cloud - BioCE Console — Major outage
consult.bioce.cloud - BioCE Console
  1. Resolved — Recovered automatically after 4m 59s (http 200).2026-08-28 03:58 (+07)
  2. Investigating — Automatic detection: timeout after 10000ms after 3 consecutive failures.2026-08-28 03:53 (+07)
pgce.bioce.cloud/api - PG-CE LMS API — Major outage
pgce.bioce.cloud/api - PG-CE LMS API
  1. Resolved — Recovered automatically after 4m 59s (http 200).2026-08-28 03:58 (+07)
  2. Investigating — Automatic detection: timeout after 10000ms after 3 consecutive failures.2026-08-28 03:53 (+07)
trials.bioce.cloud - clinical trials site — Major outage
trials.bioce.cloud - clinical trials site
  1. Resolved — Recovered automatically after 4m 59s (http 200).2026-08-28 03:58 (+07)
  2. Investigating — Automatic detection: timeout after 10000ms after 3 consecutive failures.2026-08-28 03:53 (+07)
pgcs.bioce.cloud - PG-CS site — Major outage
pgcs.bioce.cloud - PG-CS site
  1. Resolved — Recovered automatically after 4m 59s (http 200).2026-08-28 03:58 (+07)
  2. Investigating — Automatic detection: timeout after 10000ms after 3 consecutive failures.2026-08-28 03:53 (+07)
pgce.bioce.cloud - PG-CE LMS portal — Major outage
pgce.bioce.cloud - PG-CE LMS portal
  1. Resolved — Recovered automatically after 4m 59s (http 200).2026-08-28 03:58 (+07)
  2. Investigating — Automatic detection: timeout after 10000ms after 3 consecutive failures.2026-08-28 03:53 (+07)
course.bioce.cloud - course hub — Major outage
course.bioce.cloud - course hub
  1. Resolved — Recovered automatically after 4m 59s (http 200).2026-08-28 03:58 (+07)
  2. Investigating — Automatic detection: timeout after 10000ms after 3 consecutive failures.2026-08-28 03:53 (+07)
bioce.cloud - estate landing — Major outage
bioce.cloud - estate landing
  1. Resolved — Recovered automatically after 4m 59s (http 200).2026-08-28 03:58 (+07)
  2. Investigating — Automatic detection: timeout after 10000ms after 3 consecutive failures.2026-08-28 03:53 (+07)
consult.bioce.cloud - BioCE Console — Major outage
consult.bioce.cloud - BioCE Console
  1. Resolved — Recovered automatically after 4m 00s (http 200).2026-08-28 00:14 (+07)
  2. Investigating — Automatic detection: timeout after 10000ms after 3 consecutive failures.2026-08-28 00:10 (+07)
Aug 27, 2026
bioce-console.bioce.workers.dev - Console Worker — Major outage
bioce-console.bioce.workers.dev - Console Worker
  1. Resolved — Recovered automatically after 10m 59s (http 200).2026-08-27 04:36 (+07)
  2. Investigating — Automatic detection: CacheTtl: 0, is not compatible with cache: no-store header. after 3 consecutive failures.2026-08-27 04:25 (+07)
herobioce.uniqcret.com - HEROs CTMS — Major outage
herobioce.uniqcret.com - HEROs CTMS
  1. Resolved — Recovered automatically after 10m 59s (http 200).2026-08-27 04:36 (+07)
  2. Investigating — Automatic detection: CacheTtl: 0, is not compatible with cache: no-store header. after 3 consecutive failures.2026-08-27 04:25 (+07)
webapps.bioce.cloud - clinical epidemiology apps hub — Major outage
webapps.bioce.cloud - clinical epidemiology apps hub
  1. Resolved — Recovered automatically after 10m 59s (http 200).2026-08-27 04:36 (+07)
  2. Investigating — Automatic detection: CacheTtl: 0, is not compatible with cache: no-store header. after 3 consecutive failures.2026-08-27 04:25 (+07)
consult.bioce.cloud - BioCE Console — Major outage
consult.bioce.cloud - BioCE Console
  1. Resolved — Recovered automatically after 10m 59s (http 200).2026-08-27 04:36 (+07)
  2. Investigating — Automatic detection: CacheTtl: 0, is not compatible with cache: no-store header. after 3 consecutive failures.2026-08-27 04:25 (+07)
pgce.bioce.cloud/api - PG-CE LMS API — Major outage
pgce.bioce.cloud/api - PG-CE LMS API
  1. Resolved — Recovered automatically after 10m 59s (http 200).2026-08-27 04:36 (+07)
  2. Investigating — Automatic detection: CacheTtl: 0, is not compatible with cache: no-store header. after 3 consecutive failures.2026-08-27 04:25 (+07)
trials.bioce.cloud - clinical trials site — Major outage
trials.bioce.cloud - clinical trials site
  1. Resolved — Recovered automatically after 10m 59s (http 200).2026-08-27 04:36 (+07)
  2. Investigating — Automatic detection: CacheTtl: 0, is not compatible with cache: no-store header. after 3 consecutive failures.2026-08-27 04:25 (+07)
pgcs.bioce.cloud - PG-CS site — Major outage
pgcs.bioce.cloud - PG-CS site
  1. Resolved — Recovered automatically after 10m 59s (http 200).2026-08-27 04:36 (+07)
  2. Investigating — Automatic detection: CacheTtl: 0, is not compatible with cache: no-store header. after 3 consecutive failures.2026-08-27 04:25 (+07)
pgce.bioce.cloud - PG-CE LMS portal — Major outage
pgce.bioce.cloud - PG-CE LMS portal
  1. Resolved — Recovered automatically after 10m 59s (http 200).2026-08-27 04:36 (+07)
  2. Investigating — Automatic detection: CacheTtl: 0, is not compatible with cache: no-store header. after 3 consecutive failures.2026-08-27 04:25 (+07)
course.bioce.cloud - course hub — Major outage
course.bioce.cloud - course hub
  1. Resolved — Recovered automatically after 10m 59s (http 200).2026-08-27 04:36 (+07)
  2. Investigating — Automatic detection: CacheTtl: 0, is not compatible with cache: no-store header. after 3 consecutive failures.2026-08-27 04:25 (+07)
bioce.cloud - estate landing — Major outage
bioce.cloud - estate landing
  1. Resolved — Recovered automatically after 10m 59s (http 200).2026-08-27 04:36 (+07)
  2. Investigating — Automatic detection: CacheTtl: 0, is not compatible with cache: no-store header. after 3 consecutive failures.2026-08-27 04:25 (+07)
webapp.bioce.cloud - idiom app — Major outage
webapp
  1. Resolved — Component retired, not recovered. webapp.bioce.cloud was renamed to webapps.bioce.cloud on 2026-08-27; the old hostname is now a path-preserving 301 and is no longer a monitored component. The new component 'webapps' is operational. Resolving this incident because the thing it describes no longer exists - it was holding the whole board at 'Partial System Outage'.2026-08-27 04:24 (+07)
  2. Investigating — Automatic detection: http 301 after 3 consecutive failures.2026-08-27 04:22 (+07)
webapp.bioce.cloud - idiom app — Major outage
webapp
  1. Resolved — Recovered automatically after 3m 00s (http 200).2026-08-27 02:06 (+07)
  2. Investigating — Automatic detection: timeout after 10000ms after 3 consecutive failures.2026-08-27 02:03 (+07)
Maintenance mode - course, pgce, pgce-api
course.bioce.cloud - course hub, pgce.bioce.cloud - PG-CE LMS portal, pgce.bioce.cloud/api - PG-CE LMS API
  1. Completed — Maintenance mode off - course, pgce, pgce-api back to normal probing.2026-08-27 01:56 (+07)
  2. In Progress — The owner turned maintenance mode on (/usr/local/bin/maintenance on); the estate serves its bilingual maintenance page. Detected on course, pgce, pgce-api via the X-BioCE-Maintenance response header (source: marker).2026-08-27 01:55 (+07)
Aug 26, 2026
No incidents reported.
Aug 25, 2026
No incidents reported.
Aug 24, 2026
No incidents reported.
Aug 23, 2026
No incidents reported.
Aug 22, 2026
No incidents reported.
Aug 21, 2026
No incidents reported.
Aug 20, 2026
No incidents reported.
Aug 19, 2026
No incidents reported.
Aug 18, 2026
No incidents reported.
Aug 17, 2026
No incidents reported.
Aug 16, 2026
No incidents reported.
Aug 15, 2026
No incidents reported.
Aug 14, 2026
No incidents reported.