Validis Outage History

Validis is up right now

Pingoru has recorded 51 incidents for Validis: 13 in the last 12 months and 2 in the last 90 days.

Source: status.validis.com

51incidents recorded
13last 12 months
2last 90 days
3 daystypical duration
Incidents per month
024AprMayJunJulAugSepOctNov1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Validis 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 202600 of 720 (0%)
May 20263169 of 744 (23%)
June 2026169 of 720 (10%)
July 202617 of 744 (1%)
August 202628 of 744 (1%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202610 of 131 (0%)

Incidents, newest first

Minor November 21, 2024 Validis UK: Error message when starting Month End Reconciliation 4d 3h Validis UK

Started Nov 21, 2024, 02:22 PM UTC· resolved Nov 25, 2024, 05:39 PM UTC

  1. investigating Nov 21, 2024, 02:22 PM UTC

    We are currently aware of an intermittent issue where some customers are receiving an error when trying to view data or start their Month End Reconciliation through the Validis Portal. We advise affected users to wait a couple a of minutes before refreshing their browser and trying again. Our technical team are investigating as a matter of urgency. We will continue to provide you updates via this status page. We apologise for any inconvenience caused.

  2. investigating Nov 21, 2024, 05:31 PM UTC

    We are continuing to investigate this issue.

  3. investigating Nov 21, 2024, 09:40 PM UTC

    We are currently aware of an intermittent issue where some customers are receiving an error when trying to view data or start their month-end reconciliation through the Validis Portal. We advise affected users to sign out, refresh their browser, and try again. Our technical team is continuing to investigate this issue as a high priority. We apologize for any inconvenience caused.

  4. monitoring Nov 22, 2024, 02:24 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Nov 25, 2024, 05:39 PM UTC

    This incident has been resolved.

Read the full incident report →