tag:wigwag.statuspage.io,2005:/historyWigWag Status - Incident History2023-07-22T13:42:59+01:00WigWagtag:wigwag.statuspage.io,2005:Incident/110421042022-09-02T21:07:47+01:002022-09-02T21:07:47+01:00Reports of calls failing and unsuccessful registrations<p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>21:07</var> BST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>19:17</var> BST</small><br><strong>Monitoring</strong> - Calls should be successfully completing now.<br />We will continue to monitor.</p><p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>17:51</var> BST</small><br><strong>Investigating</strong> - We are seeing some call failure and have reports of unsuccessful handset registrations and are investigating</p>tag:wigwag.statuspage.io,2005:Incident/98778802022-04-29T10:33:27+01:002022-04-29T10:33:27+01:00Issues logging into Portal<p><small>Apr <var data-var='date'>29</var>, <var data-var='time'>10:33</var> BST</small><br><strong>Resolved</strong> - We have been monitoring this for a while and are not seeing any further issues.<br /><br />Please report any issues to support@wigwag.co.uk</p><p><small>Apr <var data-var='date'>29</var>, <var data-var='time'>09:35</var> BST</small><br><strong>Monitoring</strong> - We have issued a fix and currently monitoring, You should now be able to log into the portal. <br />Please report any further issues to support@wigwag.co.uk</p><p><small>Apr <var data-var='date'>29</var>, <var data-var='time'>09:32</var> BST</small><br><strong>Identified</strong> - We have identified the issue is affecting a couple of instances - remedial action is being taken currently</p><p><small>Apr <var data-var='date'>29</var>, <var data-var='time'>09:28</var> BST</small><br><strong>Investigating</strong> - We are recieving some reports of Clients being unable to log into the Portal and are investigating this currently.</p>tag:wigwag.statuspage.io,2005:Incident/84774772021-11-12T13:44:20+00:002021-11-12T13:44:20+00:00Reports of call quality issues<p><small>Nov <var data-var='date'>12</var>, <var data-var='time'>13:44</var> GMT</small><br><strong>Resolved</strong> - Between 8.30am - 9.30am This morning we had a few reports of intermittent call quality.<br />An update from one of our Traffic providers below.<br /><br />We saw instability in a single router within our Telehouse East site. This was due to a hardware limit being reached which we believe was the indirect result of overnight maintenance at a peer network. Addressing this caused widespread reconvergence across the network. We are monitoring the status of this router in case of recurrence but it has been stable since 9.34am.</p>tag:wigwag.statuspage.io,2005:Incident/80912832021-09-27T10:45:56+01:002021-09-27T10:45:56+01:00Outbound Call Issue<p><small>Sep <var data-var='date'>27</var>, <var data-var='time'>10:45</var> BST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Sep <var data-var='date'>27</var>, <var data-var='time'>10:34</var> BST</small><br><strong>Investigating</strong> - We are aware of an outbound call issue and are currently investigating.</p>tag:wigwag.statuspage.io,2005:Incident/74831692021-07-12T16:54:57+01:002021-07-12T16:54:57+01:00API not responding<p><small>Jul <var data-var='date'>12</var>, <var data-var='time'>16:54</var> BST</small><br><strong>Resolved</strong> - This incident has been resolved. We’re continuing to inspect logs to identify the query (or queries) which led to the deadlock and use our findings to prevent a recurrence in future.</p><p><small>Jul <var data-var='date'>12</var>, <var data-var='time'>13:49</var> BST</small><br><strong>Identified</strong> - The issue has been identified and addressed. The API is now responding and checks on all aspects are continuing</p><p><small>Jul <var data-var='date'>12</var>, <var data-var='time'>13:45</var> BST</small><br><strong>Update</strong> - We are continuing to investigate the API response issues. Calls are not affected by this.</p><p><small>Jul <var data-var='date'>12</var>, <var data-var='time'>13:26</var> BST</small><br><strong>Investigating</strong> - We are currently investigating this issue which will also cause interruption to access via the portal.<br /><br />You may have difficulty using the Chrome Dialler which may log you out.</p>tag:wigwag.statuspage.io,2005:Incident/71864782021-06-07T14:29:45+01:002021-06-07T14:29:45+01:00Calls and Registration Failing<p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>14:29</var> BST</small><br><strong>Resolved</strong> - Service has returned to normal and we have had no further reports of any ongoing impact.</p><p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>13:13</var> BST</small><br><strong>Monitoring</strong> - Service is beginning to return to normal for some customers and we expect all service to be returned to normal shortly.</p><p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>13:01</var> BST</small><br><strong>Update</strong> - We are continuing to work on mitigating the impact of this issue and you may still be experiencing intermittent drop in connectivity and calls.</p><p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>12:21</var> BST</small><br><strong>Update</strong> - We are seeing service restoring for most users and will monitor this. Please restart your device if it is unable to connect.</p><p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>12:15</var> BST</small><br><strong>Identified</strong> - We have identified this as relating to a connectivity impacting our central database. Actions have been taken to mitigate the impact.</p><p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>12:14</var> BST</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>12:00</var> BST</small><br><strong>Investigating</strong> - We are currently investigating reports of registration dropping and inbound and outbound calls failing on the platform.</p>tag:wigwag.statuspage.io,2005:Incident/69828442021-05-12T18:00:32+01:002021-05-12T18:00:32+01:00Number Routing updates<p><small>May <var data-var='date'>12</var>, <var data-var='time'>18:00</var> BST</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>May <var data-var='date'>12</var>, <var data-var='time'>17:00</var> BST</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>May <var data-var='date'>12</var>, <var data-var='time'>16:44</var> BST</small><br><strong>Update</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>May <var data-var='date'>12</var>, <var data-var='time'>13:54</var> BST</small><br><strong>Scheduled</strong> - We will be updating some routing for Inbound numbers today. We estimate this will only take a hour.<br />There is a small chance of calls not routing during this change for up to 30 minutes while our database catches up.</p>tag:wigwag.statuspage.io,2005:Incident/67934272021-04-20T14:09:38+01:002021-04-20T14:09:38+01:00Chrome Dialler Not Connecting<p><small>Apr <var data-var='date'>20</var>, <var data-var='time'>14:09</var> BST</small><br><strong>Resolved</strong> - This incident has now been resolved and Chrome diallers should now connect. Please let us know if you experience any further issues.</p><p><small>Apr <var data-var='date'>20</var>, <var data-var='time'>10:32</var> BST</small><br><strong>Investigating</strong> - We are currently investigating some Chrome Diallers not connecting to extensions.</p>tag:wigwag.statuspage.io,2005:Incident/67860482021-04-20T09:23:47+01:002021-04-20T09:23:47+01:00Shared Mailboxes Not Connecting<p><small>Apr <var data-var='date'>20</var>, <var data-var='time'>09:23</var> BST</small><br><strong>Resolved</strong> - This incident has now been resolved and mailboxes are now connecting. Please let us know if you experience any further issues.</p><p><small>Apr <var data-var='date'>19</var>, <var data-var='time'>17:08</var> BST</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Apr <var data-var='date'>19</var>, <var data-var='time'>14:03</var> BST</small><br><strong>Investigating</strong> - We are currently investigating some shared mailboxes not connecting and allowing customers to listen to recordings.</p>tag:wigwag.statuspage.io,2005:Incident/67398682021-04-13T09:19:54+01:002021-04-13T09:19:54+01:00Portal and API Access Issues<p><small>Apr <var data-var='date'>13</var>, <var data-var='time'>09:19</var> BST</small><br><strong>Resolved</strong> - At 8.58.am we received a few reports of some customers unable to access Portal and API elements.<br />There was also some reports of PDD (Post Dial Delay)<br />This appears to be due to a spike in traffic and service should already be restored.</p>tag:wigwag.statuspage.io,2005:Incident/67055992021-04-08T15:45:31+01:002021-04-08T15:45:31+01:00Phones Not Registered<p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>15:45</var> BST</small><br><strong>Resolved</strong> - Handsets should now be registering again successfully. <br />If a device is still showing "Not Registered" please reboot.</p><p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>15:36</var> BST</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>15:36</var> BST</small><br><strong>Investigating</strong> - We are currently investigating some phones showing Not Registered</p>tag:wigwag.statuspage.io,2005:Incident/66490892021-03-31T14:23:00+01:002021-03-31T15:11:11+01:00Some Devices showing "Not Registered"<p><small>Mar <var data-var='date'>31</var>, <var data-var='time'>14:23</var> BST</small><br><strong>Resolved</strong> - At 14:23 We received a few reports of Devices failing to connect to Device Registration Servers resulting in devices showing "Not Registered"<br />This appears to have affected a small number of devices and restarting (Snom **## Quick reboot) the devices successfully Registered.<br /><br />It looks like this relates to upstream traffic routes and only affecting a small number of routes to Registration Servers<br />We will continue to monitor currently and there has been no further reports since 14:30</p>tag:wigwag.statuspage.io,2005:Incident/65862562021-03-22T12:49:08+00:002021-03-22T12:49:08+00:00Some Calls with One Way Audio and Dial out Difficulty<p><small>Mar <var data-var='date'>22</var>, <var data-var='time'>12:49</var> GMT</small><br><strong>Resolved</strong> - We will continue to monitor calls. Everything is currently Stable</p><p><small>Mar <var data-var='date'>22</var>, <var data-var='time'>12:30</var> GMT</small><br><strong>Monitoring</strong> - We have had no additional reports of call issues in the last few hours however we will continue to monitor this for the next 24hrs<br /><br />If you would like to report a problem with a call please use<br /><br />https://wigwag.co.uk/phone-examples/</p><p><small>Mar <var data-var='date'>22</var>, <var data-var='time'>08:50</var> GMT</small><br><strong>Update</strong> - Based on example call logs some updates have been applied and we continue to Monitor.<br />Thank you for submitting call reports via<br /> https://wigwag.co.uk/phone-examples/</p><p><small>Mar <var data-var='date'>22</var>, <var data-var='time'>08:25</var> GMT</small><br><strong>Investigating</strong> - We had a few reports from 8.20am this morning of calls that had audio issues and also some calls unable to be dialled out.</p>tag:wigwag.statuspage.io,2005:Incident/65656822021-03-18T18:39:00+00:002021-03-18T23:31:34+00:00Intermittent call issues<p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>18:39</var> GMT</small><br><strong>Resolved</strong> - We are satisfied that the core issue is resolved and has been stable for some time now. We have worked through other edge issues we’ve been given examples for. Many customers have found that power-cycling their handsets has cleared issues for them.<br /><br />Please contact us as usual if you have any related, or indeed unrelated, issues supplying detailed information. Thank you for your patience during this service incident. A post mortem will follow in due course.</p><p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>12:38</var> GMT</small><br><strong>Monitoring</strong> - The mitigating work, which was completed around 11:45, appears to have been successful and we have switched this incident to monitoring status. All current reported issues will continue to be investigated and responded to. A post mortem of events over the last 24 hours will follow. Our apologies again for these service issues.</p><p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>12:21</var> GMT</small><br><strong>Update</strong> - Work is ongoing with remaining issues. Thank you again for your call logs as well as your patience throughout. Updates will continue to be made regularly</p><p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>11:49</var> GMT</small><br><strong>Update</strong> - We believe one way audio on calls were addressed by 11:25 - please contact us if you find otherwise. Outbound call volumes continue to rise and are approaching the expected levels for the time of day. We continue to process call logs to identify any remaining issues. An update will follow by 12:20</p><p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>11:08</var> GMT</small><br><strong>Identified</strong> - The analysis of logs and have identified some commonality. We have prevented further calls going to a common node and monitoring the effect on outgoing calls and any one way audio issues. Thank you for your further patience at this time. A further update will be made shortly</p><p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>10:57</var> GMT</small><br><strong>Update</strong> - We continue to process call logs to establish the cause of intermittent outgoing calls and any related symptoms. Thank you for your patience whilst we continue to work through these. We hope to have a more substantial update shortly</p><p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>10:23</var> GMT</small><br><strong>Update</strong> - We continue to investigate this issue and would welcome factual examples. In the main customer issues have been remnants of yesterday and resolved by power-cycling handsets. There were some uncaught consequences of yesterday’s changes which were resolved before 9am in so far as they affect calls.</p><p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>09:52</var> GMT</small><br><strong>Update</strong> - Following some mitigation work, we're seeing inbound call volumes as normal although there is still some intermittent connection issues and we have noticed isolated 1 way audio issues. Outbound remains impacted.</p><p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>09:05</var> GMT</small><br><strong>Investigating</strong> - We have received reports of intermittent call issues and are investigating.</p>tag:wigwag.statuspage.io,2005:Incident/65656602021-03-17T13:30:00+00:002021-03-18T23:10:57+00:00Reports of issues with calls and the portal<p><small>Mar <var data-var='date'>17</var>, <var data-var='time'>13:30</var> GMT</small><br><strong>Resolved</strong> - We are currently investigating reports of issues with calls and the portal.</p>