Rabbit Outage History

Rabbit major outage · 1 active incident View live status →

Rabbit had 4 outages in the last 2 years totaling 509h 54m of downtime, averaging 0.2 incidents per month.

There were 4 Rabbit outages since September 23, 2025 totaling 509h 54m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.rabbit.nl

Minor June 12, 2026

Degraded Performance: Outbound WhatsApp Messaging Failures

Detected by Pingoru
Jun 12, 2026, 01:54 PM UTC
Resolved
Jun 12, 2026, 05:39 PM UTC
Duration
3h 45m
Affected: Rabbit Messenger (Outgoing WhatsApp messages)
Timeline · 2 updates
  1. investigating Jun 12, 2026, 01:54 PM UTC

    We have identified an issue impacting our WhatsApp outbound messaging service. This appears to be related to an upstream issue with the WhatsApp/Meta API, causing message delivery failures and high latency. Impact: Delayed or failed delivery for outgoing WhatsApp messages. Current Action: We are monitoring Meta's status updates closely and working to mitigate the impact on our routing layer where possible. We appreciate your patience and will keep this page updated with real-time progress as Meta resolves the underlying issue.

  2. resolved Jun 12, 2026, 05:39 PM UTC

    Meta has officially confirmed that the upstream issues impacting the WhatsApp Cloud API have been fully resolved and services are restored. Our system metrics have completely returned to normal, and all outbound WhatsApp messaging is functioning as expected. Any message backlogs that built up during the peak of the outage have now fully cleared. Current State: 100% Operational. Action Required: None. All messaging services are running normally. Thank you so much for your patience and understanding while we monitored this disruption!

Read the full incident report →

Minor February 24, 2026

Messenger environments experiencing issues

Detected by Pingoru
Feb 24, 2026, 08:05 AM UTC
Resolved
Feb 24, 2026, 08:46 AM UTC
Duration
41m
Affected: Rabbit Messenger (Rabbit Messenger)Rabbit Messenger (Incoming WhatsApp messages)
Timeline · 2 updates
  1. investigating Feb 24, 2026, 08:05 AM UTC

    Some Messenger environments are currently experiencing issues in using the environments, sending and receiving messages. We're aware of the issues and are working on a resolution.

  2. resolved Feb 24, 2026, 08:46 AM UTC

    All systems are back operational.

Read the full incident report →

Minor December 11, 2025

WhatsApp emoji reactions not showing in Rabbit Messenger

Detected by Pingoru
Dec 11, 2025, 02:32 PM UTC
Resolved
Jan 01, 2026, 02:48 PM UTC
Duration
21d
Affected: Rabbit Messenger (Incoming WhatsApp messages)
Timeline · 2 updates
  1. investigating Dec 11, 2025, 02:32 PM UTC

    Earlier today we became aware of an issue where in some cases, emoji reactions to sent messages will not show in Rabbit Messenger. We are currently investigating and are in contact with Meta regarding this issue. We will update once we have more information.

  2. resolved Jan 01, 2026, 02:48 PM UTC

    Meta has marked this issue as solved.

Read the full incident report →

Minor September 23, 2025

KPN Network Performance Degradation

Detected by Pingoru
Sep 23, 2025, 09:27 AM UTC
Resolved
Sep 23, 2025, 10:39 AM UTC
Duration
1h 12m
Affected: Rabbit Messenger (Rabbit Messenger)Rabbit Messenger (Plugins)Rabbit Messenger (Incoming WhatsApp messages)
Timeline · 2 updates
  1. investigating Sep 23, 2025, 09:27 AM UTC

    Summary We are currently investigating an issue causing degraded service performance for customers connecting through the KPN network in the Netherlands. Impact Users on the KPN network may be experiencing slow response times, intermittent connection errors, and timeouts when accessing our services. The issue appears to be specific to users on this network provider. Core services remain operational, but performance is significantly impacted for those affected.

  2. resolved Sep 23, 2025, 10:39 AM UTC

    KPN has resolved the issue. All services should be available again.

Read the full incident report →