UCaaS Status Page - Registration Failure on GRR – Incident details

All systems operational

Registration Failure on GRR

Resolved
Operational
Started 5 months agoLasted about 23 hours

Affected

Core Services

Major outage from 7:16 PM to 7:16 PM, Operational from 7:16 PM to 5:51 PM

Grand Rapids (GRR) Voice

Major outage from 7:16 PM to 7:16 PM, Operational from 7:16 PM to 5:51 PM

Updates
  • Resolved
    Resolved

    At 2:26 PM ET, we received a notification from our NOC monitoring that the NMS service, which handles registration and call processing on GRR crashed. Active calls on this server did drop, and devices on GRR failed over to ATL successfully.

    What was Affected:

    • Device Registration on GRR

    • Active Calls on GRR

    When It Began: 06/05/2025 2:26 PM ET

    Current Status: This incident is now resolved.

    Next Steps:

  • Update
    Update

  • Monitoring
    Monitoring

    At 2:26 PM ET, we received a notification from our NOC monitoring that the NMS service which handles registration and call processing on GRR crashed. Active calls on this server did drop, and devices on GRR failed over to ATL successfully.

    What Is Affected:

    • Device Registration on GRR

    • Active Calls on GRR

    When It Began: 2:26 PM ET

    Current Status: The NMS service on GRR is back online as of 2:29 PM ET, and registration for all devices returned to GRR by 2:39 PM ET. At this time, all services on GRR are functioning as expected.

    Next Steps: We will be monitoring GRR for 24 hours per our major incident policy while we continue to investigate the root cause. If additional outages occur, we will manually redirect devices & calls on GRR to ATL until the problem is resolved.

    Next Update: 6/6/25 3:00 PM ET