All Systems Operational

Core Platform (B/W) Operational
90 days ago
100.0 % uptime
Today
Registrations Operational
90 days ago
100.0 % uptime
Today
Call Processing Operational
90 days ago
100.0 % uptime
Today
API Connectivity Operational
90 days ago
100.0 % uptime
Today
DMS Operational
Voicemail Operational
Netherlands Interconnect Operational
Service Provisioning Operational
Anywhere Portal Operational
Commpilot Operational
Anywhere with Webex Operational
Application Operational
PSTN Calling Operational
Push Notifications Operational
Meetings Operational
Control Hub Operational
Anywhere with MS Teams Operational
Registrations Operational
PSTN Calling Operational
Admin Portal Operational
Microsoft Operational
Anywhere Recording (Dubber) Operational
Portal Operational
Recording Operational
API Operational
Anywhere Integrator (Mondago) Operational
Go Cara Operational
Go Int Operational
Anywhere Reporting (Akixi) Operational
Reporting Operational
Data collection Operational
Receptionist Clients Operational
Broadworks Operational
Anywhere Operational
Go-Operator Operational
Unity Operational
ACC (Anywhere Contact Centre) Operational
ACC - IVR Operational
Upstream Carriers Operational
90 days ago
100.0 % uptime
Today
UK Operational
US Operational
Rest of World Operational
EU Operational
90 days ago
100.0 % uptime
Today
Hospitality PMS Operational
Jazzware Operational
Tiger TMS Operational
OCOM - (Palladion) Operational
Portal Operational
Data collection Operational
Support Ticketing (Halo) Operational
Portal Operational
HD Talk Conference Bridge Operational
Secure Call Operational
90 days ago
99.81 % uptime
Today
Calling Operational
90 days ago
99.63 % uptime
Today
Portal Operational
90 days ago
100.0 % uptime
Today
TalkDesk Operational
90 days ago
100.0 % uptime
Today
TalkDesk - Core Operational
90 days ago
100.0 % uptime
Today
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.

Scheduled Maintenance

Removal of DDI's from STCM on Gamma Trunk - Phase 2 May 1, 2026 19:00 - May 2, 2026 01:00 BST

Reason: Due to recent Gamma incident, Gamma are going to be carrying out the mitigation work highlighted in the recent RFO whereby all numbers with the STCM prefix will be moved onto the endpoint with a view to removing STCM from the trunk once numbers have been removed. This is the 2nd phase with the 1st phase being completed on 30th April 2026.

Impact: Each DDI will be unavailable for 1-2 mins as it is removed from STCM and updated with the prefix for the endpoint.

Checks: Gamma will check all DDI's now have the new endpoint prefix instead of the STCM prefix.

Rollback: Batches will be reviewed if any failures, remove the problematic numbers and re-run the batch file.

User actions: No action required from end users

Posted on Apr 28, 2026 - 16:53 BST

STCM Removal from Gamma Trunk - Number Migration to Enhanced Trunk - Phase 3 May 2, 2026 13:00-23:00 BST

Reason: As phase 1 & phase 2 have been completed and all DDI's now have an endpoint prefix, DDI's can be migrated to the enhanced trunk. This will be carried out in batches of 1000.

Impact: There is no impact to the DDI's when migrating based on a prefix change between two endpoints and no product removal. Calls will continue on the old route until the new route is applied.

Checks: Periodic checks throughout the process will take place to ensure DDI's are migrating successfully

Rollback: No rollback plan required. Checks on prefixes will be undertaken before this work starts to ensure no failures during migration

User actions: No user actions are required for this work.

Posted on Apr 29, 2026 - 10:43 BST

Legacy Network Decommission May 5, 2026 21:00-22:00 BST

As previously communicated, we have been phasing out our legacy network in preparation for its permanent decommission.

On Friday 6th March, the legacy network reached end of support. We will be carrying out our final decommission activity on 5th May, after which the legacy network will go permanently offline.

IMPORTANT: Any devices still connected to the legacy network will lose connectivity to the Evolve IP platform after this date. Migration is the only available resolution — no alternative remediation options exist.

We have taken a snapshot of all remaining registrations and will be sharing this with partners by end of play Tuesday 21st April.

If you have any questions or require assistance with your migration, please don't hesitate to get in touch.

Posted on Apr 20, 2026 - 14:06 BST

BYOC SIP interconnect work EvolveIP and Talkdesk May 5, 2026 21:00-23:00 BST

Reason:
As part of our ongoing efforts to maintain optimal performance, increase reliability, and improve monitoring and troubleshooting capabilities, we will be performing scheduled maintenance on the BYOC SIP interconnect between EvolveIP and Talkdesk.

Impact:
We do not expect any service interruption.

Checks:
Conduct post‑maintenance validation checks to confirm that the service is operating as expected.

Rollback Plan:
If any unforeseen issues are identified after the maintenance, we will revert the configuration changes to return the service to its last known stable and fully operational state.

User Actions:
No user actions required

Posted on Apr 20, 2026 - 14:15 BST
May 1, 2026
Completed - The scheduled maintenance has been completed.
May 1, 01:00 BST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 30, 19:00 BST
Scheduled - Reason: Due to recent Gamma incident, Gamma are going to be carrying out the mitigation work highlighted in the recent RFO whereby all numbers with the STCM prefix will be moved onto the endpoint with a view to removing STCM from the trunk once numbers have been removed. This will be a phased approach with half of the numbers (30k) being moved during this window and the remaining half being moved during another maintenance window (Friday 1st May).

Impact: Each DDI will be unavailable for 1-2 mins as it is removed from STCM and updated with the prefix for the endpoint.

Checks: Gamma will check all DDI's now have the new endpoint prefix instead of the STCM prefix.

Rollback: Batches will be reviewed if any failures, remove the problematic numbers and re-run the batch file.

User actions: No action required from end users

Apr 28, 16:51 BST
Apr 30, 2026
Apr 29, 2026
Resolved - This incident has been resolved.
Apr 29, 16:44 BST
Monitoring - A fix has been implemented, and we are monitoring the results.

Please retest, and if any further issues are experienced, please raise a ticket with the support team.

Apr 29, 14:39 BST
Update - The vendor is continuing to investigate the issue.

At this time, we can confirm that data is not currently affected. However, there is a risk of data loss during remediation work by the vendor.

We apologise for any inconvenience this may cause.

Apr 29, 14:11 BST
Investigating - We are currently investigating an issue affecting users who encounter an error when logging into the Akixi portal.

This has been escalated to the vendor as a priority for further investigation.

We will provide an update as soon as more information becomes available.

Apr 29, 13:42 BST
Apr 28, 2026
Completed - This maintenance will be rescheduled for a later date
Apr 28, 09:54 BST
Scheduled - Description:
We will be replacing the current profile servers to improve overall reliability and performance.

Customer impact:
A temporary disruption will occur during the restart. Users may experience temporary registration issues or minor call routing delays during this time.

Mar 30, 12:20 BST
Apr 27, 2026
Completed - The scheduled maintenance has been completed.
Apr 27, 23:00 BST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 27, 22:00 BST
Scheduled - Akixi will be performing a scheduled upgrade to the product tonight to improve performance and reliability.

This release upgrades your service from version 3.4.0.2 to 3.5.2.3 and includes quality-of-life improvements and bug fixes to enhance usability and overall performance.

Please note this upgrade applies exclusively to the Akixi CX Analytics for Microsoft Teams product.

Impact
During this time, some users may experience brief interruptions or reduced performance.


We apologise for the late notice and any inconvenience this may cause, and appreciate your understanding.

Apr 27, 10:23 BST
Apr 26, 2026

No incidents reported.

Apr 25, 2026

No incidents reported.

Apr 24, 2026
Resolved - This incident is now marked as Resolved
Apr 24, 14:20 BST
Update - The carrier has completed their investigation into finding the affected numbers and resolved any issues with these.

Please can we now get the customer to test any previously affected numbers and confirm if there are now working.

Thank you for your patience throughout this time.

Apr 16, 12:20 BST
Update - The carrier is still identifying the remaining impacted numbers. Evolve IP are still supplying the numbers which are provided by our customers.

Evolve IP will also be having a call with the carrier to get an eta to resolution which will be provided once recevied.

Apr 16, 11:20 BST
Update - We have received an update from the carrier. They are currently working through the list we have been provided by our customers of impacted numbers and they will resolve these manually throughout the morning.

The carrier is now identifying which numbers are still affected and compiling a list so they can resolved. They will be providing an update at 11:00. This status page will be updated shortly after.

Apr 16, 10:19 BST
Update - We have been informed of sporadic numbers still not correctly work. If your customers have numbers which are not working, please can the relevant Halo ticket be updated and we will collate this and work with the carrier.

We are expecting an update from the carrier at 10:00, this status page will be updated shortly after.

Apr 16, 09:25 BST
Update - The carrier has now successfully completed the bulk upload of the affected numbers.

Could we now work with your customers to confirm if the affected numbers are now routing as expected.

Apr 15, 20:34 BST
Update - The carrier has now uploaded 71% of affected numbers.

Please continue to test numbers periodically to check if they are now back in service.

Apr 15, 19:40 BST
Update - The carrier has now uploaded 52% of affected numbers. There was a slight drop in performance due to standard migrations taking place, however, now these are completed and we are outside of business hours, they are hoping to process more uploads over the next few hours.
Apr 15, 18:35 BST
Update - Following the previous update, providing the bulk upload continues to progress successfully without any issues encountered, we will be looking at all numbers being uploaded by approx. 21:00 today. This is only an estimate based on current progress as well as no issues being encountered during the upload. Once this is complete, we expect all numbers to be available and routing as expected.

Evolve IP would like to thank our partners and customers for their help and understanding throughout this major incident.

Apr 15, 17:46 BST
Update - Latest update on the bulk upload progress. The carrier is currently 40% through the list of numbers.

We will continue to update hourly. Please continue to test numbers periodically to check if they are now back in service.

Apr 15, 17:32 BST
Update - Bulk upload of numbers has started and the carrier is 20% through the list of numbers.

There will continue to be hourly updates on progress. Please continue to test numbers periodically to check if they are now back in service.

Apr 15, 16:23 BST
Update - The carrier has been able to find a way to bulk upload numbers to the trunk and ensure each number uploaded has the correct routing profile. They will be starting this work with immediate effect.

Unfortunately there is no ETA to when this work will be completed so there will be a progress update provided here hourly to state the progress. We are currently unable to say when each number affected will be uploaded so it would be advisable to periodically check affected numbers to see if they are back in service.

Further update will be provided on progress.

Apr 15, 14:59 BST
Update - We have received a batch of numbers from the carrier which are now back on the trunk and should be routing calls as normal. Halo tickets are in the process of being updated for customers to test and confirm.

Carrier is also in the process of identifying a way to bulk upload impacted numbers to make the required connections and route calls as expected. Further update to be provided on progress at 14:15.

Apr 15, 13:48 BST
Update - We are continuing to share affected numbers with the carrier, and they are actively working through these to restore service as a priority.

We understand the impact this may be having and are continuing to push for a more efficient resolution process. We will keep you informed as we receive further updates and as additional numbers are successfully restored.

Apr 15, 11:32 BST
Update - We are continuing to share affected numbers with the carrier, and they are actively working through these to restore service.

We understand the impact this may be having and are continuing to push for a more efficient resolution process. We will keep you informed as we receive further updates and as additional numbers are successfully restored.

Apr 15, 10:30 BST
Update - We are being made aware of numbers that are not routing through. We have been advised by the carrier to inform them of these numbers so we can pass to the carrier while they are working through the list of numbers to check the routing. While this is not ideal, we are working with the carrier to find a more efficient way of getting the remaining numbers routing again.

We will update further shortly.

Apr 15, 09:39 BST
Update - We are continuing to monitor to try to identify the remaining numbers that continue to fail to route. Please monitor and raise a ticket if you identify a number which is failing to route inbound.
Apr 15, 08:14 BST
Monitoring - Extensive monitoring and testing has been conducted to try and identify remaining numbers that continue to fail to route. As yet we've been unable to find a number which fails to route correctly, suggesting we're now BAU. Please monitor and raise a ticket if you identify a number which is failing to route inbound.
Apr 15, 02:35 BST
Update - Our carrier is still working through the numbers to ensure they route correctly. We will continue to update as they progress.
Apr 14, 20:43 BST
Update - Our carrier has advised they've finished their work, however we're still seeing some numbers failing to route. We've requested they work through each number and ensure they route, but in the meantime please raise a ticket with any numbers you've identified as not routing. We'l pass these through to the carrier to ensure they're added as a priority.
Apr 14, 19:17 BST
Identified - Please be advised that the previously communicated incident regarding inbound calling has not been fully resolved. We've been advised that the carrier is working through each number systematically to restore inbound service for the numbers impacted. Apologies for the confusion. We'll communicate more as soon as we have it.
Apr 14, 18:47 BST
Apr 23, 2026
Completed - The scheduled maintenance has been completed.
Apr 23, 00:00 BST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 22, 22:00 BST
Scheduled - This maintenance will onboard the UK NetScaler pair into the central management system. During the process, the appliances will be patched and licensed to ensure compliance with Citrix requirements and to support future automated upgrades.

Impact:
A brief service interruption may be observed in Akixi during node failover.

Apr 21, 18:24 BST
Apr 22, 2026
Completed - The scheduled maintenance has been completed.
Apr 22, 00:00 BST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 21, 22:00 BST
Scheduled - Description:
We will be upgrading the current production profiles servers as part of preparation for migration to OL9 servers.

Customer impact:
Customers are not expected to experience any service interruption, as servers will be updated sequentially. Users might be required to log back into their WebEx clients.

Mar 30, 12:12 BST
Apr 21, 2026
Apr 20, 2026

No incidents reported.

Apr 19, 2026

No incidents reported.

Apr 18, 2026

No incidents reported.

Apr 17, 2026

No incidents reported.