All systems are functioning normally today10 February 2012 07:53 GMT
Operational status
This page gives real-time information on the status of SWIFT's systems and messaging services, as well as information on recovery plans during outages. It also gives the planning of the scheduled network downtime and of weekends during which SWIFT performs business continuity tests. You can subscribe to receive by e-mail the updates of the operational status or use our RSS feed
to be notified of the maintenance of our services.
Current status
SWIFT's systems and services are offered 24 hours a day, seven days a week. See our availability statistics below:
| Availability by service |
|
|
Dec 2011
|
YTD
|
|
FIN Core Global
|
99.999%
|
99.999%
|
|
SWIFTNet Core Global
|
99.999%
|
99.999%
|
|
- This table shows the availability percentages of the FIN and SWIFTNet core services, as well as the year-to-date (YTD) percentages. These statistics are produced on a monthly basis.
View the monthly report for 2011 here.
|
| Availability by service in European zone |
|
|
Dec 2011
|
YTD
|
|
FIN Core EU
|
99.999%
|
99.999%
|
|
SWIFTNet Core EU
|
99.999%
|
99.999%
|
|
| Availability by service in Trans-Atlantic zone |
|
|
Dec 2011
|
YTD
|
|
FIN Core TA
|
99.999%
|
99.998%
|
|
SWIFTNet Core TA
|
99.999%
|
99.998%
|
|
| Dual-P availability by number of providers (YTD 4Q2011)
|
|
Dual Providers?
|
Dual-P connections
|
Downtime Minutes
|
Availability
|
|
No
|
316
|
13,809.32
|
99.9913%
|
|
Yes
|
382
|
8,371.22
|
99.9956%
|
| Total |
698
|
22,180.53
|
99.9936%
|
|
- This table represents the connection ability of the customers having a Dual-P connection. It shows the downtimes and the availability percentage for customers that have a single network provider (Dual Provider=No), and for customers that have two network providers (Dual Providers=Yes). These statistics are produced on a quarterly basis.
|
Planned maintenance on the SWIFTNet Integration Testbed
SWIFT organises planned maintenance on the SWIFTNet Integration Testbed (ITB) environment every Friday, from 12:00 GMT to Saturday 08:00 GMT.
Please note that starting on Wednesday 25 August 2010, SWIFT will run a series of system recovery simulations of the store-and-forward system on the ITB environment. These simulations allow messaging interface providers validate their software for correct implementation after a store-and-forward system recovery. To allow vendors run these tests, SWIFT will bring the store-and-forward system down at specific days and time. Click to see the downtime schedule.
Planned maintenance of the Alliance Lite service 
SWIFT organises planned maintenance of the Alliance Lite service every weekend. The maintenance begins on Saturday at 05:00 GMT and lasts until Sunday 17:00 GMT. During this period, the Alliance Lite service may be unavailable for the whole duration of the planned downtime, or only intermittently.
SWIFT organises planned maintenance of the Alliance Lite Test service every Tuesday between 12:00 GMT and 17:00 GMT, and every weekend from Saturday 05:00 GMT until Sunday 17:00 GMT. During this period, the Alliance Lite Test service may be unavailable for the whole duration of the planned downtime, or only intermittently.
Planned maintenance on swift.com 
Due to the deployment of WCMS 3.17, the ISO 20022 website will be unavailable on Thursday 12 January between 11:00 and 13:00 GMT. A maintenance page will be displayed during this time period.
Planned maintenance of the SWIFTNet messaging services
SWIFT organises planned maintenance, and business continuity testing, which occur during Allowable Downtime Windows (ADW). These maintenance windows and test windows begin on Saturday at 16:00 GMT. During the maintenance windows, the SWIFTNet messaging services (FIN, InterAct, FileAct and Browse) are subject to interruption as described below:
- Maintenance window: during these periods, which can last for 2, 8 or 12 hours, the SWIFTNet messaging services may experience intermittent periods of connectivity loss or of service interruption. Exceptionally, longer periods of service disruption may occur within the window.
- Business continuity testing, and cold start testing: during these tests, which can last for 12 hours, the SWIFTNet messaging services are subject to short interruptions. Extended interruptions may occur for the duration of the window.
Please consult the table below for the exact start times and end times of the ADWs.
java.lang.RuntimeException: Execution exception in com.interwoven.livesite.external.ExternalCall@11dcabf[object=com.swift.wcms.utils.operationalStatus,method=public org.dom4j.Document getAWDs(com.interwoven.livesite.runtime.RequestContext,),scope=local,parameters={},prefixCalls=[]]
at com.interwoven.livesite.common.pojo.PojoMethodCall.execute(PojoMethodCall.java:465)
at com.interwoven.livesite.external.ExternalCall.execute(ExternalCall.java:136)
at com.interwoven.livesite.runtime.model.component.Component.executeExternal(Component.java:369)
at com.interwoven.livesite.runtime.model.page.RuntimeComponent.transform(RuntimeComponent.java:222)
at com.interwoven.livesite.runtime.page.PageTokenComponent.preRender(PageTokenComponent.java:141)
at com.interwoven.livesite.runtime.page.PageTokenContainer.preRender(PageTokenContainer.java:331)
at com.interwoven.livesite.runtime.model.page.RuntimePage.transformAndOutput(RuntimePage.java:407)
at com.interwoven.livesite.runtime.model.page.RuntimePage.transformAndOutput(RuntimePage.java:388)
at com.interwoven.livesite.runtime.rendering.RenderingManager.doOutputPage(RenderingManager.java:1193)
at com.interwoven.livesite.runtime.rendering.RenderingManager.doOutput(RenderingManager.java:1136)
at com.interwoven.livesite.runtime.rendering.RenderingManager.doSetupRenderingObjects(RenderingManager.java:548)
at com.interwoven.livesite.runtime.rendering.RenderingManager.renderPageGoal(RenderingManager.java:295)
at com.interwoven.livesite.runtime.rendering.RenderingManager.render(RenderingManager.java:224)
at com.interwoven.livesite.runtime.impl.BaseRequestContext.render(BaseRequestContext.java:201)
at com.interwoven.livesite.runtime.filter.LiveSiteFilter.doFilter(LiveSiteFilter.java:111)
at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:183)
at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:138)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:535)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:675)
at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:637)
Caused by: java.lang.RuntimeException: Could not invoke method: getAWDs, reason: null
at com.interwoven.livesite.common.util.ClassUtils.executeMethod(ClassUtils.java:117)
at com.interwoven.livesite.common.pojo.PojoMethodCall.executeMethod(PojoMethodCall.java:406)
at com.interwoven.livesite.common.pojo.PojoMethodCall.execute(PojoMethodCall.java:460)
... 44 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor85.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.interwoven.livesite.common.util.ClassUtils.executeMethod(ClassUtils.java:109)
... 46 more
Caused by: java.lang.NullPointerException