Cisco Secure Access has a global infrastructure with built in redundancy and failover routing designed to minimize any planned or unplanned outages.
Secure Access provides complete transparency so you can always see the current status of all the Secure Access cloud services.
* The China (Beijing) data center is operated by Digital China Cloud (DCC), a Cisco partner providing Secure Access services in mainland China for multinational customers. For more information about this datacenter click here.
| S.No | DC Location | Start (UTC) | End (UTC) | DC Details |
|---|---|---|---|---|
| 1 | Sydney | 2026-04-14, 14:00 | 2026-04-14, 18:00 | Australia (Sydney): ap-southeast-2_1_1 |
| 2 | Sao Paulo Canada Calgary Mexico | 2026-04-15, 02:00 | 2026-04-15, 06:00 | Brazil (Sao Paulo): sa-east-1_1_0 Canada (Central): ca-central-1_1_0 Canada (West): ca-west-1_1_0 LATAM (Mexico): mx-central-1_1_0 |
| 3 | Sydney Hong Kong Jakarta | 2026-04-15, 13:00 | 2026-04-15, 17:00 | Australia (Sydney): ap-southeast-2_1_0 Asia Pacific (Hong Kong): ap-east-1_1_0 Asia Pacific (Jakarta): ap-southeast-3_1_0 |
| 4 | Hyderabad | 2026-04-15, 16:00 | 2026-04-15, 20:00 | India (South): ap-south-2_1_0 |
| 5 | Tel Aviv Zurich Stockholm Milan Spain Cape Town Paris | 2026-04-15, 20:00 | 2026-04-16, 00:00 | Israel (Tel Aviv): il-central-1_1_0 Switzerland (Zurich): eu-central-2_1_0 Europe (Stockholm): eu-north-1_1_0 Europe (Milan): eu-south-1_1_0 Europe (Spain): eu-south-2_1_0 Africa (South Africa): af-south-1_1_0 Europe (France): eu-west-3_1_0 |
| 6 | Sao Paulo Canada Calgary Mexico | 2026-04-16, 02:00 | 2026-04-16, 06:00 | Brazil (Sao Paulo): sa-east-1_1_1 Canada (Central): ca-central-1_1_1 Canada (West): ca-west-1_1_1 LATAM (Mexico): mx-central-1_1_1 |
| 7 | Jakarta Hyderabad Hong Kong | 2026-04-16, 16:00 | 2026-04-16, 20:00 | Asia Pacific (Jakarta): ap-southeast-3_1_1 India (South): ap-south-2_1_1 Asia Pacific (Hong Kong): ap-east-1_1_1 |
| 8 | Tel Aviv Zurich Stockholm Milan Spain Cape Town Paris | 2026-04-16, 20:00 | 2026-04-17, 00:00 | Israel (Tel Aviv): il-central-1_1_1 Switzerland (Zurich): eu-central-2_1_1 Europe (Stockholm): eu-north-1_1_1 Europe (Milan): eu-south-1_1_1 Europe (Spain): eu-south-2_1_1 Africa (South Africa): af-south-1_1_1 Europe (France): eu-west-3_1_1 |
| 9 | Ohio N.Virginia Oregon Miami Los Angeles | 2026-04-22, 02:00 | 2026-04-22, 06:00 | US (Midwest): us-east-2_1_0 US (Virginia): us-east-1_1_0 US (Pacific Northwest): us-west-2_1_0 US (Virginia): csc-us-east-1_1_0 US (California): csc-us-west-1_1_0 |
| 10 | Mumbai | 2026-04-22, 16:00 | 2026-04-22, 20:00 | India (Mumbai): ap-south-1_1_0 India (Mumbai): csc-ap-south-1_1_0 |
| 11 | Tokyo Osaka Singapore | 2026-04-22, 16:00 | 2026-04-22, 19:00 | Asia Pacific (Tokyo): ap-northeast-1_1_0 Asia Pacific (Osaka): ap-northeast-3_1_0 Asia Pacific (Singapore): ap-southeast-1_1_0 Asia Pacific (Tokyo): csc-ap-northeast-1_1_0 |
| 12 | Frankfurt London Jeddah | 2026-04-22, 20:00 | 2026-04-23, 00:00 | Europe (Frankfurt): eu-central-1_1_0 UK (London): eu-west-2_1_0 Saudi Arabia (Jeddah): csc-me-central-2_1_0 |
| 13 | Ohio N.Virginia Oregon Reston San Jose | 2026-04-23, 02:00 | 2026-04-23, 06:00 | US (Midwest): us-east-2_1_1 US (Virginia): us-east-1_1_1 US (Pacific Northwest): us-west-2_1_1 US (Virginia): csc-us-east-1_1_1 US (California): csc-us-west-1_1_1 |
| 14 | Mumbai Chennai | 2026-04-23, 16:00 | 2026-04-23, 20:00 | India (South): ap-south-1_1_1 India (South): csc-ap-south-1_1_1 |
| 15 | Tokyo Osaka Singapore | 2026-04-23, 16:00 | 2026-04-23, 20:00 | Asia Pacific (Tokyo): ap-northeast-1_1_1 Asia Pacific (Osaka): ap-northeast-3_1_1 Asia Pacific (Singapore): ap-southeast-1_1_1 Asia Pacific (Osaka): csc-ap-northeast-1_1_1 |
| 16 | Frankfurt London Riyadh | 2026-04-23, 20:00 | 2026-04-24, 00:00 | Europe (Frankfurt): eu-central-1_1_1 UK (London): eu-west-2_1_1 Saudi Arabia (Riyadh): csc-me-central-2_1_2 |