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.
Disturbances from 12:00 - 12:21 CET. Entering SMS to the system with difficulties. Some delays during delivery. The Problem was solved.
Disturbances from 09:35 - 10:24 CET. SMS could be entered to the system sometimes only with difficulties and delays may have occured during delivery. The Problem was solved.
From 18:25 CET onwards, there were performance problems with entering SMS jobs to the system. The problems were fixed at 20:14 CET.
Maintenance work was carried out on the network infrastructure of one of our backbone providers. This resulted in a planned service interruption from 02:21 - 02:32 CET. All interfaces (APIs) could not be reached during the service interruption. Scheduled SMS planned to be sent in this period, were sent afterwards.
Disturbances from approx. 04:00 - 06:35 CET. SMS could be entered to the system sometimes only with difficulty and delays may have occured during delivery. The Problem was solved.
Serious network disturbances occurred between 17:32 - 17:37 CET. This could result in SMS messages not being transmitted. Scheduled SMS previously entered to the system were delivered after the disturbance.
Serious network disturbances occurred between 18:31 - 18:37 CET. This could result in SMS messages not being transmitted. Scheduled SMS previously entered to the system were delivered after the disturbance.
During the night to 02.10.2017 CET, a malfunction in parts of the virtual ASPSMS infrastructure led to serious problems with SMSBLASTER web edition as well as with with putting SMS jobs into the system via xml1.aspsms.com and webservice.aspsms.com as well and to slight problems with the remaining interfaces. SMS with delayed delivery time which where received before the problem occured were not affected. The problem was fixed at 07:36 CET.
Serious network disturbances occurred between 14:30 - 14:34 CET. This could result in SMS messages not being transmitted.
In the time frame 17:50 - 18:20 CET there was a malfunction in parts of the physical and virtual ASPSMS infrastructure. This led to serious problems putting SMS jobs in the system via xml1.aspsms.com and webservice.aspsms.com as well as to slight problems with the remaining interfaces. SMS with delayed delivery time received before this period were not affected. The problem was fixed at 18:20 CET.
ASPSMS JSON API (https://json.aspsms.com/) and the ASPSMS SOAP web service (https://soap.aspsms.com/) were temporarily unavailable several times in the time window of 08:13 - 08:25 CET.
After a security update of the SMSBLASTER.COM web edition, contact import and Send log problems occurred between Friday 8th and Monday 11th September 2017. The problems have now been resolved.
The malfunction had no effect on the sending and delivery of the SMS.
However, for SMS sent and delivered during this period of time, the SMSBLASTER.COM web edition Send log shows the status Unknown regardless of the actual delivery status.
The actual delivery status of affected SMS messages can be viewed at https://www.aspsms.com/en/sendlog/ or by using the ASPSMS WinLog application.
Due to an malfunction in the infrastructure of the ASPSMS system it was possible that the sending of SMS was delayed between 15:07 - 15:17 CET. The problem was solved.|
Due to a malfunction in a subsystem of ASPSMS, sending SMS was partially slowed down. This could lead to timeouts for individual customers or customer systems. The problem was solved at 11:45 CET.|
Power outage in Eastern Switzerland: The large-scale power failure at 05:39 CET was successfully bridged by the ASPSMS system. However, due to an internal technical disturbance, which subsequently occurred in a subsystem, individual SMS messages were not processed correctly and therefore not sent. The problem could be fixed at 11:01 CET.|
Due to a malfunction in the ASPSMS system, problems with the delivery of SMS could occur from 10:10 - 10:16 CET.|
Due to a short-term malfunction of the XML interface, xml1.aspsms.com did not respond between 07:55 - 08:15 clock. The redundant interface xml2.aspsms.com worked perfectly. Customers with a ZaWin installation are recommended to restart it.|
Power Outage in St. Gallen|
On Wednesday morning there was a large power outage in St. Gallen. For this reason, the ASPSMS system was not available from 10:01 - 10:44 CET.
Between 11:35 and 11:55 CET, parts of the ASPSMS system were again affected and not reachable.