All Systems Operational
Business Voice — Canada Operational
Customer Voice Server #1 (Canada) Operational
Customer Voice Server #2 (Canada) Operational
Customer Voice Server #3 (Canada) Operational
Customer Voice Server #4 (Canada) Operational
Customer Voice Server #5 (Canada) Operational
Customer Voice Server #6 (Canada) Operational
Customer Voice Server #7 (Canada) Operational
Customer Voice Server #8 (Canada) Operational
Customer Voice Server #9 (Canada) Operational
Customer Voice Server #10 (Canada) Operational
Customer Voice Server #11 (Canada) Operational
Customer Voice Server #12 (Canada) Operational
Inbound Calls — Local Partner A (Canada) Operational
Inbound Calls — Local Partner B (Canada) Operational
Inbound Calls — Local Partner C (Canada) Operational
Inbound Calls — Local Partner D (Canada) Operational
Inbound Calls — Local Partner E (Canada) Operational
Inbound Calls — Local Partner F (Canada) Operational
Inbound Calls — Local Partner G (Canada) Operational
Inbound Calls — Local Partner H (Canada) Operational
Inbound Calls — Local Partner I (Canada) Operational
Inbound Calls — Local Partner J (Canada) Operational
Inbound Calls — Local Partner K (Canada) Operational
Inbound Calls — All Local Partners (Canada) Operational
Outbound Calls (Canada) ? Operational
Business Fax — Canada Operational
Inbound Fax (Canada) Operational
Outbound Fax (Canada) Operational
Business SMS — Canada Operational
Inbound SMS (Canada) Operational
Outbound SMS (Canada) Operational
Business Voice — United States Operational
Customer Voice Server #1 (United States) Operational
Inbound Calls — Local Partner E (United States) Operational
Inbound Calls — Local Partner I (United States) Operational
Inbound Calls — Local Partner K (United States) Operational
Inbound Calls — All Local Partners (United States) Operational
Outbound Calls (United States) ? Operational
Business Fax — United States Operational
Inbound Fax (United States) Operational
Outbound Fax (United States) Operational
Business SMS — United States Operational
Inbound SMS (United States) Operational
Outbound SMS (United States) Operational
Business UC — Global Operational
Chat Operational
Presence Operational
Video Conferencing Operational
Click-to-dial Browser Plug-in Operational
Management — Global Operational
Customer Portal (Studio) Operational
Device Provisioning Operational
Customer API Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Jun 23, 2017

No incidents reported today.

Jun 22, 2017
Resolved - (english below)

Cher client,

Nous avons obtenu confirmation de la part de notre partenaire local dans la région de Montréal que les difficultés éprouvées sur leur réseau plus tôt aujourd'hui devraient avoir cessé et que le service vers vos numéros sans-frais (1-800) devrait maintenant aussi être revenu à la normale.

Le problème se serait déclaré à 14h21 et aurait été résolu à 15h56.

Nous tentons maintenant d'obtenir un rapport de panne plus complet de la part du partenaire en question. D'ici là, si vous nécessitez plus d'information sur ce problème, n'hésitez pas à nous envoyer un courriel à support@ubity.com.

Nous sommes désolé des inconvénients que ce problème aurait pu vous causer.

Composante(s) affectée(s): Inbound Calls — Local Partner A (Canada), Inbound Calls — Local Partner B (Canada)

***

Dear customer,

We have gotten confirmation from our local partner in the Montreal area that the issue they have been having on their network has been resolved and that service to your toll-free (1-800) numbers should now also be fully restored.

The issue started at 2:21PM and was resolved at 3:56PM.

We are now awaiting a more complete outage report from our local partner. In the meantime, should you require more information on this particular issue, please send us an e-mail at support@ubity.com.

Please accept our sincere apologies for this inconvenience.

Affected component(s): Inbound Calls — Local Partner A (Canada), Inbound Calls — Local Partner B (Canada)
Jun 22, 16:02 EDT
Update - (english below)

Cher client,

Nous avons obtenu confirmation de la part de notre partenaire local dans la région de Montréal que le service devrait être complètement rétabli sur vos numéros de téléphone locaux dans cette région, et ce depuis 15h15. Toutefois, des problèmes intermittents perdureraient toujours pour certains numéros sans-frais (1-800).

Plus de détails suivront sous peu.

Merci de votre compréhension.

Composante(s) affectée(s): Inbound Calls — Local Partner A (Canada), Inbound Calls — Local Partner B (Canada)

***

Dear customer,

We have gotten confirmation from our local partner in the Montreal area that service to your local phone numbers in this area should have been restored since 3:15PM. Nevertheless, intermittent issues could still be experienced on certain toll-free (1-800) numbers.

More details will follow shortly.

Thank you for your understanding.

Affected component(s): Inbound Calls — Local Partner A (Canada), Inbound Calls — Local Partner B (Canada)
Jun 22, 15:52 EDT
Identified - (english below)

Cher client,

Un de nos partenaires locaux dans la grande région de Montréal éprouve présentement des difficultés sur leur réseau, ce qui pourrait avoir un impact sur vos numéros de téléphone dans cette région, ainsi que sur certains de vos numéros sans-frais (1-800).

Nous demeurons en contact étroit avec leur équipe technique jusqu'au rétablissement complet du service.

Nous sommes désolé des inconvénients que ce problème pourrait vous causer.

Composante(s) affectée(s): Inbound Calls — Local Partner A (Canada), Inbound Calls — Local Partner B (Canada)

***

Dear customer,

One of our local partners in the greater Montreal area is currently experiencing an issue on their network which could impact some of your local DIDs in that area, as well as some of your toll-free (1-800) numbers.

We are in close contact with their support team and they are actively working on a quick resolution.

Please accept our sincere apologies for this inconvenience.

Affected component(s): Inbound Calls — Local Partner A (Canada), Inbound Calls — Local Partner B (Canada)
Jun 22, 14:21 EDT
Jun 21, 2017

No incidents reported.

Jun 20, 2017

No incidents reported.

Jun 19, 2017

No incidents reported.

Jun 18, 2017

No incidents reported.

Jun 17, 2017

No incidents reported.

Jun 16, 2017

No incidents reported.

Jun 15, 2017

No incidents reported.

Jun 14, 2017

No incidents reported.

Jun 13, 2017

No incidents reported.

Jun 12, 2017

No incidents reported.

Jun 11, 2017

No incidents reported.

Jun 10, 2017

No incidents reported.

Jun 9, 2017

No incidents reported.