LawLytics Outage History

LawLytics is up right now

Pingoru has recorded 13 incidents for LawLytics: 1 in the last 12 months and 0 in the last 90 days.

Source: status.lawlytics.com

13incidents recorded
1last 12 months
0last 90 days
6 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking LawLytics 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 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 508 (0%)

Incidents, newest first

Critical November 18, 2025 Partial Outage Caused by Infrastructure Provider 5h 57m Customer Sites, Platform (CMS), Analytics

Started Nov 18, 2025, 12:05 PM UTC· resolved Nov 18, 2025, 06:03 PM UTC

  1. identified Nov 18, 2025, 12:05 PM UTC

    We’re currently experiencing a partial outage caused by a downstream issue with one of our infrastructure provider. Our team is actively monitoring the situation and will provide updates as soon as services are restored.

  2. identified Nov 18, 2025, 12:17 PM UTC

    We are still experiencing a partial outage caused by a downstream issue with one of our infrastructure provider. Our team is actively monitoring the situation and will provide updates as soon as services are restored.

  3. monitoring Nov 18, 2025, 04:23 PM UTC

    A fix has been implemented by our infrastructure provider and we are monitoring the results.

  4. resolved Nov 18, 2025, 06:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 20, 2025 Major Outage Caused by Vendor Issue 2h 59m Customer Sites, Platform (CMS), Analytics

Started Oct 20, 2025, 04:37 PM UTC· resolved Oct 20, 2025, 07:37 PM UTC

  1. identified Oct 20, 2025, 04:37 PM UTC

    We’re currently experiencing a major outage caused by a downstream issue with one of our vendors (AWS). Our team is actively monitoring the situation and will provide updates as soon as services are restored.

  2. identified Oct 20, 2025, 04:39 PM UTC

    We are continuing to monitor the issue.

  3. identified Oct 20, 2025, 04:41 PM UTC

    We’re continuing to monitor the situation, as vendor services remain impacted by the outage.

  4. identified Oct 20, 2025, 04:42 PM UTC

    We’re continuing to monitor the situation.

  5. monitoring Oct 20, 2025, 05:13 PM UTC

    We’re actively monitoring system stability, vendor services remain affected by the outage.

  6. monitoring Oct 20, 2025, 05:15 PM UTC

    Vendor services remain affected by the ongoing outage. We’re actively monitoring the situation.

  7. resolved Oct 20, 2025, 07:37 PM UTC

    This incident has been resolved.

Read the full incident report →