Uptime VoIP Status - Incident history https://status.uptimevoip.co Uptime VoIP Tue, 8 Jul 2025 19:12:28 +0000 GRR - Phone registration failures Type: Incident Duration: 51 minutes Affected Components: Provisioning, Core Services, Manager Portal, Portals and Services Jul 8, 19:12:28 GMT+0 - Investigating - We are currently seeing some customers with intermittent failures of phone registration on our GRR datacenter and we are investigating this incident. An update will be provided in 30 minutes. Jul 8, 19:28:35 GMT+0 - Monitoring - We have redirected all GRR phones to our IAD datacenter which has resolved the issues. If you are still having call failures after this email, please reboot your phone before submitting a ticket to [help@uptimevoip.co](mailto:help@uptimevoip.co) for further support. Jul 8, 20:03:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 51 minutes

Affected Components: , , ,

<p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>19:12:28</var> GMT+0</small><br><strong>Investigating</strong> - We are currently seeing some customers with intermittent failures of phone registration on our GRR datacenter and we are investigating this incident. An update will be provided in 30 minutes. .</p> <p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>19:28:35</var> GMT+0</small><br><strong>Monitoring</strong> - We have redirected all GRR phones to our IAD datacenter which has resolved the issues. If you are still having call failures after this email, please reboot your phone before submitting a ticket to [help@uptimevoip.co](mailto:help@uptimevoip.co) for further support. .</p> <p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>20:03:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 8 Jul 2025 19:12:28 +0000 https://status.uptimevoip.co/incident/cmcuwq4m8004a3ocg1divof4x https://status.uptimevoip.co/incident/cmcuwq4m8004a3ocg1divof4x GRR Core Server - Loss of Communication Type: Incident Duration: 1 day, 1 hour and 31 minutes Affected Components: Core Services Jun 4, 14:30:00 GMT+0 - Investigating - At 10:30am ET, our monitoring system alerted us to the GRR server being unreachable for two minutes, resulting in device registrations and inbound calls to failover to other servers. Shortly after the same datacenter loss communication again. We are investigating quickly and will determine if we need to temporarily close GRR. Updates to follow Jun 4, 16:02:05 GMT+0 - Monitoring - We implemented a internet provider fix at the GRR datacenter and are currently monitoring the result. If you continue to have issues after a reboot, please email [help@uptimevoip.co](mailto:help@uptimevoip.co) and we will handle issues on a case by case basis. Jun 5, 16:01:21 GMT+0 - Resolved - This incident has been resolved. Our datacenter made the final changes to the routes around the impacted ISP. Type: Incident

Duration: 1 day, 1 hour and 31 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>14:30:00</var> GMT+0</small><br><strong>Investigating</strong> - At 10:30am ET, our monitoring system alerted us to the GRR server being unreachable for two minutes, resulting in device registrations and inbound calls to failover to other servers. Shortly after the same datacenter loss communication again. We are investigating quickly and will determine if we need to temporarily close GRR. Updates to follow.</p> <p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>16:02:05</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a internet provider fix at the GRR datacenter and are currently monitoring the result. If you continue to have issues after a reboot, please email [help@uptimevoip.co](mailto:help@uptimevoip.co) and we will handle issues on a case by case basis. .</p> <p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>16:01:21</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. Our datacenter made the final changes to the routes around the impacted ISP..</p> ]]> Wed, 4 Jun 2025 14:30:00 +0000 https://status.uptimevoip.co/incident/cmbi3d04a000s1hn8p8tokqml https://status.uptimevoip.co/incident/cmbi3d04a000s1hn8p8tokqml GRR - Storage upgrades Type: Maintenance Duration: 5 hours Feb 8, 07:00:00 GMT+0 - Completed - Maintenance has completed successfully Feb 8, 02:00:01 GMT+0 - Identified - Maintenance is now in progress Feb 8, 02:00:00 GMT+0 - Identified - We are planning a scheduled maintenance during this time to upgrade the storage array, vastly improving performance on the GRR core servers. No impact on calling is expected, and you don’t need to do anything to prepare. If you happen to experience an issue during or after maintenance, please reboot your phones and email [help@uptimevoip.co](mailto:help@uptimevoip.co) if the issue persists. Type: Maintenance

Duration: 5 hours

<p><small>Feb <var data-var='date'> 8</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Feb <var data-var='date'> 8</var>, <var data-var='time'>02:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Feb <var data-var='date'> 8</var>, <var data-var='time'>02:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning a scheduled maintenance during this time to upgrade the storage array, vastly improving performance on the GRR core servers. No impact on calling is expected, and you don’t need to do anything to prepare. If you happen to experience an issue during or after maintenance, please reboot your phones and email [help@uptimevoip.co](mailto:help@uptimevoip.co) if the issue persists..</p> ]]> Sat, 8 Feb 2025 02:00:00 +0000 https://status.uptimevoip.co/maintenance/cm6v70pvh006i11qwlj3t6h54 https://status.uptimevoip.co/maintenance/cm6v70pvh006i11qwlj3t6h54 Core server maintenance Type: Maintenance Duration: 2 hours Feb 4, 04:00:00 GMT+0 - Identified - We are planning a scheduled maintenance during this time. We do not anticipate any impact on our services. Feb 4, 06:00:00 GMT+0 - Completed - Maintenance has completed successfully Feb 4, 04:00:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 2 hours

<p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning a scheduled maintenance during this time. We do not anticipate any impact on our services..</p> <p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>04:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> ]]> Tue, 4 Feb 2025 04:00:00 +0000 https://status.uptimevoip.co/maintenance/cm6pnv2tf004lh2vgclgso3x0 https://status.uptimevoip.co/maintenance/cm6pnv2tf004lh2vgclgso3x0 Call park issues Type: Incident Duration: 2 days, 3 hours and 33 minutes Feb 3, 14:19:00 GMT+0 - Identified - We have identified an **intermittent** issue with call parks for some users, where a call is dropped when parked. We are currently working on a fix for this issue and will provide updates as soon as we have more information. **Workaround:** If you are **experiencing** this issue, you can place the call on hold and transfer it as a temporary solution. Feb 5, 17:52:07 GMT+0 - Resolved - We have found the dropped call issue when placing calls onpark or hold to be caused by a cross core calling bug. DIDs have been moved back to their home cores to resolve this issue. If you still continue to have dropped calls on hold or park, please submit a ticket to [help@uptimevoip.co](mailto:help@uptimevoip.co) so we can troubleshoot these on a case by case basis. Type: Incident

Duration: 2 days, 3 hours and 33 minutes

<p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>14:19:00</var> GMT+0</small><br><strong>Identified</strong> - We have identified an **intermittent** issue with call parks for some users, where a call is dropped when parked. We are currently working on a fix for this issue and will provide updates as soon as we have more information. **Workaround:** If you are **experiencing** this issue, you can place the call on hold and transfer it as a temporary solution..</p> <p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>17:52:07</var> GMT+0</small><br><strong>Resolved</strong> - We have found the dropped call issue when placing calls onpark or hold to be caused by a cross core calling bug. DIDs have been moved back to their home cores to resolve this issue. If you still continue to have dropped calls on hold or park, please submit a ticket to [help@uptimevoip.co](mailto:help@uptimevoip.co) so we can troubleshoot these on a case by case basis..</p> ]]> Mon, 3 Feb 2025 14:19:00 +0000 https://status.uptimevoip.co/incident/cm6pmeqwk001yh2vggkdwxmns https://status.uptimevoip.co/incident/cm6pmeqwk001yh2vggkdwxmns Inbound call failures Type: Incident Duration: 5 days, 5 hours and 34 minutes Jan 29, 16:38:00 GMT+0 - Investigating - We are currently investigating inbound call failures reported Jan 29, 18:18:00 GMT+0 - Identified - We have identified the issue as an errant dial translation rule that was affecting inbound and outbound calls, generally with a "403 Forbidden." error showing when trying to dial a number. We are currently working on applying the fix and will update you as soon as possible. Jan 29, 18:23:00 GMT+0 - Monitoring - The dial translation has been fixed and we are now monitoring. Calls should be back to normal. If they are not, please submit a case to [help@uptimevoip.co](mailto:help@uptimevoip.co) so we can troubleshoot on a case by case basis. Feb 3, 22:12:28 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 5 days, 5 hours and 34 minutes

<p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>16:38:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating inbound call failures reported.</p> <p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>18:18:00</var> GMT+0</small><br><strong>Identified</strong> - We have identified the issue as an errant dial translation rule that was affecting inbound and outbound calls, generally with a "403 Forbidden." error showing when trying to dial a number. We are currently working on applying the fix and will update you as soon as possible..</p> <p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>18:23:00</var> GMT+0</small><br><strong>Monitoring</strong> - The dial translation has been fixed and we are now monitoring. Calls should be back to normal. If they are not, please submit a case to [help@uptimevoip.co](mailto:help@uptimevoip.co) so we can troubleshoot on a case by case basis..</p> <p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>22:12:28</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 29 Jan 2025 16:38:00 +0000 https://status.uptimevoip.co/incident/cm6ijdmjp010qbhbcih8j9a3c https://status.uptimevoip.co/incident/cm6ijdmjp010qbhbcih8j9a3c Central Voice - Outage Type: Incident Duration: 8 hours and 33 minutes Jul 16, 00:44:13 GMT+0 - Investigating - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service. Jul 16, 00:52:45 GMT+0 - Resolved - The Central voice node is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 8 hours and 33 minutes

<p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>00:44:13</var> GMT+0</small><br><strong>Investigating</strong> - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>00:52:45</var> GMT+0</small><br><strong>Resolved</strong> - The Central voice node is now operational! This update was created by an automated monitoring service..</p> ]]> Tue, 16 Jul 2024 00:44:12 +0000 https://status.uptimevoip.co/incident/clynoxr2a147671h2orsnuvei2v https://status.uptimevoip.co/incident/clynoxr2a147671h2orsnuvei2v Central Voice - Outage Type: Incident Duration: 2 hours and 1 minute Jul 16, 00:38:19 GMT+0 - Investigating - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service. Jul 16, 00:40:20 GMT+0 - Resolved - The Central voice node is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 2 hours and 1 minute

<p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>00:38:19</var> GMT+0</small><br><strong>Investigating</strong> - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>00:40:20</var> GMT+0</small><br><strong>Resolved</strong> - The Central voice node is now operational! This update was created by an automated monitoring service..</p> ]]> Tue, 16 Jul 2024 00:38:19 +0000 https://status.uptimevoip.co/incident/clynoq6oa129815h2orhwh15jrh https://status.uptimevoip.co/incident/clynoq6oa129815h2orhwh15jrh Central Voice - Outage Type: Incident Duration: 3 hours and 12 minutes Jul 16, 00:27:43 GMT+0 - Investigating - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service. Jul 16, 00:30:55 GMT+0 - Resolved - The Central voice node is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 3 hours and 12 minutes

<p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>00:27:43</var> GMT+0</small><br><strong>Investigating</strong> - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>00:30:55</var> GMT+0</small><br><strong>Resolved</strong> - The Central voice node is now operational! This update was created by an automated monitoring service..</p> ]]> Tue, 16 Jul 2024 00:27:43 +0000 https://status.uptimevoip.co/incident/clynocjwk96052gvorg5f28fqb https://status.uptimevoip.co/incident/clynocjwk96052gvorg5f28fqb Central Voice - Outage Type: Incident Duration: 8 hours and 3 minutes Jul 16, 00:25:32 GMT+0 - Resolved - The Central voice node is now operational! This update was created by an automated monitoring service. Jul 16, 00:17:29 GMT+0 - Investigating - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service. Type: Incident

Duration: 8 hours and 3 minutes

<p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>00:25:32</var> GMT+0</small><br><strong>Resolved</strong> - The Central voice node is now operational! This update was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>00:17:29</var> GMT+0</small><br><strong>Investigating</strong> - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service..</p> ]]> Tue, 16 Jul 2024 00:17:29 +0000 https://status.uptimevoip.co/incident/clynnzdn573137hgoayy0r3qrx https://status.uptimevoip.co/incident/clynnzdn573137hgoayy0r3qrx Central Voice - Outage Type: Incident Duration: 1 day, 2 hours and 2 minutes Jul 15, 23:45:55 GMT+0 - Investigating - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service. Jul 16, 00:11:56 GMT+0 - Resolved - The Central voice node is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 1 day, 2 hours and 2 minutes

<p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>23:45:55</var> GMT+0</small><br><strong>Investigating</strong> - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>00:11:56</var> GMT+0</small><br><strong>Resolved</strong> - The Central voice node is now operational! This update was created by an automated monitoring service..</p> ]]> Mon, 15 Jul 2024 23:45:55 +0000 https://status.uptimevoip.co/incident/clynmusjd1588hgoa2aaxjkfx https://status.uptimevoip.co/incident/clynmusjd1588hgoa2aaxjkfx Central Voice - Outage Type: Incident Duration: 2 hours and 20 minutes Jul 15, 23:24:44 GMT+0 - Investigating - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service. Jul 15, 23:27:03 GMT+0 - Resolved - The Central voice node is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 2 hours and 20 minutes

<p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>23:24:44</var> GMT+0</small><br><strong>Investigating</strong> - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>23:27:03</var> GMT+0</small><br><strong>Resolved</strong> - The Central voice node is now operational! This update was created by an automated monitoring service..</p> ]]> Mon, 15 Jul 2024 23:24:44 +0000 https://status.uptimevoip.co/incident/clynm3jcy584158lyolomr2z56g https://status.uptimevoip.co/incident/clynm3jcy584158lyolomr2z56g Central Voice - Outage Type: Incident Duration: 1 hour and 16 minutes Jul 15, 23:03:51 GMT+0 - Investigating - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service. Jul 15, 23:05:06 GMT+0 - Resolved - The Central voice node is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 1 hour and 16 minutes

<p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>23:03:51</var> GMT+0</small><br><strong>Investigating</strong> - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>23:05:06</var> GMT+0</small><br><strong>Resolved</strong> - The Central voice node is now operational! This update was created by an automated monitoring service..</p> ]]> Mon, 15 Jul 2024 23:03:51 +0000 https://status.uptimevoip.co/incident/clynlcoup525275lrolzkfnk084 https://status.uptimevoip.co/incident/clynlcoup525275lrolzkfnk084 Central Voice - Outage Type: Incident Duration: 2 hours and 1 minute Jul 15, 22:45:30 GMT+0 - Investigating - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service. Jul 15, 22:47:30 GMT+0 - Resolved - The Central voice node is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 2 hours and 1 minute

<p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>22:45:30</var> GMT+0</small><br><strong>Investigating</strong> - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>22:47:30</var> GMT+0</small><br><strong>Resolved</strong> - The Central voice node is now operational! This update was created by an automated monitoring service..</p> ]]> Mon, 15 Jul 2024 22:45:30 +0000 https://status.uptimevoip.co/incident/clynkp3cc5011901an5x2tyr1tz https://status.uptimevoip.co/incident/clynkp3cc5011901an5x2tyr1tz Central Voice - Outage Type: Incident Duration: 1 hour and 6 minutes Jul 15, 22:22:38 GMT+0 - Investigating - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service. Jul 15, 22:23:44 GMT+0 - Resolved - The Central voice node is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 1 hour and 6 minutes

<p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>22:22:38</var> GMT+0</small><br><strong>Investigating</strong> - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>22:23:44</var> GMT+0</small><br><strong>Resolved</strong> - The Central voice node is now operational! This update was created by an automated monitoring service..</p> ]]> Mon, 15 Jul 2024 22:22:38 +0000 https://status.uptimevoip.co/incident/clynjvojm43134513n5koikz0bl https://status.uptimevoip.co/incident/clynjvojm43134513n5koikz0bl Central Voice - Outage Type: Incident Duration: 5 hours and 1 minute Jul 15, 22:00:05 GMT+0 - Investigating - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service. Jul 15, 22:05:05 GMT+0 - Resolved - The Central voice node is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 5 hours and 1 minute

<p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>22:00:05</var> GMT+0</small><br><strong>Investigating</strong> - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>22:05:05</var> GMT+0</small><br><strong>Resolved</strong> - The Central voice node is now operational! This update was created by an automated monitoring service..</p> ]]> Mon, 15 Jul 2024 22:00:05 +0000 https://status.uptimevoip.co/incident/clynj2oyo348874lrolbt2tote1 https://status.uptimevoip.co/incident/clynj2oyo348874lrolbt2tote1 Central Voice - Outage Type: Incident Duration: 1 day and 26 minutes Jul 13, 06:11:41 GMT+0 - Investigating - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service. Jul 13, 06:36:06 GMT+0 - Resolved - The Central voice node is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 1 day and 26 minutes

<p><small>Jul <var data-var='date'> 13</var>, <var data-var='time'>06:11:41</var> GMT+0</small><br><strong>Investigating</strong> - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 13</var>, <var data-var='time'>06:36:06</var> GMT+0</small><br><strong>Resolved</strong> - The Central voice node is now operational! This update was created by an automated monitoring service..</p> ]]> Sat, 13 Jul 2024 06:11:41 +0000 https://status.uptimevoip.co/incident/clyjqbbmu1163dwoouxcl2t6q https://status.uptimevoip.co/incident/clyjqbbmu1163dwoouxcl2t6q Central Voice - Outage Type: Incident Duration: 22 hours and 2 minutes Jul 10, 22:10:57 GMT+0 - Investigating - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service. Jul 10, 22:32:59 GMT+0 - Resolved - The Central voice node is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 22 hours and 2 minutes

<p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>22:10:57</var> GMT+0</small><br><strong>Investigating</strong> - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>22:32:59</var> GMT+0</small><br><strong>Resolved</strong> - The Central voice node is now operational! This update was created by an automated monitoring service..</p> ]]> Wed, 10 Jul 2024 22:10:57 +0000 https://status.uptimevoip.co/incident/clyge9eic404704gion22g0p2vj https://status.uptimevoip.co/incident/clyge9eic404704gion22g0p2vj Central Voice - Outage Type: Incident Duration: 1 hour and 8 minutes Jul 6, 14:08:29 GMT+0 - Investigating - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service. Jul 6, 14:09:37 GMT+0 - Resolved - The Central voice node is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 1 hour and 8 minutes

<p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>14:08:29</var> GMT+0</small><br><strong>Investigating</strong> - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>14:09:37</var> GMT+0</small><br><strong>Resolved</strong> - The Central voice node is now operational! This update was created by an automated monitoring service..</p> ]]> Sat, 6 Jul 2024 14:08:29 +0000 https://status.uptimevoip.co/incident/clya79j09105812jtod83s37sty https://status.uptimevoip.co/incident/clya79j09105812jtod83s37sty Central Voice - Outage Type: Incident Duration: 58 minutes Jul 6, 13:30:01 GMT+0 - Investigating - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service. Jul 6, 13:30:58 GMT+0 - Resolved - The Central voice node is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 58 minutes

<p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>13:30:01</var> GMT+0</small><br><strong>Investigating</strong> - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>13:30:58</var> GMT+0</small><br><strong>Resolved</strong> - The Central voice node is now operational! This update was created by an automated monitoring service..</p> ]]> Sat, 6 Jul 2024 13:30:01 +0000 https://status.uptimevoip.co/incident/clya5w24y82396dtokdxo92oyv https://status.uptimevoip.co/incident/clya5w24y82396dtokdxo92oyv Central Voice - Outage Type: Incident Duration: 2 hours and 9 minutes Jul 6, 13:06:12 GMT+0 - Investigating - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service. Jul 6, 13:08:21 GMT+0 - Resolved - The Central voice node is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 2 hours and 9 minutes

<p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>13:06:12</var> GMT+0</small><br><strong>Investigating</strong> - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>13:08:21</var> GMT+0</small><br><strong>Resolved</strong> - The Central voice node is now operational! This update was created by an automated monitoring service..</p> ]]> Sat, 6 Jul 2024 13:06:12 +0000 https://status.uptimevoip.co/incident/clya51g8a8274l3n4vnyr6efa https://status.uptimevoip.co/incident/clya51g8a8274l3n4vnyr6efa Central Voice - Outage Type: Incident Duration: 4 hours and 11 minutes Jul 6, 12:52:13 GMT+0 - Investigating - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service. Jul 6, 12:56:23 GMT+0 - Resolved - The Central voice node is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 4 hours and 11 minutes

<p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>12:52:13</var> GMT+0</small><br><strong>Investigating</strong> - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>12:56:23</var> GMT+0</small><br><strong>Resolved</strong> - The Central voice node is now operational! This update was created by an automated monitoring service..</p> ]]> Sat, 6 Jul 2024 12:52:13 +0000 https://status.uptimevoip.co/incident/clya4jg4q0168f9oggxdph2n9 https://status.uptimevoip.co/incident/clya4jg4q0168f9oggxdph2n9 Central Voice - Outage Type: Incident Duration: 3 hours and 10 minutes Jul 6, 12:42:21 GMT+0 - Investigating - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service. Jul 6, 12:45:30 GMT+0 - Resolved - The Central voice node is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 3 hours and 10 minutes

<p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>12:42:21</var> GMT+0</small><br><strong>Investigating</strong> - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>12:45:30</var> GMT+0</small><br><strong>Resolved</strong> - The Central voice node is now operational! This update was created by an automated monitoring service..</p> ]]> Sat, 6 Jul 2024 12:42:21 +0000 https://status.uptimevoip.co/incident/clya46rry2301j4oe2f3h569j https://status.uptimevoip.co/incident/clya46rry2301j4oe2f3h569j Central Voice - Outage Type: Incident Duration: 6 hours and 20 minutes Jul 6, 11:31:06 GMT+0 - Investigating - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service. Jul 6, 11:37:26 GMT+0 - Resolved - The Central voice node is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 6 hours and 20 minutes

<p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>11:31:06</var> GMT+0</small><br><strong>Investigating</strong> - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>11:37:26</var> GMT+0</small><br><strong>Resolved</strong> - The Central voice node is now operational! This update was created by an automated monitoring service..</p> ]]> Sat, 6 Jul 2024 11:31:06 +0000 https://status.uptimevoip.co/incident/clya1n55q235801hkn97nyio1a0 https://status.uptimevoip.co/incident/clya1n55q235801hkn97nyio1a0 Central Voice - Outage Type: Incident Duration: 1 hour Jul 6, 10:10:20 GMT+0 - Investigating - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service. Jul 6, 10:11:19 GMT+0 - Resolved - The Central voice node is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 1 hour

<p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>10:10:20</var> GMT+0</small><br><strong>Investigating</strong> - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>10:11:19</var> GMT+0</small><br><strong>Resolved</strong> - The Central voice node is now operational! This update was created by an automated monitoring service..</p> ]]> Sat, 6 Jul 2024 10:10:20 +0000 https://status.uptimevoip.co/incident/cly9yr9na0914e2oc9z86taqa https://status.uptimevoip.co/incident/cly9yr9na0914e2oc9z86taqa Central Voice - Outage Type: Incident Duration: 5 hours and 4 minutes Jul 6, 10:00:34 GMT+0 - Investigating - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service. Jul 6, 10:05:37 GMT+0 - Resolved - The Central voice node is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 5 hours and 4 minutes

<p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>10:00:34</var> GMT+0</small><br><strong>Investigating</strong> - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>10:05:37</var> GMT+0</small><br><strong>Resolved</strong> - The Central voice node is now operational! This update was created by an automated monitoring service..</p> ]]> Sat, 6 Jul 2024 10:00:34 +0000 https://status.uptimevoip.co/incident/cly9yepeo159238e1n06ac72uur https://status.uptimevoip.co/incident/cly9yepeo159238e1n06ac72uur Central Voice - Outage Type: Incident Duration: 4 hours and 5 minutes Jul 6, 09:24:36 GMT+0 - Investigating - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service. Jul 6, 09:28:40 GMT+0 - Resolved - The Central voice node is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 4 hours and 5 minutes

<p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>09:24:36</var> GMT+0</small><br><strong>Investigating</strong> - The Central voice node cannot be accessed at the moment. If you experience any issues, please reboot your phones to make sure they register to another core. This incident was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>09:28:40</var> GMT+0</small><br><strong>Resolved</strong> - The Central voice node is now operational! This update was created by an automated monitoring service..</p> ]]> Sat, 6 Jul 2024 09:24:36 +0000 https://status.uptimevoip.co/incident/cly9x4gg510926gfoe0yrd866v https://status.uptimevoip.co/incident/cly9x4gg510926gfoe0yrd866v