Resolved

We have found the root cause of the incorrect port out notifications. All of the emails were sent in error, and none of the numbers are leaving Skyetel's network. Here's what happened:

Skyetel has been in the process of migrating it's phone number inventory to our own SPID for about a year and today we processed a large migration that impacted many Skyetel customer's phone numbers. We do this regularly, and they are usually done using a process that prevents email notifications from being sent to customers. In this case, a new team member was doing an authorized migration but accidentally had a typo in the migration order that triggered the port out rejection emails.

So the good news is that our authentication system just was battle tested (and it worked!), but the bad news is we scared the heebie jeebies out of everyone. We are very sorry for the inconvenience.

Avatar for
Investigating

We are aware that our network sent port out notification emails to our customers and are investigating.

Avatar for
Began at:

Affected components
  • Misc