Resolved
Resolved
After 4 hours and 10 minutes

We've now resolved the incident. Thanks for your patience.

Avatar for
Recovering
After 42 minutes

This issue is now resolved and we’ve corrected our systems to account for this edge case. We will leave this notice up for a couple hours to make sure our customers who are not in the office yet have a chance to see it.

Skyetel recently automated a lot of its porting workflow, most notably it’s Port Out notifications. However, there are still circumstances where a port needs to be processed manually due to technical variables about the phone number or gaining/loosing carriers.

We thought we had accounted for all edge cases but… we apparently missed one. This morning our team manually authorized a port out request to a gaining carrier which triggered a bug in our authentication system that caused a loop. The system then ran through all of our phone numbers as a security check and sent them the port out message in error.

No numbers were ported out, and nothing shady happened that should cause concern. Your numbers are fully intact :). This was strictly an embarrassing bug.

We are very sorry for the inconvenience this caused.

Avatar for
Identified
After 25 minutes

We identified the glitch, and stopped additional emails. We will provide an update as to the cause of this within two hours.

Sorry for spamming you :(

Avatar for
Investigating

Our team is currently investigating a port out notification bug that is causing a flood of inaccurate port out notifications. Don’t worry - these numbers are not actually being ported out. Updates to follow shortly.

Avatar for
Began at:

Affected components
  • Misc