Rival5 - Notice history

RCom Unified Communications Hosted PBX Instances - Operational

100% - uptime
Sep 2024 · 99.933%Oct · 100.00%Nov · 100.00%
Sep 202499.933% uptime
Oct 2024100.00% uptime
Nov 2024100.00% uptime
100% - uptime

Emergency / 911 Call Routing - Operational

100% - uptime
Sep 2024 · 99.933%Oct · 100.00%Nov · 100.00%
Sep 202499.933% uptime
Oct 2024100.00% uptime
Nov 2024100.00% uptime

International Calling - Operational

100% - uptime
Sep 2024 · 99.933%Oct · 100.00%Nov · 100.00%
Sep 202499.933% uptime
Oct 2024100.00% uptime
Nov 2024100.00% uptime

Origination (Inbound) Calling - Operational

100% - uptime
Sep 2024 · 99.933%Oct · 100.00%Nov · 100.00%
Sep 202499.933% uptime
Oct 2024100.00% uptime
Nov 2024100.00% uptime

Termination (Outbound) Calling - Operational

100% - uptime
Sep 2024 · 99.933%Oct · 100.00%Nov · 100.00%
Sep 202499.933% uptime
Oct 2024100.00% uptime
Nov 2024100.00% uptime

Toll-Free Origination (Inbound) Calling - Operational

100% - uptime
Sep 2024 · 99.933%Oct · 100.00%Nov · 100.00%
Sep 202499.933% uptime
Oct 2024100.00% uptime
Nov 2024100.00% uptime

RFax Electronic Fax Services - Operational

100% - uptime
Sep 2024 · 100.00%Oct · 100.00%Nov · 100.00%
Sep 2024100.00% uptime
Oct 2024100.00% uptime
Nov 2024100.00% uptime

Notice history

Nov 2024

No notices reported this month

Oct 2024

No notices reported this month

Sep 2024

Transit/ISP Investigation
  • Resolved
    Resolved

    Rival5 engineers have conferred with the affected ISP and identified issues with a peering partner of the affected ISP stemming from recent maintenance performed. Routes and peering relationships between the ISP and providers to/from our infrastructure and data centers are suspected to have failed as a result of this maintenance and have been reset.

    The affected ISP is working closely with their peering partner to ensure stability and is keeping Rival5 apprised of any pertinent information.

    This only affected some customers within Rival5's network, but then also only affected some customers within this affected ISP's network as well. Rival5 is considering this incident resolved at this time but will still continue to monitor traffic to and from previously affected customers as routes are restored.

  • Monitoring
    Monitoring

    Rival5 network engineers have been working with customers' primary ISP involved in the to/from transit between connected sites with endpoints deployed and our data centers. After communicating troubles and providing examples traffic and traces, Rival5 has observed stabilized device registration behavior.

    We will continue to monitor this situation closely throughout today and will confer with the affected ISP.

  • Investigating
    Investigating

    Ok Tuesday 09/18/24 at 06:50 AM Central irregular and repetitious device registrations were beginning to cause anomaly warnings within our monitoring system.

    Rival5 support and network engineers soon began troubleshooting issues with customers that submitted a support request using our Rival5 Support Center.

    Our team has reached out to a shared ISP across customers for troubleshooting assistance and route identification into and out of their network, and we have also been in contact with network architects within our transit connectivity provider to troubleshoot paths and routes currently in use and identify any issues/make changes as necessary.

    We will update this thread shortly with more information.

Sep 2024 to Nov 2024

Next