An infrastructure overhaul will be taking place. SIBYL and it's databases will be offline, updates will be given on this page.

12:00 GMT - SIBYL taken offline, database spinning down.
12:01 GMT - Database offline, shutting down instance for re-enrollment.
12:06 GMT - Instance stopped, re-enrollment requested.
12:08 GMT - Re-enrollment complete, instance spinning up.
12:08 GMT - Provisioning second instance.
12:09 GMT - Platform out of capacity for DB2 instance, investigating.
12:32 GMT - DB2 instance unable to be provisioned, workaround will be applied for next maintenance.
12:38 GMT - Core instance provisioned, transferring SIBYL to core instance. Original instance now designated as DB1.
12:47 GMT - DB1 database start confirmed.
12:50 GMT - SIBYL transferred to dedicated core instance.
12:53 GMT - SIBYL startup command sent, waiting for heartbeat.
13:38 GMT - SIBYL heartbeat confirmed, database connection also confirmed. Monitoring throughput until SIBYL is stable.
14:07 GMT - Reported memory bottleneck on new core instance, average transaction time is not stabilising.
14:18 GMT - Average transaction time unsatisfactory, re-enrolling core instance.
15:04 GMT - New core instance enrolled, transferring SIBYL.
15:36 GMT - SIBYL transferred, waiting for heartbeat.
15:40 GMT - Heartbeat confirmed, database link confirmed.
15:52 GMT - Encountering odd network issues with core instance.
16:37 GMT - Odd network issues are still persisting.
17:55 GMT - Issue resolved, all systems operational.
17:57 GMT - Maintenance concluded.

Conclusion: Dedicated DB1 instance was deployed, DB2 was unable to be deployed due to capacity errors. Dedicated SIBYL core was deployed.