Callbell Outage History

Callbell is up right now

Callbell had 9 outages in the last 2 years totaling 2h 57m of downtime — averaging 0.4 incidents per month.

There were 9 Callbell outages since July 6, 2025 totaling 2h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.callbell.eu

Minor June 16, 2026

Media send failing (error 500) - WhatsApp Cloud API

Detected by Pingoru
Jun 16, 2026, 03:36 PM UTC
Resolved
Jun 16, 2026, 05:18 PM UTC
Duration
1h 41m
Affected: WhatsApp Integration
Timeline · 4 updates
  1. investigating Jun 16, 2026, 03:36 PM UTC

    Meta Cloud API is having issues in sending medias. We are currently investigating this incident. For updates check

  2. identified Jun 16, 2026, 05:12 PM UTC

    We are continuing to work on a fix for this incident.

  3. monitoring Jun 16, 2026, 05:12 PM UTC

    We implemented a fix and are currently monitoring the result.

  4. resolved Jun 16, 2026, 05:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 12, 2026

WhatsApp Cloud API - Issues sending messages

Detected by Pingoru
Jun 12, 2026, 02:01 PM UTC
Resolved
Jun 12, 2026, 03:17 PM UTC
Duration
1h 16m
Affected: Web DashboardMobile AppPublic APIAnalyticsFacebook IntegrationWhatsApp IntegrationInstagram IntegrationTelegram Integration
Timeline · 4 updates
  1. investigating Jun 12, 2026, 02:01 PM UTC

    Meta is having issues in sending messages through WhatsApp Cloud API. We are currently investigating this incident.

  2. identified Jun 12, 2026, 02:11 PM UTC

    Meta is continuing having a distributed outage. We are continuing to work on a fix for this incident.

  3. monitoring Jun 12, 2026, 03:17 PM UTC

    We implemented a fix and are currently monitoring the result.

  4. resolved Jun 12, 2026, 03:17 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 8, 2026

Platform slowness

Detected by Pingoru
Apr 08, 2026, 02:40 PM UTC
Resolved
Apr 08, 2026, 02:40 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 08, 2026, 02:40 PM UTC

    Type: Incident Duration: 15 minutes Affected Components: WhatsApp Integration, Telegram Integration, Mobile App, Analytics, Public API, Instagram Integration, Facebook Integration, Web Dashboard Apr 8, 14:40:06 GMT+0 - Investigating - We are currently investigating this incident. Apr 8, 14:51:12 GMT+0 - Identified - We are continuing to work on a fix for this incident. Apr 8, 14:55:06 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor February 27, 2026

Platform issues

Detected by Pingoru
Feb 27, 2026, 02:12 PM UTC
Resolved
Feb 27, 2026, 02:12 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Feb 27, 2026, 02:12 PM UTC

    Type: Incident Duration: 41 minutes Affected Components: Mobile App, Web Dashboard Feb 27, 14:34:36 GMT+0 - Identified - We are continuing to work on a fix for this incident. Feb 27, 14:41:54 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Feb 27, 14:53:30 GMT+0 - Resolved - This incident has been resolved. Feb 27, 14:12:35 GMT+0 - Investigating - We are currently investigating this incident.

Read the full incident report →

Minor February 25, 2026

Platform slowdowns

Detected by Pingoru
Feb 25, 2026, 07:27 PM UTC
Resolved
Feb 25, 2026, 07:27 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Feb 25, 2026, 07:27 PM UTC

    Type: Incident Duration: 35 minutes Affected Components: Mobile App, Web Dashboard Feb 25, 19:27:35 GMT+0 - Investigating - We are currently investigating this incident. Feb 25, 19:32:29 GMT+0 - Identified - We are continuing to work on a fix for this incident. Feb 25, 19:48:50 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Feb 25, 20:02:38 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Major October 2, 2025

Major outage

Detected by Pingoru
Oct 02, 2025, 02:00 PM UTC
Resolved
Oct 02, 2025, 02:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 02, 2025, 02:00 PM UTC

    Type: Incident Duration: 2 hours and 14 minutes Affected Components: Public API, Analytics, Facebook Integration, WhatsApp Integration, Instagram Integration, Telegram Integration, Mobile App, Web Dashboard Oct 2, 16:14:32 GMT+0 - Resolved - This incident has been resolved. Oct 2, 15:32:02 GMT+0 - Identified - We are continuing to work on a fix for this incident. Oct 2, 14:00:46 GMT+0 - Investigating - We are currently investigating this incident. Oct 2, 15:57:19 GMT+0 - Monitoring - The app is working again, but chat counters are unavailable for now.

Read the full incident report →

Major July 23, 2025

WhatsApp QR unavailable

Detected by Pingoru
Jul 23, 2025, 10:34 PM UTC
Resolved
Jul 23, 2025, 10:34 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jul 23, 2025, 10:34 PM UTC

    Type: Incident Duration: 1 hour and 37 minutes Affected Components: WhatsApp Integration Jul 23, 23:55:53 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 23, 23:55:03 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jul 23, 22:34:48 GMT+0 - Investigating - We are currently investigating this incident. Jul 24, 00:11:39 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Major July 6, 2025

Dashboard currently unavailable

Detected by Pingoru
Jul 06, 2025, 09:18 PM UTC
Resolved
Jul 06, 2025, 09:18 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jul 06, 2025, 09:18 PM UTC

    Type: Incident Duration: 3 hours and 20 minutes Affected Components: Instagram Integration, WhatsApp Integration, Facebook Integration, Telegram Integration, Mobile App, Analytics, Public API, Web Dashboard Jul 7, 00:20:32 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 7, 00:38:01 GMT+0 - Resolved - This incident has been resolved. Jul 6, 21:18:15 GMT+0 - Investigating - We are currently investigating this incident. Jul 7, 00:20:02 GMT+0 - Identified - We are continuing to work on a fix for this incident.

Read the full incident report →