Last checked: 5 minutes ago
Get notified about any outages, downtime or incidents for SimpliGov and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for SimpliGov.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
SendGrid API v3 | Active |
Preproduction | Active |
API | Active |
Authorization | Active |
Email Interaction | Active |
eSignature | Active |
Export | Active |
File Conversion | Active |
Metaquery | Active |
Portal | Active |
SimpliSign | Active |
Submission | Active |
Production | Active |
API | Active |
Authorization | Active |
Email Interaction | Active |
eSignature | Active |
Export | Active |
File Conversion | Active |
Metaquery | Active |
Portal | Active |
SimpliSign | Active |
Submission | Active |
Staging | Active |
API | Active |
Authorization | Active |
Email Interaction | Active |
eSignature | Active |
Export | Active |
File Conversion | Active |
Metaquery | Active |
Portal | Active |
SimpliSign | Active |
Submission | Active |
Training | Active |
API | Active |
Authorization | Active |
Email Interaction | Active |
eSignature | Active |
Export | Active |
File Conversion | Active |
Metaquery | Active |
Portal | Active |
SimpliSign | Active |
Submission | Active |
View the latest incidents for SimpliGov and check for official updates:
Description: **Preliminary Root Cause:** SimpliGov utilizes Azure App Configuration and key vault for secret sharing with authentication services. The key required for authentication between SimpliGov services rotated and stalled during rotation, causing the 502 status code errors noted. **Mitigation:** SimpliGov support manually rotated the key required and have gathered logs to investigate the matter further **Next Steps:** We apologize for the impact to affected customers. SimpliGov will continue to monitor the situation going forward and will identify the underlying rotation stall issue. All customer records being processed throughout the incident period should be consistent with their expected statuses. Customers do not need to take any reconciliatory actions in their production tenants unless they were directly notified to do so by the SimpliGov team.
Status: Postmortem
Impact: Major | Started At: Feb. 15, 2022, 12:26 a.m.
Description: Between 11:15 AM and 11:19 AM, SimpliGov users noted 502 Gateway Unavailable errors when navigating to SimpliGov via web browser. SimpliGov engineers identified the issue and resolved it by 11:19 AM. The application gateway load balancer received several health notifications from underlying applications which were actually in a healthy state. SimpliGov is following up with the application gateway vendor (Microsoft Azure Government) to investigate why such health notices occurred despite having valid underlying applications.
Status: Resolved
Impact: None | Started At: Feb. 4, 2022, 7:37 p.m.
Description: This incident has been resolved and the Azure service affected has resumed normal operations.
Status: Resolved
Impact: Minor | Started At: Feb. 3, 2022, 12:37 a.m.
Description: Customer dashboard backlogs have been processed and records should be in their accurate statuses.
Status: Resolved
Impact: Minor | Started At: Jan. 19, 2022, 11:11 p.m.
Description: **Preliminary Root Cause:** SimpliGov auto-submit retry batching occurred during a recent period of instability, causing a significant backlog of records to process across all customers. Due to the backlog size and time to horizontally scale, customers experienced degraded submission times and potential 504 errors on submission. **Mitigation:** SimpliGov support determined the cause of the issue and manually scaled capacity by adding more nodes and additional submission pods to expedite auto-submit processing for the submission backlog. Dashboard sync processes were run to ensure that dashboards contained current and accurate data. **Next Steps:** We apologize for the impact to affected customers. SimpliGov will continue to monitor the situation going forward. All customer records being processed throughout the incident period should be consistent with their expected statuses. Customers do not need to take any reconciliatory actions in their production tenants unless they were directly notified to do so by the SimpliGov team.
Status: Postmortem
Impact: Minor | Started At: Jan. 18, 2022, 6:16 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.