Armalytix Outage History

Armalytix is up right now

Pingoru has recorded 5 incidents for Armalytix: 5 in the last 12 months and 0 in the last 90 days.

Source: status.armalytix.com

5incidents recorded
5last 12 months
0last 90 days
5 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Armalytix in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202623 of 720 (0%)
May 202616 of 744 (1%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 582 (0%)

Incidents, newest first

Minor May 5, 2026 Users reporting issues logging into armalytix. 6h 12m Consumer Journey, APIs, Corporate Portal

Started May 05, 2026, 10:47 AM UTC· resolved May 05, 2026, 04:59 PM UTC

  1. investigating May 05, 2026, 10:47 AM UTC

    Currently under investigation

  2. monitoring May 05, 2026, 11:10 AM UTC

    Service has been restored and we continue to monitor.

  3. resolved May 05, 2026, 04:59 PM UTC

    Service remains stable and we are closing the incident.

Read the full incident report →

Minor April 21, 2026 Client Statement Scanning unavailable 3h 8m Corporate Portal

Started Apr 21, 2026, 09:31 AM UTC· resolved Apr 21, 2026, 12:39 PM UTC

  1. investigating Apr 21, 2026, 09:31 AM UTC

    We're currently experiencing issues with Client Statement Scanning. The issue is under investigation.

  2. resolved Apr 21, 2026, 12:39 PM UTC

    Client Statement Scanning has recovered.

Read the full incident report →

Notice December 26, 2025 Intermittent issues retrieving risk insights 10h 56m

Started Dec 26, 2025, 08:06 AM UTC· resolved Dec 26, 2025, 07:02 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major November 18, 2025 Armalytix APIs not reachable 3h 51m

Started Nov 18, 2025, 11:37 AM UTC· resolved Nov 18, 2025, 03:28 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →