On the interface json.aspsms.com a problem could occur 18:00 - 19:45 CET. When sending SMS into the system, an error 500 was reported instead of the status code. Occasionally timeouts occurred until 20:30 CET. SMS scheduled for this period were sent despite the fault. The problem is now solved.|
There was a malfunction on the interfaces json.aspsms.com, soap.aspsms.com and xml3.aspsms.com between 10:45 - 11:15 CET. No SMS could be delivered to the system. SMS scheduled for this period were sent despite the malfunction. Until 13:15 o'clock ASPTOKEN SMS could still cause problems under certain circumstances. This is solved now, too.|
Due to a malfunction in the SMTP interface, SMS sent via <Recipient>@smtp.aspsms.com between 18:00 and 14:50 were partly not delivered.|
Due to a malfunction in the hosting infrastructure of the ASPSMS system,, no SMS messages could be entered via the APIs between 10:38 - 10:43 CET. SMSBLASTER web edition, the legacy SOAP interface webservice.aspsms.com, xml2.aspsms.com, xml4.aspsms.com and the website aspsms.com could partially not be reached until 11:00 a.m. either.|
Due to a malfunction in a network storage, the SMSBLASTER web edition, the ASPSMS SOAP Web service soap.aspsms.com and the website aspsms.com could partially not be reached between 09:50 - 10:09 CET. All other interfaces and services were available.|
Due to a network malfunction at 16:15 CET problems could occur when sending SMS to the ASPSMS system. In the period until 16:30 CET the SMSBLASTER web edition could not be reached at times.|
Due to a subliminal network failure since Monday, 16.04.2018 20:10 CET it could have happened that e-mail notifications (forwarding of incoming SMS, credit warnings, notification e-mails, etc.) were sent with delay or even partially not at all. Wednesday, 18.04.2018 the problem was detected and solved at 09:46 CET. The posting of SMS into the ASPSMS system and sending SMS were not affected at all.|
Due to a malfunction it was not possible to send SMS from 10:38 - 11:15 CET via the legacy SOAP api webservice.aspsms.com. We recommend all customers who still use webservice.aspsms.com to switch to soap.aspsms.com.|
Due to a malfunction in the ASPSMS system, problems with entering SMS jobs to the system and delays with the delivery of SMS could have occurred from 14:46 - 15:22 CET.|
Due to a malfunction in the network infrastructure, SMS could occasionally not be delivered to the system during the period 08:05 - 08:10 CET. SMS messages whose transmission was planned for the period of the fault were sent afterwards.|
In the period 17-21.03.2018, no delivery notifications were received for some networks. This behavior had no influence on the effective delivery of the SMS. The problem has been solved.|
Due to a malfunction in the ASPSMS system, problems with entering SMS jobs to the system and delays with the delivery of SMS could occur from 10:00 - 10:25 CET.|
The failure of the SMTP interface was ongoing. No SMS jobs could be entered through email@example.com, <Recipient>@smtp.aspsms.com and firstname.lastname@example.org. The problem was resolved 11:57 CET.
The failure of the SMTP interface was ongoing. No SMS jobs could be entered through email@example.com, <Recipient>@smtp.aspsms.com and firstname.lastname@example.org. The problem was resolved 11:57 CET. On some routes it could happen that SMS up could not get through until 13:20 CET.
Disturbances from 10:39 - 11:03 CET. SMS could be entered to the system sometimes only with difficulties and delays may have occured during delivery. The Problem was partially solved. SMTP interface still affected.
Massive problems in the Swisscom mobile network from 09:41 - 09:58 CET. SMS messages to Swisscom's networks were buffered and delivered after the problems were solved.