How Ombrik keeps millions of users informed during incidents

A status page people rely on at Ombrik

Updates that came too late

Ombrik’s users work in its apps all day. When sync or sign-in slowed down, they went looking for answers. The old status page was updated by hand, so it often showed everything as operational while support queues filled up.

Status tied to real checks

Ombrik now runs its public status page on Navy, on its own domain. Each component is backed by monitors that check web apps and sync APIs every 30 seconds from 18 regions. When an outage is confirmed from 3 regions, the component changes state and the incident timeline starts on its own.

Planned work, announced ahead

Enterprise admins asked for advance notice of maintenance. Ombrik schedules maintenance windows in Navy, and subscribers get an email before the work starts and when it ends. The 90-day uptime bars give admins a clear record to share with their own teams.

Details:

• Industry: Digital Media & Marketing
• Location: San Jose, California
• Employees: 29,000+
• Identity Provider: Okta
• Key Workloads: Public Status Page, Web Apps, Sync APIs

Ombrik’s status page now has more than 250,000 subscribers. During incidents, users check it first, and support teams spend their time on real issues instead of answering the same question.

---