Is OmniChat down?

Last checked 1m ago
Current status
OmniChat is up

No incidents right now.

Get alerts when OmniChat breaks →

Free · no credit card

Official status page: https://status.omni.chat · Polled every 5 minutes · 27 components tracked

Real-time OmniChat status, recent outages, and incident history — pulled directly from OmniChat's official status page at https://status.omni.chat every 5 minutes. Pingoru tracks 27 OmniChat services and has captured 9 incidents in the last 90 days (99.55% uptime). Get email, Slack, Discord, or webhook alerts the moment OmniChat reports a new incident — free for 5 monitors, no credit card.

Users who monitor OmniChat also follow these eCommerce services: Shopify Stripe PayPal Blackbaud NetSuite Squarespace BigCommerce Cybersource Gorgias PayFast View all 6,000+ providers
OmniChat uptime 99.55% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Instabilidade nas conversas do Whizz
    Resolved 4h 22m
    Started Apr 28, 2026, 09:43 PM UTC · Resolved Apr 29, 2026, 02:06 AM UTC
    Whizz Agent
    4 updates · show timeline
    • monitoring · Apr 28, 2026, 09:43 PM UTC

      Encontramos um problema no Whizz em que as conversas ficaram confusas ou trouxeram informações não pertinentes ao escopo de atuação. A ocorrência durou poucos minutos, pois foi resolvida prontamente. No momento, estamos monitorando o serviço.

    • monitoring · Apr 28, 2026, 09:47 PM UTC

      We are continuing to monitor for any further issues.

    • resolved · Apr 29, 2026, 02:06 AM UTC

      Informamos que, após o período de monitoramento, não identificamos novos comportamentos atípicos e o sistema está estável. Lamentamos o transtorno e agradecemos sua compreensão. A confiabilidade de nossa plataforma é a prioridade máxima da OmniChat, por isso, seguimos trabalhando em melhorias contínuas para oferecer a melhor experiência possível. Um postmortem com o detalhamento técnico do incidente será publicado nos próximos dias.

    • postmortem · Apr 29, 2026, 01:44 PM UTC

      **O que aconteceu?** Entre 17:02 e 17:31 do dia 28 de abril, houve um problema na plataforma em que uma degradação no funcionamento do Whizz resultou em falhas no processamento de mensagens. Como consequência, algumas conversas apresentaram respostas confusas ou com informações não aderentes ao escopo esperado, impactando a experiência dos clientes. A ocorrência teve curta duração e foi rapidamente identificada e corrigida pelo time.   **Causa Raiz:** Às 17:02, foi realizada uma atualização na plataforma. Essa atualização visava melhorar o tempo de resposta do agente através da execução simultânea do processamento de mensagens. Entretanto, esse cenário levou a uma condição de concorrência, na qual múltiplas mensagens foram processadas fora da ordem esperada. Como resultado, houve inconsistência no contexto das conversas, fazendo com que algumas respostas fossem geradas com informações incorretas ou não relacionadas ao fluxo esperado.   **Resolução e prevenção:** O time de Engenharia acompanhou a atualização em tempo real e, ao identificar a inconsistência no processamento das mensagens, iniciou imediatamente a atuação para mitigação. Após a identificação do comportamento incorreto, foi realizada a reversão para a versão anterior, cuja conclusão aconteceu às 17:31, normalizando o funcionamento da plataforma. Para evitar a recorrência do problema e aumentar a confiabilidade do processo, serão adotadas as seguintes ações: * Evolução do processo de testes automatizados, com maior cobertura para cenários de concorrência e processamento simultâneo, incluindo paridade de carga em ambiente de _staging_; * Implementação de mecanismos de controle na troca de mensagens, garantindo a ordenação e a consistência no processamento, com travas de segurança para evitar cenários semelhantes; * Revisão do processo de implantação de atualizações críticas visando mitigar impactos na operação.

    Latest: **O que aconteceu?** Entre 17:02 e 17:31 do dia 28 de abril, houve um problema na plataforma em que uma degradação no funcionamento do Whizz resultou em falhas no processamento de …

See the full OmniChat outage history

6 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 4 incidents
  • Instabilidade nas conversas do Whizz Resolved
    Started Apr 28, 2026, 09:43 PM UTC · Resolved Apr 29, 2026, 02:06 AM UTC · 4h 22m
  • Indisponibilidade nos atendimentos do Whizz Resolved
    Started Apr 17, 2026, 12:08 PM UTC · Resolved Apr 17, 2026, 08:22 PM UTC · 8h 13m
  • Instabilidade na plataforma Resolved
    Started Apr 14, 2026, 09:27 PM UTC · Resolved Apr 15, 2026, 12:58 AM UTC · 3h 31m
  • Lentidão envio de mensagem whizz Resolved
    Started Apr 14, 2026, 03:13 PM UTC · Resolved Apr 14, 2026, 11:44 PM UTC · 8h 31m

See OmniChat in your Pingoru dashboard

Monitor OmniChat alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add OmniChat to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every OmniChat incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just OmniChat or see every provider at once.

Maintenance calendar

Scheduled OmniChat maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every OmniChat status change, one inbox

Pingoru watches OmniChat's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

OmniChat reports on 27 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route OmniChat alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming OmniChat maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy OmniChat services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching OmniChat from the same account, with per-user notification preferences for any monitor.

Get notified on OmniChat status changes

Pingoru watches OmniChat's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring OmniChat free

Monitor OmniChat along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add OmniChat and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track OmniChat uptime & incident history

See 90 days of OmniChat uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See OmniChat uptime history

Frequently asked questions

What is OmniChat's uptime?
Over the last 90 days, OmniChat reported 99.55% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.omni.chat — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see OmniChat's uptime history rolling forward in real time.
Has OmniChat had outages in 2026?
Yes — OmniChat has had 9 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last OmniChat outage?
The most recent OmniChat incident was "Instabilidade nas conversas do Whizz", which started on April 28, 2026 and was resolved on April 29, 2026. Pingoru captured this directly from https://status.omni.chat. See the full incident card above for affected components and the update timeline.
How often does OmniChat have outages?
Based on the last 90 days, OmniChat averages 3.0 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is OmniChat's status page?
OmniChat's official status page is https://status.omni.chat. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is OmniChat down right now?
OmniChat is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment OmniChat reports a change. Current status is based on 27 tracked services.
How does Pingoru know if OmniChat is down?
We read https://status.omni.chat directly, using OmniChat's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when OmniChat has an outage?
Create a free Pingoru account and add OmniChat as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
OmniChat's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real OmniChat incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real OmniChat issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official OmniChat status?
We use OmniChat's own status page at https://status.omni.chat. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Up" mean?
All tracked OmniChat components are reporting operational. No incidents are currently affecting service.

Stop finding out from your users.

We watch OmniChat's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor OmniChat free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →