Visit TTNC

Subscribe

All systems are functional.

Past incidents

Saturday 26th March 2016

Nothing to report

Friday 25th March 2016

Nothing to report

Thursday 24th March 2016

Nothing to report

Wednesday 23rd March 2016

Scheduled Maintenance, scheduled 10 years ago

This is an important notice concerning our VoIP services.

From the 31st March 2016, we will provide all Caller IDs in the standard E.164 format, e.g. +442031511000.

This change will only affect you if you are using the Caller ID in some way. For example, you are using a CRM system in conjunction with your PBX. The PBX recognises Caller IDs so your CRM displays your customers details. Or you might be using Caller IDs as part of a Dial Plan in your PBX.

Tuesday 22nd March 2016

TTNC Status Update

Resolved:

The faults responsible for yesterdays disruption to calls, including difficulties experienced in applying changes to numbers, have now been resolved. Customers should no longer be experiencing any difficulties.

If you believe your service may still be affected. Please get in touch with our support team who will be more than happy to help.

Monday 21st March 2016

Intermittent issues.

UPDATE

We are continuing to monitor our systems.

Intermittent issues.

UPDATE

We are continuing to notice intermittent issues with some calls.

We are still monitoring our systems and trying to prevent these issues.

Intermittent issue.

UPDATE

We believe calls are connecting currently as they should.

We are continuing to monitor the systems.

Intermittent issue.

We are still aware of intermittent issues with calls.

The tech team are currently looking into the this and trying to resolve the issues.

Intermittent issue.

We have become aware of intermittent issues regarding calls.

Calls

This morning we experienced some issues with our upstream carrier and some inbound and outbound calls were affected.

We believe these issues are now rectified.

Inbound Calls

Some customers may have experienced issues with inbound calls on their TTNC numbers. This was due to an upstream carrier issue which is now resolved.

We will continue to monitor the the situation.

Sunday 20th March 2016

Nothing to report