Omni CMS Outage History

Omni CMS is up right now

Pingoru has recorded 2 incidents for Omni CMS: 2 in the last 12 months and 1 in the last 90 days.

Source: omniupdate.status.io

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

Incidents, newest first

Minor August 6, 2026 Accessibility Check / Insights Accessibility Report / Calendar Management / Personalization Management 23m Modern Campus CMS, Modern Campus CMS Insights, Modern Campus CMS Personalization, Modern Campus CMS Calendar and 2 more

Started Aug 06, 2026, 06:58 PM UTC· resolved Aug 06, 2026, 07:22 PM UTC

  1. investigating Aug 06, 2026, 06:58 PM UTC

    We are investigating issues with Accessibility Check, Calendar Management, Insights Accessibility Report, and Personalization Management

Read the full incident report →

Critical May 27, 2026 Website Search Distruption 3h 53m Modern Campus CMS Website Search, Modern Campus CMS Website Search (Modern Campus CMS Website Search — Primary Data Center)

Started May 27, 2026, 06:04 PM UTC· resolved May 27, 2026, 09:57 PM UTC

  1. investigating May 27, 2026, 06:04 PM UTC

    We are currently investigating an issue affecting our website search service hosted at websitesearch.moderncampus.net. As a result, search functionality is temporarily unavailable for clients using our website search service. Clients will experience failed search results while using website search features. Our team identified the disruption and has engaged our external service provider to assist with resolution efforts. We are actively monitoring the situation and working with the external service provider to restore normal service as quickly as possible.

  2. monitoring May 27, 2026, 06:08 PM UTC

    We have contacted our external service provider, who has applied a fix. We will continue to monitor the health of the application.

  3. monitoring May 27, 2026, 06:17 PM UTC

    Our external service provider is investigating the root cause and monitoring the fix. Once we have more information and confirm the issue is resolved, we will share our findings.

Read the full incident report →