TracCloudStatusHistory: Difference between revisions
From Redrock Wiki
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
<hr> | <hr> | ||
<i>History:</i><br> | <i>History:</i><br> | ||
<b>2023-10-05</b> - TracCloud 500, 502, 503, 504 errors from 3:40 to 4:15pm PST. | |||
<b>2023-09-26</b> - TracCloud bad gateway error from 2:45 to 3:00pm PST. | <b>2023-09-26</b> - TracCloud bad gateway error from 2:45 to 3:00pm PST. | ||
Revision as of 16:16, 5 October 2023
History:
2023-10-05 - TracCloud 500, 502, 503, 504 errors from 3:40 to 4:15pm PST.
2023-09-26 - TracCloud bad gateway error from 2:45 to 3:00pm PST.
2023-06-13 - TracCloud instances with custom URLs received error 500 from 3:15pm to 3:35pm PST.
2023-05-09 - TracCloud 503 error from 2:00pm to 2:10pm.
2023-05-08 - TracCloud slowness/errors due to failed maintenance over weekend, resolved at 1:30pm.
2022-12-05 - TracCloud connection timing out for certain ISPs due to AWS outage from 11:34 AM to 12:51 PM PST. https://health.aws.amazon.com/health/status
2022-10-18 - TracCloud running slowly due to AWS limitations. Resolved at 2:30pm MST.
2022-10-03 - TracCloud Appointment Scheduling limitations, resolved at 9:19am MST
2022-07-28 - TracCloud Down due to AWS outage from 10:11am to 11:25am MST. https://health.aws.amazon.com/health/status
2022-07-25 - TracCloud SSO limitations, resolved at 8:00am MST.