All Systems Operational
Yellowdig Engage (North America) Operational
90 days ago
99.89 % uptime
Today
Frontend Operational
90 days ago
99.89 % uptime
Today
API Operational
90 days ago
99.89 % uptime
Today
Yellowdig Engage (Australia & Asia) Operational
90 days ago
100.0 % uptime
Today
Frontend Operational
90 days ago
100.0 % uptime
Today
API Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Past Incidents
Sep 22, 2020

No incidents reported today.

Sep 21, 2020

No incidents reported.

Sep 20, 2020

No incidents reported.

Sep 19, 2020

No incidents reported.

Sep 18, 2020

No incidents reported.

Sep 17, 2020

No incidents reported.

Sep 16, 2020
Completed - The scheduled maintenance was completed. To our knowledge no additional downtime was created and we did not receive any influx of support tickets that would suggest otherwise. This update to our back-end systems will allow us to do deploys of new code without incurring any downtime or creating maintenance windows. That will enable us to quickly and safely release most new features and bug fixes at any time, as needed. We know that many of our partner institutions are relying on us more than ever before and we see this as the first of many steps toward ensuring that the platform is there, ready whenever anyone needs it, and is continuously improving.
Sep 16, 13:00 EDT
Scheduled - Hi,

I'm writing to let you know that Yellowdig will be undergoing a maintenance period tomorrow, Wednesday September 16. The maintenance will begin at 9:00AM and should be completed by noon (12:00PM).

We do not expect that this maintenance will incur any downtime or that users will notice any service interruptions as a result, but there is some chance that users will experience some fleeting errors or extended page loads.

Should any unexpected service interruptions occur, we will report them and update our status page accordingly.

Best,
Brian
Sep 15, 18:17 EDT
Sep 15, 2020
Resolved - A data migration created a period with higher than normal error rates. These would have started around 4:40pm EST and ended around 5:05pm EST.
Sep 15, 16:40 EDT
Sep 14, 2020
Resolved - We observed a small spike in the baseline of error rates for the platform which also generated a handful of support tickets between 11:30pm and 12:00am reporting LTI launch failures or "oh snap" errors with error codes. Some small adjustments were made that quickly reduced the error rate back to typical levels.
Sep 14, 23:30 EDT
Resolved - A maintenance message was put up to move some system components around. This work was meant to improve system stability and was necessary to enable the next steps in enabling code deployments that do not incur any downtime. The impacted time was from 6:00pm EST to 6:15pm EST.
Sep 14, 18:00 EDT
Resolved - A data heavy migration cause higher than normal error volume, which affected access for some users. The impacted times would have been from 2:55pm EST to 3:30 EST.
Sep 14, 02:55 EDT
Sep 13, 2020

No incidents reported.

Sep 12, 2020

No incidents reported.

Sep 11, 2020

No incidents reported.

Sep 10, 2020

No incidents reported.

Sep 9, 2020

No incidents reported.

Sep 8, 2020
Resolved - A portion of our users encountered "Oh Snap" errors this morning which was caused by disk space on one of our servers being full. Depending on how a user's traffic was routed through the system they may have encountered this while trying to enter a specific community or more globally throughout the platform.

We were already in the process of replacing the server that encountered the issue and improving our monitoring of their functioning and disk capacity. The completion of that work will prevent this issue from re-occurring in the future.

We believe these errors likely started to occur around 11:27 am EST. Our operational team cleared that server's disk space and the errors would have stopped as of 12:00 noon EST.

We apologize for any inconvenience and will strive to ensure it does not happen again.
Sep 8, 11:27 EDT