System Status

Service Degradation - Alltel USA

Date reported: 2010-03-12 16:00:00 GMT
This issue was resolved on: 2010-03-12 12:30 EST

Since 11:00 EST on 2010-03-12, MX Telecom have been experiencing a connectivity issue with Alltel USA.

Delivery reports for premium MT SMS sent to Alltel USA users are currently being delayed. Delivery of premium MTs is not affected.

MO and standard rate MT SMS traffic is unaffected.

Engineers are aware of the issue and are working to resolve it as quickly as possible. There is no estimated time to resolution at the moment.

* RESOLVED: 2010-03-12 12:30 EST
We are now receiving delivery reports for premium MT messages sent to Alltel users.

MX Telecom SMS Gateway Partner Notification

Date reported: 2010-03-10 12:35:00 GMT
There is no projected resolution date

This is a courtesy notification to partners using the SMS ID functionality of the MX Telecom SMS Gateway.

As of 09:00 GMT on Wednesday, 7th April 2010, the MX Telecom SMS Gateway will generate SMS IDs greater than the maximum number that can be stored in a 32 bit value (4,294,967,295). We recommend that partners who use the SMS Gateway APIs check that their platforms will handle SMS ID values of this size correctly. This will ensure that their services continue to function as expected.

An SMS ID is a positive 64 bit integer used to uniquely identify an SMS message as it passes through the SMS Gateway. Partners receive an SMS ID from the SMS Gateway when:

1. a Mobile Terminated (MT) SMS message is successfully submitted to the SMS Gateway - the SMS Gateway includes the SMS ID for the message in the request response. Partners using the SMPP interface to the SMS Gateway should be aware that the hexadecimal SMS ID returned in the body of SUBMIT_SM_RESP PDUs will increase from 8 to 9 characters in length.

2. the SMS Gateway passes a delivery report back to a partner’s platform for an MT SMS message. This SMS ID will match the ID in the response sent by the SMS Gateway when it originally received the MT SMS message request.

3. the SMS Gateway passes a Mobile Originated SMS message onto a partner’s platform.

Please refer to the relevant API documentation for specific details of the parameters used.

There is no change to the behaviour of MX Telecom's hosted applications such as CMX2.

Should you have any queries, please contact your Account Manager or the MX Telecom Support team.

Planned Maintenance - Three UK

Date reported: 2010-03-14 23:30:00 GMT
Projected date of resolution: 2010-03-15 07:00:00 GMT

Three UK have informed us of planned maintenance work to their SMS platform between 2010-03-14 23:30 - 2010-03-15 07:00 GMT.

During this period premium MT SMS sent to Three UK subscribers may be delayed.

In the event of an outage, MT messages sent to Three subscribers will be queued on the MX Telecom SMS gateway for delivery once maintenance has been completed.

Bulk MT and MO SMS traffic will be unaffected.

Planned Maintenance - Three UK PayForIt

Date reported: 2010-03-14 23:30:00 GMT
Projected date of resolution: 2010-03-15 07:00:00 GMT

Three UK have informed us of planned maintenance to their PayForIt billing platform from 2010-03-14 23:30 - 2010-03-15 07:00 GMT. This may impact PayForIt charges made via the MX Telecom Charge To Account Gateway for Three UK subscribers.

During this maintenance the MX Telecom Charge To Account Gateway may be impacted as follows:

a) It may not be possible to make one off charges via Payforit for users on the Three network.

b) It may not be possible to initiate subscription services for all Three users where a 'free period' has not been specified.

c) Scheduled charges for existing Three subscriptions may fail during this period, though charges will be retried by MX Telecom automatically once normal service resumes.

Service degradation - AT&T USA PSMS subscriptions

Date reported: 2010-02-17 05:00:00 GMT
There is no projected resolution date

We have identified an issue affecting some Premium SMS subscriptions on AT&T USA. It appears that, starting on 2010-02-17, some subscriptions are being concluded by AT&T, but AT&T are not sending out notifications to aggregators to this effect. The effect of this is that partners may see fewer subscription renewals than they might otherwise expect.

We believe that only a very small minority of subscriptions are affected, however it appears to be an ongoing issue. We also believe that the subscriptions are being concluded for normal reasons (such as a prepay user out of credit or the user calling Customer Services), so no loss of revenue is expected as a result of this problem.

We are working actively with AT&T to resolve this issue, however there is currently no estimated time to resolution.