Incidents | QContact Ltd

Media 7 Health Event

Sat, 17 May 2025 10:59:00 -0000

This incident has been resolved. The underlying host experienced hardware failure within Azure, and the server was re-provisioned on an alternative host.

Media 7 Health Event

Sat, 17 May 2025 10:55:00 -0000

Investigating

Azure ZA North Connectivity

Wed, 14 May 2025 10:47:00 -0000

Update from Azure: What happened? Between 23:30 UTC on 13 May 2025 and 08:20 UTC on 14 May 2025, you were identified as an Azure customer in the South Africa North and South Africa West regions who may have experienced intermittent connectivity loss and increased network latency. What went wrong, and why? A third-party telecom network disruption in the affected regions was identified as a contributing factor to this event. How did we respond? 23:30 UTC on 13 May 2025 - Customer impact began. 03:30 UTC on 14 May 2025 - As customer reports increased, we were alerted to the issue and promptly began our investigation. 05:00 UTC on 14 May 2025 - We identified that the issue was due to a third-party network disruption in the affected regions. 08:20 UTC on 14 May 2025 - We confirmed that the issue was self-healed with no need for manual intervention. We confirmed that customer impact was mitigated, and service functionality was fully restored. What happens next? This Mitigation Statement is the final communication for this incident. For details about which Azure incidents qualify for which Post Incident Reviews (PIRs), refer to https://aka.ms/AzurePIRs. The impact times above represent the full incident duration, so are not specific to any individual customer. Actual impact to service availability may vary between customers and resources – for guidance on implementing monitoring to understand granular impact: https://aka.ms/AzPIR/Monitoring. To stay informed about future Azure service issues, make sure that you configure and maintain Azure Service Health alerts – these can trigger emails, SMS, push notifications, webhooks, and more: https://aka.ms/ash-alerts. For broader guidance on preparing for cloud incidents, refer to https://aka.ms/incidentreadiness.

Azure ZA North Connectivity

Wed, 14 May 2025 09:16:00 -0000

Azure have added a service advisory https://app.azure.com/h/5_YX-JWG/8ffce0 Starting at 23:30 UTC on 13 May 2025, you were identified as an Azure customer in the South Africa North and South Africa West region who may have experienced intermittent connectivity loss and increased network latency in the region. This issue is now mitigated. Further details will be provided shortly.

Azure ZA North Connectivity

Wed, 14 May 2025 08:27:00 -0000

We see DNS recovery and international connectivity restored. We will continue to monitor

Azure ZA North Connectivity

Wed, 14 May 2025 06:38:00 -0000

An outage is occurring with Azure DNS infrastructure in South Africa North. We have implemented a workaround to use external DNS infrastructure. We also note international connectivity issues into ZA North from outside South Africa. We await details from Azure.

Azure ZA North Connectivity

Wed, 14 May 2025 06:18:00 -0000

We are investigating connectivity from Azure ZA North

Database Failover

Wed, 19 Mar 2025 07:31:00 -0000

This was caused by the automatic application of a critical security update. We have adjusted the automatic security update process to ensure failover fully completes before updates are applied. We apologise for the inconvenience caused.

Database Failover

Wed, 19 Mar 2025 07:11:00 -0000

At 06:52:59 a database server failed. An automatic recovery was started and completed by 06:54:36

Telkom Mobile Inbound Calling

Thu, 06 Mar 2025 07:52:00 -0000

This issue appears to have been resolved and calls are successfully connecting.

Telkom Mobile Inbound Calling

Thu, 06 Mar 2025 05:10:00 -0000

We are aware of an issue where Telkom Mobile customers in South Africa are unable to dial certain inbound numbers provided by QContact. This issue is within Telkom's network, and a fault has been raised on why the interconnect is failing.

Kenya Numbering

Tue, 11 Feb 2025 05:00:32 +0000

Maintenance completed

Kenya Numbering

Tue, 11 Feb 2025 02:30:32 -0000

Please be aware of a maintenance window for Kenyan numbering by the upstream Carrier between 5:30am and 8:00am East Africa Time. There may be intermittent disruptions to service during this period.

Angani Voice

Thu, 06 Feb 2025 11:49:00 -0000

Service is resolved to normal levels - we have not received details from Angani yet as to the cause.

Angani Voice

Thu, 06 Feb 2025 11:23:00 -0000

We are aware of a disruption at Angani in Kenya. Awaiting feedback

WhatsApp Disruption

Wed, 05 Feb 2025 17:17:00 -0000

We await an RCA from Meta, but have been informed this was due to an unannounced code change at Meta which changed the way webhooks (used for incoming messages) were sent. This prevented 360dialog from receiving the messages in the correct format, and forwarding them to the correct recipient. 360Dialog setup a workaround for accounts which only had a single number on the WABA while awaiting Meta to reverse the change. The clients who only had a single number on their WABA recovered at around 9:30am UTC. Those who had multiple numbers started to recover around 2 hours later at 11:20 UTC. We have been informed that messages sent during the disruption *can not* be retrieved, as they were not stored by Meta or 360Dialog for data protection reasons. We understand this is very disappointing news to hear, and have communicated this back - but there is unfortunately no way to recover these. If we receive a formal RCA, we will publish it for our clients.

WhatsApp Disruption

Wed, 05 Feb 2025 14:33:00 -0000

360Dialog have confirmed the issue is resolved, but we await further confirmation of more details.

WhatsApp Disruption

Wed, 05 Feb 2025 14:22:00 -0000

Meta have advised the issue is resolved on their status page, but awaiting official comms from 360Dialog "We have recovered from an earlier outage impacting Cloud API, and services have now been restored. We apologize for any inconvenience that this may have caused."

WhatsApp Disruption

Wed, 05 Feb 2025 11:20:00 -0000

We have started to receive messages from accounts which have multiple numbers under the same WABA. No official comms from Meta or 360Dialog at this time.

WhatsApp Disruption

Wed, 05 Feb 2025 09:41:00 -0000

We have started receiving a small amount of incoming messages. We understand only users who have a single number under the WABA will be receiving messages at this time.

WhatsApp Disruption

Wed, 05 Feb 2025 08:28:00 -0000

Update from Meta https://metastatus.com/whatsapp-business-api Some disruptions: Cloud API Feb 5 2025 9:11 AM GMT+1 Our engineering teams have identified the root cause of the medium disruptions impacting webhooks on WhatsApp Cloud API. We are currently deploying the fix and the expected deployment time is in 8hours. We will provide another update within 4 hours or sooner if additional information is available.

WhatsApp Disruption

Wed, 05 Feb 2025 07:29:00 -0000

Latest update from 360Dialog: We are monitoring the situation closely and waiting on Meta.

WhatsApp Disruption

Wed, 05 Feb 2025 00:10:00 -0000

Tracking on 360Dialog website: https://status.360dialog.com/cm6r59kif000nhwyo48km38ut

WhatsApp Disruption

Tue, 04 Feb 2025 22:30:00 -0000

Please note 360Dialog is experiencing an issue with incoming WhatsApp deliveries. Outbound messages are still being delivered.

Azure network disruption

Tue, 07 Jan 2025 13:28:00 -0000

Replacement redundancy is now also now back in place.

Azure network disruption

Tue, 07 Jan 2025 12:06:00 -0000

Azure have confirmed the issue is fully resolved with the following details.. Between 10:34 UTC and 11:05 UTC on 07 January 2025, a platform issue resulted in an impact to the Virtual Machines service in the South Africa North region. Impacted customers experienced connection failures when trying to access some VMs hosted in the region. These VMs may have also restarted unexpectedly. What went wrong, and why? During this incident, a top-of-rack (ToR) network device, connecting a single rack of servers, experienced an unexpected reboot, consequently the hosts connected to this ToR experienced a loss in connectivity. Customers may have been unable to connect to their resources and Virtual Machines (VMs) that were deployed on the affected resources may have experienced a restart.

Azure network disruption

Tue, 07 Jan 2025 11:03:00 -0000

Due to the network disruption in Azure North, we have moved all affected and degraded workloads on affected services away from unhealthy nodes. We will keep workloads away from problem resources until we see full service restored.

Azure network disruption

Tue, 07 Jan 2025 10:43:00 -0000

Failover is complete - more updates to come

Azure network disruption

Tue, 07 Jan 2025 10:41:00 -0000

Failover has been initiated on affected systems which will alleviate this issue. Updates to follow

Azure network disruption

Tue, 07 Jan 2025 10:30:00 -0000

We are aware of an issue affecting Azure clients. This is due to a national Azure outage affecting connectivity to our systems. Please see below Azure incident status: A network device has experienced a fault, resulting in network connectivity loss to downstream resources. The unhealthy network device is being isolated from the network and traffic is being rerouted to healthy infrastructure. Further updates can be viewed here: https://app.azure.com/h/9KP2-3_8/8ffce0

Meta Disruption

Thu, 12 Dec 2024 02:03:00 -0000

Meta have confirmed the update is resolved From - https://metastatus.com/whatsapp-business-api "We have recovered from an earlier outage impacting Cloud API, and services have now been restored. We apologize for any inconvenience that this may have caused."

Meta Disruption

Wed, 11 Dec 2024 18:34:00 -0000

Meta is currently experiencing disruption with their WhatsApp Business API, Instagram and Facebook Messenger APIs - for more information see https://metastatus.com/whatsapp-business-api We will automatically retry and failed deliveries. At present this is having limited to no impact on our customers, but we continue to monitor

Postmark API

Wed, 11 Dec 2024 02:40:00 -0000

The API has returned to normal. Any messages would have been queued our side and retried during the disruption.

Postmark API

Wed, 11 Dec 2024 02:19:00 -0000

Postmark is experiencing API issues again. We are monitoring

E-mail API

Wed, 04 Dec 2024 22:28:00 -0000

Update from Postmark: We've deployed additional fixes and latency/errors have returned to normal performance. Engineering will continue to monitor into the evening for consistent results.

E-mail API

Wed, 04 Dec 2024 21:56:00 -0000

Update from Postmark: We've confirmed the source of the issue and are implementing fixes. Latency and errors has been reduced but engineers are continuing to remedy the issue.

E-mail API

Wed, 04 Dec 2024 20:13:00 -0000

Postmark has notified us of some latency issues on their API again. Message delivery may be delayed, but no messages are being lost.

Delays on outgoing e-mail

Fri, 22 Nov 2024 03:19:00 -0000

Postmark have confirmed issues with their API which they now believe it to be mitigated. You can find more information at https://status.postmarkapp.com/notices/iejilmig3r9ldil5-increased-api-latency-timeouts

Delays on outgoing e-mail

Fri, 22 Nov 2024 02:18:00 -0000

Update from Postmark: Additional fixes have been deployed to remedy unhealthy API instances and are now recovering to their expected performance. We will continue to monitor before resolving this status.

Delays on outgoing e-mail

Thu, 21 Nov 2024 20:43:00 -0000

Update from Postmark: We are still experiencing latency issues with some API instances affecting a small subset of customers. The engineering team is continuing to investigate and remedy the issue. Updates will be provided as more information is available.

Delays on outgoing e-mail

Thu, 21 Nov 2024 17:19:00 -0000

Update from Postmark: A fix was deployed reducing latency and timeouts for unhealthy API instances. We are continuing to monitor while it recovers.

Delays on outgoing e-mail

Thu, 21 Nov 2024 17:06:00 -0000

For customers using the built-in e-mail functionality (those using Office 365 are unaffected), our e-mail provider is currently experiencing API instability. This may lead to delays in e-mails being sent, as we automatically retry to deliver your messages. We await further details from our e-mail provider (Postmark)

SA Network Disruption

Wed, 06 Nov 2024 12:43:00 -0000

The situation has continued to remain stable. During the disruption period, 1.04% of requests resulted in a timeout due to the network issues according to 3rd party monitoring.

SA Network Disruption

Wed, 06 Nov 2024 10:54:00 -0000

Between approximately 2am and 10:40am there have been network connectivity issues with certain ISPs within South Africa accessing OVH's network in Europe (across multiple datacentres). You can see the network effect for a sample ISP here - https://lon1-eri.smokeping.ovh.net/smokeping??&target=EMEA.AS10474& This appears to now have stabilised. However if you continue to experience problems, please contact support as we have the ability to re-route your traffic over a working international link. We encourage all users within South Africa still using OVH UK data locations, to request the migration of your data to Azure SA.

MTN and Liquid Telecom Interconnect

Wed, 23 Oct 2024 07:11:00 -0000

This has been confirmed as resolved.

MTN and Liquid Telecom Interconnect

Wed, 23 Oct 2024 06:16:00 -0000

Liquid confirm the issue has been raised with MTN as a priority issue, but no ETA on resolution at present

MTN and Liquid Telecom Interconnect

Tue, 22 Oct 2024 15:14:00 -0000

We are aware of an interconnection issue between Liquid Telecom and MTN. This is disrupting outbound and inbound calls using 060 numbers and MTN. This is due to a failure of an SS7 link between the carriers. We have no ETA yet on resolution. Please note, this is a carrier issue rather than something within QContact's control. This affects all traffic between Liquid Telecom and MTN.

Azure & OVH Interconnect

Thu, 17 Oct 2024 16:00:00 -0000

Between 13:14 UTC and 13:19 UTC there was a brief network connectivity issue between Azure LHR, Azure JNB and OVH LON where connections where stalled or timed out. For any customer whose voice is hosted in one of those Azure regions, but data is held in OVH London - this may have resulted in disruption to recordings. The issue was automatically resolved when the network connectivity resumed. This issue did not affect any other region than the ones listed.

Azure & OVH Interconnect

Thu, 17 Oct 2024 16:00:00 -0000

Azure Voice

Tue, 15 Oct 2024 09:50:00 -0000

This issue reoccured briefly between 11:41 and 11:49. Circuit breaker limits further increased as well as now being fully automated.

Azure Voice

Tue, 15 Oct 2024 09:50:00 -0000

This issue reoccured briefly between 11:41 and 11:49. Circuit breaker limits further increased as well as now being fully automated.

Azure Voice

Tue, 15 Oct 2024 09:50:00 -0000

This issue reoccured briefly between 11:41 and 11:49. Circuit breaker limits further increased as well as now being fully automated.

Azure Voice

Fri, 11 Oct 2024 12:44:00 -0000

This issue has been resolved. Connections to the platform were being throttled - this lead to slower refreshes and answering of calls. The throttle limits have been increased. The telemetry which monitors throttling wasn't correctly configured, meaning the limits were hit before an adjustment could be made. The limits have been increased to ensure no legitimate usage results in any further throttling.

Azure Voice

Fri, 11 Oct 2024 12:44:00 -0000

Azure Voice

Fri, 11 Oct 2024 12:44:00 -0000

Azure Voice

Fri, 11 Oct 2024 12:21:00 -0000

Reports of delays in being able to answer calls or successfully registering (phone spinning) on refresh in Azure regions.

Azure Voice

Fri, 11 Oct 2024 12:21:00 -0000

Reports of delays in being able to answer calls or successfully registering (phone spinning) on refresh in Azure regions.

Azure Voice

Fri, 11 Oct 2024 12:21:00 -0000

Reports of delays in being able to answer calls or successfully registering (phone spinning) on refresh in Azure regions.

Google API access

Mon, 12 Aug 2024 13:26:00 -0000

We see network connectivity is restored.

Google API access

Mon, 12 Aug 2024 13:21:00 -0000

We are aware of a network connectivity issue into Google's network affecting European user's ability to use DNS lookups, GCS cloud storage and access to Dialogflow APIs

Issues dialling South African mobile numbers

Sat, 10 Aug 2024 07:47:00 -0000

Calls have been re-routed via an alternative route while we await details from the upstream carrier.

Issues dialling South African mobile numbers

Sat, 10 Aug 2024 07:36:00 -0000

We are investigating issues dialling +278xxx numbers

SSO

Wed, 29 May 2024 08:13:00 -0000

The update has been fully deployed in all regions.

SSO

Wed, 29 May 2024 07:57:00 -0000

We are deploying an update to resolve this issue.

SSO

Wed, 29 May 2024 07:27:00 -0000

We are investigating an issue with Microsoft Entra ID SSO

Meta Service Issue

Wed, 03 Apr 2024 20:45:00 -0000

Meta have confirmed the issue is resolved. The fix for the outage impacting service on Cloud API has been deployed and this issue is now mitigated as of 04-03-2024 at 1:45 PM PST. Thank you for your patience.

Meta Service Issue

Wed, 03 Apr 2024 18:10:00 -0000

There is currently disruption with Meta services globally. This is affecting message delivery on Facebook, Instagram and WhatsApp. Waiting on an update from Meta who will post at https://metastatus.com/whatsapp-business-api

Azure South Africa Region

Mon, 18 Mar 2024 04:30:00 -0000

This incident has officially been closed by Azure now additional bandwidth is online the services are no longer at risk. If you require more information about this incident, please feel free to reach out to your account manager for more details.

Azure South Africa Region

Sat, 16 Mar 2024 17:13:00 -0000

Latest Update from Azure With the current bandwidth demand and network utilization, all services are currently healthy with no issues detected. We are still detecting some minor latency for small transient periods. In preparation for demand increases, we are on track to take all available measures to increase capacity. Substantial additional capacity remains on track to be provisioned by March 19, 2024. We continue to closely monitor all telemetry to ensure network stability leading into the South Africa region's business hours on Monday, March 18, 2024. The majority of Azure Services affected by this issue have returned to normal functionality. Customers should see recovery and minimal impact at this time. -- We continue to see a good level of service across all carriers other than Seacom. We also see significant improvements on zScaler CPT IV since around 09:30am local time in SA, which was the only monitored zScaler region in SA still affected.

Azure South Africa Region

Sat, 16 Mar 2024 00:18:00 -0000

Update from Azure is that international connectivity is restricted at present to 400Gbps, and they continue to experience issues with stability on additional capacity at this time. An additional 1Tbps of capacity is due online by Tuesday. We continue to see normal levels of service all on carriers other that Seacom.

Azure South Africa Region

Fri, 15 Mar 2024 20:23:00 -0000

As per our last update - we continue to see good service across Africa with the exception of Seacom which is still routing domestic traffic via Europe and USA. Latest Update from Azure: We have determined that multiple fiber cables on the West Coast of Africa — WACS, MainOne, SAT3, ACE — have been impacted which reduced total capacity supporting our Regions in South Africa. In addition to these cable impacts, the on-going cable cuts in the Red Sea — EIG, Seacom, AAE-1 — are also impacting overall capacity on the East Coast of Africa. These incidents together had reduced the total network capacity for most of Africa's regions. We've added the additional network capacity, however, there has been a slight amount of instability in the newly added links. We're working with the partner carrier to investigate the issues. Additionally, we're planning to add additional capacity within the region over the weekend and into next week to bring more headroom into the region. Once our additional capacity is stable, we plan to re-enable Azure Front Door (AFD) routing within the South Africa region to improve some application performance. As we continue to work on further increasing the capacity, our telemetry shows signs of recovery, and packet drops have reduced significantly. Many of the Azure Services that were affected by this issue earlier have now returned to normal functionality. We are validating for any remaining impacted services, however customers should notice considerable improvements.

Azure South Africa Region

Fri, 15 Mar 2024 14:37:00 -0000

Latest from Azure is they are experiencing difficulties still bringing the new capacity online and updated ETA is now 18:00 UTC. Connectivity across the board in South Africa remains good with the exception of Seacom.

Azure South Africa Region

Fri, 15 Mar 2024 07:12:00 -0000

We have seen normal levels of latency return on all Vodacom links. We are seeing issues remain with Seacom where capacity remains constrained. All other mainstream carriers and ISPs continue to show normal performance with low latency and zero packet loss. Updates to follow.

Azure South Africa Region

Fri, 15 Mar 2024 04:44:00 -0000

Azure now estimate this work to have completed by 14:00 UTC - we continue to monitor. Updates to follow.

Azure South Africa Region

Thu, 14 Mar 2024 22:54:00 -0000

We continue to see the issue limited to Vodacom and Seacom at this time. Azure have also updated the ETA back to 02:00 UTC for the additional capacity. Update from Azure Current Status: We have determined that multiple fiber cables on the West Coast of Africa — WACS, MainOne, SAT3, ACE — have been impacted which reduced total capacity supporting our Regions in South Africa. In addition to these cable impacts, the on-going cable cuts in the Red Sea — EIG, Seacom, AAE-1 — are also impacting overall capacity on the East Coast of Africa. These incidents together had reduced the total network capacity for most of Africa's regions. The overall network health for the region has been steadily improving. Many of the Azure Services that were affected earlier by this issue have now returned to their normal levels. We are still validating for any remaining services, however the users for these would already notice considerable improvements. We are working on adding more capacity and we anticipate that these steps will help further with ongoing capacity bottleneck. The new estimated time of completion for this activity is 2:00 UTC on 15 March 2024

Azure South Africa Region

Thu, 14 Mar 2024 19:58:00 -0000

We continue to see elevated latency to Seacom and Vodacom. While we see no other issues at present, should issues persist on Friday, for South African clients we have provisioned resources within Amazon Web Services in Cape Town, and are able to move voice service there on a temporary basis.

Azure South Africa Region

Thu, 14 Mar 2024 18:17:00 -0000

Update from Azure We have determined that multiple fiber cables on the West Coast of Africa — WACS, MainOne, SAT3, ACE — have been impacted which reduced total capacity supporting our Regions in South Africa. In addition to these cable impacts, the on-going cable cuts in the Red Sea — EIG, Seacom, AAE-1 — are also impacting overall capacity on the East Coast of Africa. These incidents together had reduced the total network capacity for most of Africa's regions. Our efforts through simultaneous workstreams to reduce non-critical traffic has helped to normalize the network bandwidth. We believe most of the customers should no longer be seeing impact and we are continuing to validate the health metrics across the Azure Services which were impacted initially. Our teams continue to work on bringing additional capacity to minimize any impact across services. We expect that this work should take about 4 hrs from now, which would be around 22:00 UTC on 14 March 2024.

Azure South Africa Region

Thu, 14 Mar 2024 17:18:00 -0000

International latency has now recovered to usual levels. Microsoft themselves continue to re-route local 365 resources to both Europe and South Africa West. We continue to see higher latency to Vodacom and Seacom, but packet loss is now zero on these links too.

Azure South Africa Region

Thu, 14 Mar 2024 15:42:00 -0000

We have seen significant improvements on international connectivity in the past 10 minutes. While latency is still around 35% higher than usual, we are currently seeing zero packet loss (down from up to 80% packet loss on international links earlier in the incident)

Azure South Africa Region

Thu, 14 Mar 2024 14:40:00 -0000

We have seen service largely restored domestically. We continue to see issues remain with ISPs that use Seacom or Vodacom for upstream connectivity or SIP trunks. We are also still seeing high international connectivity latency and packet loss, but significant improvement on earlier.

Azure South Africa Region

Thu, 14 Mar 2024 14:26:00 -0000

Azure Update Current Status: We have determined that multiple fiber cables on the West Coast of Africa -- WACS, MainOne, SAT3, ACE – have been impacted which reduced total capacity supporting our Regions in South Africa. In addition to these cable impacts, the on-going cable cuts in the Red Sea -- EIG, Seacom, AAE-1 -- are also impacting capacity on the East Coast of Africa. This combination of incidents has impacted all Africa capacity – including other Cloud providers and public Internet as well. Current Workstreams: We are exploring the following mitigation workstreams Working with our local network partner to fix defective links. Exploring traffic redirection and optimization on our network We estimate that these workstreams will take up to 12 hours to complete. Customers who are experiencing severe disruption to their operations may want to consider their BCDR options. The next update will be provided in 4 hours or as events warrant.

Azure South Africa Region

Thu, 14 Mar 2024 13:22:00 -0000

Update from Azure Current Status: We have determined that multiple fiber cables on the West Coast of Africa — WACS, MainOne, SAT3, ACE — have been impacted which reduced total capacity supporting our Regions in South Africa. In addition to these cable impacts, the on-going cable cuts in the Red Sea — EIG, Seacom, AAE-1 — are also impacting capacity on the East Coast of Africa. This combination of incidents has impacted all Africa capacity – including other Cloud providers and public Internet as well. Current Workstreams: We are exploring the following mitigation workstreams Working with our local network partner to fix defective links. Exploring traffic redirection and optimization on our network The next update will be provided in 60 minutes, or as events warrant

Azure South Africa Region

Thu, 14 Mar 2024 12:11:00 -0000

This issue continues to affected certain customers accessing resources in Azure South Africa. The issue is affecting access to both Azure and Microsoft 365 across South Africa, as well as other service providers. Update from Azure We are currently investigating a networking issue that has resulted in higher-than-expected latency for users whose resources are hosted in or connect with South Africa North and West. The next update will be provided in 60 minutes, or as events warrant.

Azure South Africa Region

Thu, 14 Mar 2024 12:00:00 -0000

Azure have notified that they are rerouting connections to alternate components to mitigate impact.

Azure South Africa Region

Thu, 14 Mar 2024 11:33:00 -0000

Update from Azure Starting at 10:30 UTC on 14 Mar 2024, Azure Services in South Africa North and South Africa West may experience service degradation and availability issues. Additionally, customers may have observed higher than expected latency and packet drops for resources hosted in these regions. Current Status: We are aware of this issue and are actively investigating. The next update will be provided in 60 minutes, or as events warrant.

Azure South Africa Region

Thu, 14 Mar 2024 11:21:00 -0000

Azure have assigned the reoccurrence issue VT60-RPZ https://app.azure.com/h/VT60-RPZ/8ffce0

Azure South Africa Region

Thu, 14 Mar 2024 10:52:00 -0000

This issue has reoccured - monitoring

Azure South Africa Region

Wed, 13 Mar 2024 18:00:00 -0000

Azure have confirmed the fibre cut was resolved, and have closed the issue

Azure South Africa Region

Wed, 13 Mar 2024 17:23:00 -0000

Update from Azure: In addition to addressing a fiber cut and assessing how quickly we can expedite its repair, our efforts to restore optimum network performance have included reducing the reservation on certain links, leading to a notable decrease in packet drops and an overall improvement in services. While we have optimized and load balanced our network to utilize all available capacity, we are still assessing impact with some of our routing on segments whether or not we can take on a peak load. Azure Front Door is planning to redirect traffic away from South Africa to another region, provided that no further packet drops occur. The next update will be provided in 2 hours, or as events warrant.

Azure South Africa Region

Wed, 13 Mar 2024 14:56:00 -0000

Update from Azure We determined that this issue was caused by a fiber cut, resulting in congestion specifically affecting the traffic in the Africa region. This has impacted the connectivity between South Africa and Europe, causing disruptions to your services. Our teams are actively working to address these issues and restore normal operations. The next update will be provided in 60 minutes, or as events warrant.

Azure South Africa Region

Wed, 13 Mar 2024 14:30:00 -0000

Azure have notified us of network issues within South Africa North and South Africa West. We are monitoring https://app.azure.com/h/_NF5-7PG/8ffce0

Meta Disruptions

Tue, 05 Mar 2024 21:00:00 -0000

Meta have confirmed all services are restored to normal

Meta Disruptions

Tue, 05 Mar 2024 16:48:00 -0000

Meta have updated the incident to say they are recovering.

Meta Disruptions

Tue, 05 Mar 2024 16:00:00 -0000

Meta is experiencing a large service disruption which may be affecting WhatsApp, Facebook and Instagram services at this time More details are posted at https://metastatus.com/

UK Outbound Calling

Mon, 05 Feb 2024 15:43:00 -0000

Carrier has confirmed the issue was in a DNS change made. Awaiting a detailed RFO.

UK Outbound Calling

Mon, 05 Feb 2024 15:34:00 -0000

We are seeing service return to normal - awaiting feedback from carrier.

UK Outbound Calling

Mon, 05 Feb 2024 15:24:00 -0000

This has been escalated internally with the upstream carrier to the relevant technicians.

UK Outbound Calling

Mon, 05 Feb 2024 15:07:00 -0000

We are aware of an issue dialling out to UK numbers. This has been flagged with the upstream carrier.

WhatsApp Cloud Numbers

Fri, 02 Feb 2024 08:28:00 -0000

360Dialog have confirmed resolution - we continue to monitor

WhatsApp Cloud Numbers

Fri, 02 Feb 2024 08:17:00 -0000

We still await feedback from 360Dialog

WhatsApp Cloud Numbers

Fri, 02 Feb 2024 07:56:00 -0000

360Dialog has confirmed they're aware of the issue and investigating.

WhatsApp Cloud Numbers

Fri, 02 Feb 2024 07:54:00 -0000

We are aware of an issue affecting all WhatsApp Cloud Numbers. We are awaiting feedback from 360Dialog.

Database Maintainence

Fri, 05 Jan 2024 23:29:35 +0000

Maintenance completed

Database Maintainence

Fri, 05 Jan 2024 23:29:35 -0000