Arch systems status page

At approximately 11:00am EDT, all services began experiencing higher than normal response times. Service metrics and performance returned to normal following a rollback at 12:04pm EDT. Later, Arch Portal encountered additional issues beginning at 1:55pm EDT, which were resolved by 2:26pm EDT. Further analysis into these incidents is ongoing. We apologize for any inconvenience caused.

Intercom is used to provide Arch’s customer support chat. This service is experiencing intermittent disruptions as a result of underlying issues in AWS’s us-east-1 region today. Please email support@arch.co directly to reach customer support.

Arch’s Client API was unavailable between 9:26am EDT and 10:26am EDT. This incident was related to this morning’s Arch Portal outage. The incident is mitigated at this time. A detailed postmortem analysis is underway, and additional details will be available soon.

Edit: incident duration and end time was revised on 10/10 based on postmortem analysis findings.

Arch’s Portal was unavailable this morning starting at 8:10am EDT. The incident was mitigated at 9:45am EDT. A detailed postmortem analysis is underway, and additional details will be available soon. We apologize for the inconvenience.

All Arch systems will be briefly offline around 8pm EST to facilitate scheduled production server maintenance.

Issue identified: The Arch LP Portal arch.co/portal returned a 503 for all users, denying access to the service.

Resolved(4:04pm Eastern Time): A slightly older version of this service was successfully deployed, granting access to the service again. At 4:23pm the root cause of this issue was fixed.

Issue identified: users were incorrectly redirected to arch.co after login

Resolved(2:00pm EST): The root cause of this issue was discovered and fixed. This issue affected all users.

–

Issue identified: users see a blank screen after logging in.

Update: we are continuing to investigate this issue.

Issue identified: Arch resources, including our website, were temporarily unavailable. (13:05 — Mar 28)
Resolved: All services are up and appear stable.

Issue identified: Our public website was temporarily unavailable. User portal and all other parts of system are not affected. (17:30 — Apr 8)
Resolved: All services are up and appear stable.

Issue identified: Our user portal and public website are unreachable. We are investigating. (23:01 — Mar 1)
Resolved: All services are up and appear stable.