All systems are operational

About This Site

Welcome at Fonzer’s statuspage. On this page you will find the status of our Cloud Communications platform, including maintenance updates and incidents.

Reporting an issue

If you wish to report an unmentioned issue with one of our services, please raise a ticket at support.fonzer.com

Incident Status

Investigating: We have reports of a problem and are currently investigating.
Identified: We have identified the issue and are currently working on a fix.
Watching: We have executed a fix and are currently monitoring the situation.
Resolved: The fix was successful. The incident is resolved and closed.

Component Status

Operational: The component is working, no issues have been reported.
Performance Issues: The component is working, but some performance issues can be experienced.
Partial Outage: The component may not be working for everybody. For example this could be a geographical issue.
Major Outage: The component is not working for anybody.

PBX

Registrations

Operational

Incoming Calls

Operational

Outgoing Calls

Operational

Internal Calls

Operational

BLF

Operational

Qaller App

Operational

Web Calls

Operational

Trunks

Registrations

Operational

Web Interfaces

Panel

Operational

API

Operational

Other

Network

Operational

Past Incidents

4th June 2023

No incidents reported

3rd June 2023

No incidents reported

2nd June 2023

Incoming Calls Incoming calls to Queue

Incoming calls to queue might be delayed or have audio issues when picked up. We are currently investigating and working on a solution. Incoming calls that don't land on a queue don't seem to be affected.

Recent tests proved no more issues with the queues.

Panel Panel response is occasionally slow and queues have performance issues

Panel occasionally does not load all assets.

All issues have been resolved, no more incidents reported.

The performance issues of the panel seem to be resolved.

We are still awaiting official response of the interconnect party involved.

Issue has been identified as being caused by a nightly maintenance at our 3rd party cross-datacenter connect provider.