Performance Issue: CUBlog service experienced a brief service/performance interuption
Last Updated:
2018-12-07 20:27:30
Event:
2018-12-06 13:50:00
Status:
Closed
Brief Description:
This morning the CUBlog service experienced a brief service interruption (10 minutes).
User Impact:
N/A
Workaround:
There is no workaround for this issue
Current Status:
Service restored.
From CampusPress:
Our logs show a spike in response times around the time of the reported problems. Any slowness or downtime you experienced was due to bots...while our autoscaling tried to launch more instances to cope with the higher number of requests.
During this period you could have definitely experienced delays, slowness and specifically 499 status codes.
From CampusPress:
Our logs show a spike in response times around the time of the reported problems. Any slowness or downtime you experienced was due to bots...while our autoscaling tried to launch more instances to cope with the higher number of requests.
During this period you could have definitely experienced delays, slowness and specifically 499 status codes.
Services Affected:
CU Blogs
Full Description:
This morning the CUBlog service experienced a brief service interruption (10 minutes). Service was restored and we are investigating the issue with CampusPress
Timeline of Changes
| Description | Current Status | Date | Time |
|---|---|---|---|
| This morning the CUBlog service experienced a brief service interruption (10 minutes). Service was restored and we are investigating the issue with CampusPress | Service restored. From CampusPress: Our logs show a spike in response times around the time of the reported problems. Any slowness or downtime you experienced was due to bots...while our autoscaling tried to launch more instances to cope with the higher number of requests. During this period you could have definitely experienced delays, slowness and specifically 499 status codes. | 2018-12-07 | 20:27:30 |
| This morning the CUBlog service experienced a brief service interruption (10 minutes). Service was restored and we are investigating the issue with CampusPress | Service restored. | 2018-12-06 | 15:34:03 |