All Systems Operational

Uptime over the past 90 days. View historical uptime.
Authentication Operational
90 days ago
100.0 % uptime
Today
Virtual Contact Centre Operational
90 days ago
100.0 % uptime
Today
User Interface Operational
90 days ago
100.0 % uptime
Today
Voice Ingress Operational
90 days ago
100.0 % uptime
Today
WebChat Ingress/Egress Operational
90 days ago
100.0 % uptime
Today
Email Ingress Operational
90 days ago
100.0 % uptime
Today
SMS Ingress Operational
90 days ago
100.0 % uptime
Today
Payments Operational
90 days ago
100.0 % uptime
Today
Voice Egress Operational
90 days ago
100.0 % uptime
Today
AI Chat Bot Operational
90 days ago
100.0 % uptime
Today
SMS Egress Operational
90 days ago
100.0 % uptime
Today
Manager Pro UI Operational
90 days ago
100.0 % uptime
Today
Data Capture Operational
90 days ago
100.0 % uptime
Today
Wall Boards Operational
90 days ago
100.0 % uptime
Today
Online Statistics Operational
90 days ago
100.0 % uptime
Today
Call Recording Operational
90 days ago
100.0 % uptime
Today
Voicemail Operational
90 days ago
100.0 % uptime
Today
Automated Dialler / Callback Lists Operational
90 days ago
100.0 % uptime
Today
PSTN Voice Platform Operational
90 days ago
100.0 % uptime
Today
Hubbub Voip Platform Operational
90 days ago
99.98 % uptime
Today
Telecoms/Data Network Operational
AWS ec2-eu-west-2 Operational
AWS s3-eu-west-2 Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Jul 30, 2026

No incidents reported today.

Jul 29, 2026

No incidents reported.

Jul 28, 2026

No incidents reported.

Jul 27, 2026

No incidents reported.

Jul 26, 2026

No incidents reported.

Jul 25, 2026

No incidents reported.

Jul 24, 2026

No incidents reported.

Jul 23, 2026

No incidents reported.

Jul 22, 2026

No incidents reported.

Jul 21, 2026

Call failures on the voice platform — two call-processing nodes unresponsive (21 July 2026, 14:35–15:47 BST)
Resolved - On 21 July 2026 between 14:35 and 15:47 BST, the voice platform experienced a major degradation in call handling. Two processing servers entered a state in which they accepted new calls but could not progress them: callers experienced failed calls, unanswered ringing, or silent calls that could not be hung up. Because the affected servers continued to respond to routine health checks, the platform's load balancer continued to route calls to them and as their reported load figures froze, an increasing share of traffic was directed at the most-affected server as it was reporting the lowest load. By 15:00 the majority of new calls were failing. Calls handled by the remaining healthy servers continued to work normally throughout.

Service was restored by restarting the two affected servers at 15:45. The faulty component has been disabled until the underlying defect and the integration defect are both fixed. We are additionally: adding alerting that detects this failure signature within minutes; hardening the call-processing servers to automatically recover if call handling stalls; changing the routing layer to stop sending calls to servers whose health data has gone stale.

We are sorry for the disruption this caused.
Jul 21, 15:00 BST

Jul 20, 2026

No incidents reported.

Jul 19, 2026

No incidents reported.

Jul 18, 2026

No incidents reported.

Jul 17, 2026

No incidents reported.

Jul 16, 2026

Additional Hubbub IP Platform Updates
Completed - The scheduled maintenance has been completed.
Jul 16, 04:00 BST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 15, 22:00 BST
Scheduled - Following last nights planned maintenance we need to undertake minor follow up work to optimise some features added in the upgrade package.

This maintenance is not expected to cause any impact on ongoing calls or service, however softphone users may notice their Hubbub VoIP softphones de-register and re-register over a very short period; 1 to 15 seconds at most. If this happens the green tick on their softphone may briefly turn into a red cross, then revert to a green tick.

If your softphone does not re-register for any reason, please refresh your VCC page or close and reopen your installed application, whichever is appropriate.
Jul 15, 15:54 BST
← Incident History Powered by Atlassian Statuspage