SMS delivery via HTTP POST was broken via one of our SMS relays for a while this morning. The symptom was that "da", the destination address, was being posted as the "target" rather than the destination number. This means if we post to your server on https://example.com/sms/, we could have posted the SMS with the destination number of literally "https://example.com/sms/". This would have broken anything depending on the "da" to make decisions on what to do with the message. This is fixed now, and the problem occurred between around 9:15 and 11:21. Apologies for any inconvenience.