What happened
Services can let people reply to their text messages by asking for a virtual mobile number (VMN). VMNs are set up by one of Notify’s text message providers. Services can see and reply to the messages they receive when they sign in to Notify, or get them using the API.
On 30 June some of our users told us that they were not receiving any inbound text messages.
The cause of the problem was a mistake by one of the mobile networks while doing some server maintenance. Changes to the servers that store Notify’s VMN details affected routing of some inbound messages.
After confirming that messages were not being received we contacted our provider. They investigated and alerted the mobile phone network, who were able to fix the problem.
What was the impact
Between 09:00 BST June 30 and 10:37 BST July 3, we did not receive inbound text messages sent to VMNs beginning with 073.
Inbound text messages sent to all other VMNs were not affected.
Depending on their phone type, users would have had one of the following experiences:
Unfortunately, we do not know how many inbound text messages users tried to send during this time. The phone networks were not able to resend any messages that failed.
What we’re doing about it
We're working with our provider and the phone network to stop this from happening again.
They're improving their monitoring and testing to make sure that any future changes do not affect Notify. If something does go wrong, they'll be made aware of it immediately so they can fix it.
We apologise for the impact this had to your service and your users. We know that the ability to receive inbound messages is often crucial for your service.
If you have any questions, please get in touch using our support page: