Primevox Communications - Notice history

All systems operational

Operational

Inbound Calling - Operational

100.0% uptime
Dec 2021 · 100.0%Jan 2022 · 100.0%Feb · 99.99%

Previous page

Next page

Dec 2021
Jan 2022
Feb 2022

Outbound Calling - Operational

100.0% uptime
Dec 2021 · 100.0%Jan 2022 · 100.0%Feb · 99.99%

Previous page

Next page

Dec 2021
Jan 2022
Feb 2022

AnswerCARE & Voicemail - Operational

100.0% uptime
Dec 2021 · 100.0%Jan 2022 · 100.0%Feb · 100.0%

Previous page

Next page

Dec 2021
Jan 2022
Feb 2022
Operational

Inbound Messaging - Operational

99.92% uptime
Dec 2021 · 100.0%Jan 2022 · 99.77%Feb · 100.0%

Previous page

Next page

Dec 2021
Jan 2022
Feb 2022

Outbound Messaging - Operational

99.92% uptime
Dec 2021 · 100.0%Jan 2022 · 99.77%Feb · 100.0%

Previous page

Next page

Dec 2021
Jan 2022
Feb 2022
Operational

PBX Admin & User Portal - Operational

100.0% uptime
Dec 2021 · 100.0%Jan 2022 · 100.0%Feb · 99.99%

Previous page

Next page

Dec 2021
Jan 2022
Feb 2022

SMS/MMS Messaging API - Operational

100.0% uptime
Dec 2021 · 100.0%Jan 2022 · 100.0%Feb · 100.0%

Previous page

Next page

Dec 2021
Jan 2022
Feb 2022

Call History API - Operational

100.0% uptime
Dec 2021 · 100.0%Jan 2022 · 100.0%Feb · 100.0%

Previous page

Next page

Dec 2021
Jan 2022
Feb 2022

Click-to-Call API - Operational

100.0% uptime
Dec 2021 · 100.0%Jan 2022 · 100.0%Feb · 100.0%

Previous page

Next page

Dec 2021
Jan 2022
Feb 2022

eFax API - Operational

100.0% uptime
Dec 2021 · 100.0%Jan 2022 · 100.0%Feb · 100.0%

Previous page

Next page

Dec 2021
Jan 2022
Feb 2022

Notice history

View current status

Feb 2022

Issues in Phoenix datacenter
ResolvedPartial outage6 minutes
  • ResolvedUTC

    The packet loss in our Phoenix datacenter has been resolved. Calls, phone status, and web portal activity should all return to normal within minutes.

    We genuinely apologize for this inconvenience!

  • IdentifiedUTC

    Hello, we've identified packet loss in our Phoenix, AZ datacenter.

    Some customers my experience dropped calls and an inability to access our web portal.

    All engineers are actively engaged to repair this issue as quickly as possible.

Jan 2022

SMS/MMS Delays
ResolvedPartial outage5 hours 47 minutes
  • ResolvedUTC

    Upstream carriers are showing fully operational SMS and MMS messaging.

    If you continue to encounter any issues with messaging, please email support@primevox.net and we will be happy to assist!

  • UpdateUTC

    Inbound SMS and MMS messaging is operating normally.

    Outbound SMS and MMS, however, continue to experience some delays with delivery. Upstream carriers are still working on a resolution.

  • IdentifiedUTC

    Several major upstream carriers are experiencing delays with SMS/MMS (text and picture messaging). These messages may be delayed in delivery or experience delivery failures. Not all carriers are affected.

    If you are unable to receive MFA/2FA while trying to log in to the Cloud PBX portal, please send an email to support@primevox.net to have us temporarily disable this feature.

Dec 2021

Raleigh datacenter packet loss
ResolvedDegraded performance33 minutes
  • ResolvedUTC

    The packet loss in our Raleigh, NC datacenter has been fixed, and we are seeing that traffic return to normal.

    What this means: Very few users likely noticed any issue at all. Even though this was a small event, PrimeVOX feels it is important to always maintain clear and proactive communications with our customers, just in case a small event would ever lead to a larger one, we want you to always know what is going on.

  • IdentifiedUTC

    We have identified some packet loss coming out of our Raleigh, NC datacenter. Our fiber carriers are engaged and working to resolve this issue.

    What this means: Packet loss can sometimes cause occasional calls to drop, or call quality to become degraded for some calls. Most people will not notice this issue since it is limited to only 1 data center.

DEC12
Log4j Vulnerability Remediation
CompletedMaintenance11 minutes
  • CompletedDecember 12, 2021 at 5:56 PMUTC

    Remediation of the log4j vulnerability has been completed.

  • In progressDecember 12, 2021 at 5:46 PMUTC

    Maintenance is now in progress.

  • PlannedDecember 12, 2021 at 5:45 PMUTC

    We have identified a single piece of software in our infrastructure that is susceptible to the newly discovered log4j 0-day vulnerability, and will be patching it shortly.

    There is no expected impact to services.

Previous

Dec 2021 to Feb 2022

Next