Uptime Summary
Recent Uptime
Day | Date | Uptime |
---|---|---|
Friday | June 24 | 100.00 % |
Thursday | June 23 | 100.00 % |
Wednesday | June 22 | 100.00 % |
Tuesday | June 21 | 100.00 % |
Monday | June 20 | 100.00 % |
Table of Contents
|
Jun 25
|
Jun 24
|
Jun 23
|
Jun 22
|
Jun 21
|
Jun 20
|
Jun 19
|
|
|
---|---|---|---|---|---|---|---|---|---|
|
|||||||||
|
|||||||||
|
|||||||||
|
Date | Status |
---|---|
4/28/2022 | UP |
4/29/2022 | UP |
4/30/2022 | UP |
5/1/2022 | UP |
5/2/2022 | UP |
5/3/2022 | UP |
5/4/2022 | UP |
5/5/2022 | UP |
5/6/2022 | UP |
5/7/2022 | UP |
5/8/2022 | UP |
5/9/2022 | UP |
5/10/2022 | UP |
5/11/2022 | UP |
5/12/2022 | UP |
5/13/2022 | UP |
5/14/2022 | UP |
5/15/2022 | UP |
5/16/2022 | UP |
5/17/2022 | UP |
5/18/2022 | UP |
5/19/2022 | UP |
5/20/2022 | UP |
5/21/2022 | UP |
5/22/2022 | UP |
5/23/2022 | UP |
5/24/2022 | UP |
5/25/2022 | UP |
5/26/2022 | UP |
5/27/2022 | UP |
5/28/2022 | UP |
5/29/2022 | UP |
5/30/2022 | UP |
5/31/2022 | UP |
6/1/2022 | UP |
6/2/2022 | UP |
6/3/2022 | UP |
6/4/2022 | UP |
6/5/2022 | UP |
6/6/2022 | UP |
6/7/2022 | UP |
6/8/2022 | UP |
6/9/2022 | UP |
6/10/2022 | UP |
6/11/2022 | UP |
6/12/2022 | UP |
6/13/2022 | UP |
6/14/2022 | UP |
6/15/2022 | UP |
6/16/2022 | UP |
6/17/2022 | UP |
6/18/2022 | UP |
6/19/2022 | UP |
6/20/2022 | UP |
6/21/2022 | UP |
6/22/2022 | UP |
6/23/2022 | UP |
6/24/2022 | UP |
6/25/2022 | UP |
6/26/2022 | UP |
Date | Status |
---|---|
4/28/2022 | UP |
4/29/2022 | UP |
4/30/2022 | UP |
5/1/2022 | UP |
5/2/2022 | UP |
5/3/2022 | UP |
5/4/2022 | UP |
5/5/2022 | UP |
5/6/2022 | UP |
5/7/2022 | UP |
5/8/2022 | UP |
5/9/2022 | UP |
5/10/2022 | UP |
5/11/2022 | UP |
5/12/2022 | UP |
5/13/2022 | UP |
5/14/2022 | UP |
5/15/2022 | UP |
5/16/2022 | UP |
5/17/2022 | UP |
5/18/2022 | UP |
5/19/2022 | UP |
5/20/2022 | UP |
5/21/2022 | UP |
5/22/2022 | UP |
5/23/2022 | UP |
5/24/2022 | UP |
5/25/2022 | UP |
5/26/2022 | UP |
5/27/2022 | UP |
5/28/2022 | UP |
5/29/2022 | UP |
5/30/2022 | UP |
5/31/2022 | UP |
6/1/2022 | UP |
6/2/2022 | UP |
6/3/2022 | UP |
6/4/2022 | UP |
6/5/2022 | UP |
6/6/2022 | UP |
6/7/2022 | UP |
6/8/2022 | UP |
6/9/2022 | UP |
6/10/2022 | UP |
6/11/2022 | UP |
6/12/2022 | UP |
6/13/2022 | UP |
6/14/2022 | UP |
6/15/2022 | UP |
6/16/2022 | UP |
6/17/2022 | UP |
6/18/2022 | UP |
6/19/2022 | UP |
6/20/2022 | UP |
6/21/2022 | UP |
6/22/2022 | UP |
6/23/2022 | UP |
6/24/2022 | UP |
6/25/2022 | UP |
6/26/2022 | UP |
Date | Status |
---|---|
4/28/2022 | UP |
4/29/2022 | UP |
4/30/2022 | UP |
5/1/2022 | UP |
5/2/2022 | UP |
5/3/2022 | UP |
5/4/2022 | UP |
5/5/2022 | UP |
5/6/2022 | UP |
5/7/2022 | UP |
5/8/2022 | UP |
5/9/2022 | UP |
5/10/2022 | UP |
5/11/2022 | UP |
5/12/2022 | UP |
5/13/2022 | UP |
5/14/2022 | UP |
5/15/2022 | UP |
5/16/2022 | UP |
5/17/2022 | UP |
5/18/2022 | UP |
5/19/2022 | UP |
5/20/2022 | UP |
5/21/2022 | UP |
5/22/2022 | UP |
5/23/2022 | UP |
5/24/2022 | UP |
5/25/2022 | UP |
5/26/2022 | UP |
5/27/2022 | UP |
5/28/2022 | UP |
5/29/2022 | UP |
5/30/2022 | UP |
5/31/2022 | UP |
6/1/2022 | UP |
6/2/2022 | UP |
6/3/2022 | UP |
6/4/2022 | UP |
6/5/2022 | UP |
6/6/2022 | UP |
6/7/2022 | UP |
6/8/2022 | UP |
6/9/2022 | UP |
6/10/2022 | UP |
6/11/2022 | UP |
6/12/2022 | UP |
6/13/2022 | UP |
6/14/2022 | UP |
6/15/2022 | UP |
6/16/2022 | UP |
6/17/2022 | UP |
6/18/2022 | UP |
6/19/2022 | UP |
6/20/2022 | UP |
6/21/2022 | UP |
6/22/2022 | UP |
6/23/2022 | UP |
6/24/2022 | UP |
6/25/2022 | UP |
6/26/2022 | UP |
Date | Status |
---|---|
4/28/2022 | UP |
4/29/2022 | UP |
4/30/2022 | UP |
5/1/2022 | UP |
5/2/2022 | UP |
5/3/2022 | UP |
5/4/2022 | UP |
5/5/2022 | UP |
5/6/2022 | UP |
5/7/2022 | UP |
5/8/2022 | UP |
5/9/2022 | UP |
5/10/2022 | UP |
5/11/2022 | UP |
5/12/2022 | UP |
5/13/2022 | UP |
5/14/2022 | UP |
5/15/2022 | UP |
5/16/2022 | UP |
5/17/2022 | UP |
5/18/2022 | UP |
5/19/2022 | UP |
5/20/2022 | UP |
5/21/2022 | UP |
5/22/2022 | UP |
5/23/2022 | UP |
5/24/2022 | UP |
5/25/2022 | UP |
5/26/2022 | UP |
5/27/2022 | UP |
5/28/2022 | UP |
5/29/2022 | UP |
5/30/2022 | UP |
5/31/2022 | UP |
6/1/2022 | UP |
6/2/2022 | UP |
6/3/2022 | UP |
6/4/2022 | UP |
6/5/2022 | UP |
6/6/2022 | UP |
6/7/2022 | UP |
6/8/2022 | UP |
6/9/2022 | UP |
6/10/2022 | UP |
6/11/2022 | UP |
6/12/2022 | UP |
6/13/2022 | UP |
6/14/2022 | UP |
6/15/2022 | UP |
6/16/2022 | UP |
6/17/2022 | UP |
6/18/2022 | UP |
6/19/2022 | UP |
6/20/2022 | UP |
6/21/2022 | UP |
6/22/2022 | UP |
6/23/2022 | UP |
6/24/2022 | UP |
6/25/2022 | UP |
6/26/2022 | UP |
Date | Status |
---|---|
4/28/2022 | UP |
4/29/2022 | UP |
4/30/2022 | UP |
5/1/2022 | UP |
5/2/2022 | UP |
5/3/2022 | UP |
5/4/2022 | UP |
5/5/2022 | UP |
5/6/2022 | UP |
5/7/2022 | UP |
5/8/2022 | UP |
5/9/2022 | UP |
5/10/2022 | UP |
5/11/2022 | UP |
5/12/2022 | UP |
5/13/2022 | UP |
5/14/2022 | UP |
5/15/2022 | UP |
5/16/2022 | UP |
5/17/2022 | UP |
5/18/2022 | UP |
5/19/2022 | UP |
5/20/2022 | UP |
5/21/2022 | UP |
5/22/2022 | UP |
5/23/2022 | UP |
5/24/2022 | UP |
5/25/2022 | UP |
5/26/2022 | UP |
5/27/2022 | UP |
5/28/2022 | UP |
5/29/2022 | UP |
5/30/2022 | UP |
5/31/2022 | UP |
6/1/2022 | UP |
6/2/2022 | UP |
6/3/2022 | UP |
6/4/2022 | UP |
6/5/2022 | UP |
6/6/2022 | UP |
6/7/2022 | UP |
6/8/2022 | UP |
6/9/2022 | UP |
6/10/2022 | UP |
6/11/2022 | UP |
6/12/2022 | UP |
6/13/2022 | UP |
6/14/2022 | UP |
6/15/2022 | UP |
6/16/2022 | UP |
6/17/2022 | UP |
6/18/2022 | UP |
6/19/2022 | UP |
6/20/2022 | UP |
6/21/2022 | UP |
6/22/2022 | UP |
6/23/2022 | UP |
6/24/2022 | UP |
6/25/2022 | UP |
6/26/2022 | UP |
Metrics
StatusCast’s engineers were alerted to an issue affecting some customers accessing the status.page version of the application. Engineers confirmed that a certificate renewal was not properly propagated to all servers. This did not impact customers utilizing the statuscast.com domain or those utilizing a custom domain name.
Once we were made aware of this issue the updated certificate was pushed out directly to all instances. At this point service should be operating as expected for all users, however if you continue to experience any issues please contact support@statuscast.com.
StatusCast's engineers were alerted that schedule maintenance events created from StatusCast's legacy application("V2") were not properly auto-closing after their estimated duration had been reached. After an initial investigation engineers have confirmed the cause on the service responsible and a patch was performed to correct the error. Any maintenance that was overdue for closure should have been resolved and StatusCast's engineers will continue to monitor the legacy process for this to ensure no other issues occur.