ArcSite Outage History

ArcSite is up right now

Pingoru has recorded 3 incidents for ArcSite: 2 in the last 12 months and 0 in the last 90 days.

Source: status.arcsite.com

3incidents recorded
2last 12 months
0last 90 days
under a minutetypical duration

Incidents, newest first

Minor March 24, 2026 Request high latency – User Site, API

Started Mar 24, 2026, 08:55 PM UTC· resolved Mar 24, 2026, 08:55 PM UTC

  1. resolved Mar 24, 2026, 08:55 PM UTC

    Our database is experiencing a high request load, so some requests may be laggy or even time out. We’ve put in some temporary tweaks to address this and everything should be OK now, and a more robust solution is on the way.

Read the full incident report →

Notice March 6, 2026 Service Disruption Due to Unexpected Memory Exhaustion 23s

Started Mar 06, 2026, 02:08 PM UTC· resolved Mar 06, 2026, 02:09 PM UTC

  1. investigating Mar 06, 2026, 02:08 PM UTC

    At approximately 05:00 UTC on March 6, our service experienced a temporary disruption caused by a sudden surge of abnormal requests that led to excessive memory usage and exhausted available system memory. This resulted in the service becoming unavailable for a short period. As an immediate mitigation, we enabled zram-based swap on the affected hosts to provide additional compressed memory buffering and improve resilience against sudden memory spikes. The service has since been restored and is operating normally. Our team is continuing to investigate the root cause of the abnormal request pattern and will implement further safeguards once the underlying issue is identified. We will provide additional updates if new information becomes available.

  2. resolved Mar 06, 2026, 02:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 27, 2025 Message Queue Outage Causing Web/API Downtime –

Started Jun 27, 2025, 05:00 PM UTC· resolved Jun 27, 2025, 05:00 PM UTC

  1. resolved Jun 27, 2025, 05:00 PM UTC

    our production system experienced a significant service disruption resulting in widespread 502 errors and unresponsiveness across both the website and APIs. The root cause was traced to a failure in the message queue service (RabbitMQ), which led to timeouts when dispatching asynchronous tasks.

Read the full incident report →