Connection Issue - Not able to connect to easylink service

thiyagu.ceg

We are getting the below error continously today while trying to get the status of the email jobs using the below url , Kindly let us know what could have gone wrong, the delivery status process was working successfully for last couple of years.

https://messaging.easylink.com/soap/sync

User Id : MET/MR/EPT

Error :

faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException

 faultString: WSWS3713E: Connection to the remote host messaging.easylink.com failed.Received the following error: null

 faultActor: null

 faultDetail:

 

WSWS3713E: Connection to the remote host messaging.easylink.com failed.Received the following error: null

                at com.ibm.ws.webservices.engine.transport.http.HttpOutboundChannelConnection.connect(HttpOutboundChannelConnection.java:786)

                at com.ibm.ws.webservices.engine.transport.http.HttpsOutboundChannelConnection.connect(HttpsOutboundChannelConnection.java:210)

                at com.ibm.ws.webservices.engine.transport.http.HTTPSender.invoke(HTTPSender.java:528)

                at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:227)

                at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:227)

                at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:227)

                at com.ibm.ws.webservices.engine.WebServicesEngine.invoke(WebServicesEngine.java:336)

                at com.ibm.ws.webservices.engine.client.Connection.invokeEngine(Connection.java:783)

                at com.ibm.ws.webservices.engine.client.Connection.invoke(Connection.java:660)

                at com.ibm.ws.webservices.engine.client.Connection.invoke(Connection.java:618)

                at com.ibm.ws.webservices.engine.client.Connection.invoke(Connection.java:453)

                at com.ibm.ws.webservices.engine.client.Stub$Invoke.invoke(Stub.java:947)

 

thuneke

That is still the correct URL. If you click on the URL you should get a page stating you have reached the API URL. If you don't you should to see if anything changed on your side to block the URL.