Is IBM Aspera San Jose (sjc) down?
Current IBM Aspera San Jose (sjc) status is UP

We checked the official IBM Aspera San Jose (sjc) Status Page 3 min. 33 sec. ago. Learn more
Having a problem? Help Allie Gator keep this page accurate!

Report an Issue

Stay informed of future downtime with dashboards and notifications

Recent IBM Aspera San Jose (sjc) Outages and Issues

Follow the recent outages and downtime for IBM Aspera San Jose (sjc) in the table below.

Start Time

Type

Length

Message

Details

March 09, 2024 17:04 UTC

MAINT

about 4 hours

[AoC:API] Maintenance Notice

See more
Start Time

March 09, 2024 17:04 UTC

Type MAINT
Affected Components

Amazon Transfer Clusters - Oregon (us-west-2)

AoC Managed Storage - Amsterdam (ams)

AoC Managed Storage - Dallas (dal)

AoC Managed Storage - Frankfurt (fra)

IBM Cloud Transfer Clusters - San Jose (sjc)

IBM Cloud Transfer Clusters - Sao Paulo (sao)

IBM Cloud Transfer Clusters - Sydney (syd)

IBM Cloud Transfer Clusters - Tokyo (tok)

IBM Cloud Transfer Clusters - Toronto (tor)

IBM Cloud Transfer Clusters - Washington D.C. (wdc)

IBM Cloud Transfer Clusters - Osaka (osa)

Azure Transfer Clusters - Central United States (ats-azure-centralus)

Azure Transfer Clusters - East United States (ats-azure-eastus)

Azure Transfer Clusters - North Europe (ats-azure-northeurope)

Azure Transfer Clusters - West United States (ats-azure-westus)

Google Transfer Clusters - United States Central 1 (us-central1)

Google Transfer Clusters - London (europe-west2)

Google Transfer Clusters - Los Angeles (us-west2)

IBM Cloud Transfer Clusters - Dallas (dal)

IBM Cloud Transfer Clusters - Frankfurt (fra)

IBM Cloud Transfer Clusters - Milan (mil)

Azure Transfer Clusters - West Europe (westeurope)

IBM-Aspera API Services - api.ibmaspera.com

AoC Managed Storage - Toronto (tor)

Amazon Transfer Clusters - Frankfurt (eu-central-1)

Amazon Transfer Clusters - Ireland (eu-west-1)

Amazon Transfer Clusters - São Paulo (sa-east-1)

Amazon Transfer Clusters - Singapore (ap-southeast-1)

Amazon Transfer Clusters - Sydney (ap-southeast-2)

Amazon Transfer Clusters - Tokyo (ap-northeast-1)

Amazon Transfer Clusters - London (eu-west-2)

Amazon Transfer Clusters - N. California (us-west-1)

IBM Cloud Transfer Clusters - Amsterdam (ams)

IBM Cloud Transfer Clusters - London (lon)

Azure Transfer Clusters - London (ats-azure-uksouth)

Azure Transfer Clusters - South East Asia (azure-southeastasia)

AoC Managed Storage - Sydney (syd)

Amazon Transfer Clusters - Virgina (us-east-1)

Message

[AoC:API] Maintenance Notice

Details

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar 09, 2024 - 09:00 PST

February 24, 2024 17:04 UTC

MAINT

about 8 hours

[AoC:API] - Monthly Maintenance Notice

See more
Start Time

February 24, 2024 17:04 UTC

Type MAINT
Affected Components

IBM-Aspera API Services - Frontend

Google Transfer Clusters - London (europe-west2)

Google Transfer Clusters - Los Angeles (us-west2)

IBM Cloud Transfer Clusters - Milan (mil)

Azure Transfer Clusters - West United States (ats-azure-westus)

Azure Transfer Clusters - Central United States (ats-azure-centralus)

IBM-Aspera API Services - platform.bss.asperasoft.com

AoC Managed Storage - Amsterdam (ams)

AoC Managed Storage - Dallas (dal)

AoC Managed Storage - Frankfurt (fra)

AoC Managed Storage - Toronto (tor)

AoC Managed Storage - Sydney (syd)

Amazon Transfer Clusters - Frankfurt (eu-central-1)

Amazon Transfer Clusters - Ireland (eu-west-1)

Amazon Transfer Clusters - Oregon (us-west-2)

Amazon Transfer Clusters - São Paulo (sa-east-1)

Amazon Transfer Clusters - Singapore (ap-southeast-1)

Amazon Transfer Clusters - Sydney (ap-southeast-2)

Amazon Transfer Clusters - Tokyo (ap-northeast-1)

Amazon Transfer Clusters - Virgina (us-east-1)

Amazon Transfer Clusters - London (eu-west-2)

Amazon Transfer Clusters - N. California (us-west-1)

IBM Cloud Transfer Clusters - Amsterdam (ams)

IBM Cloud Transfer Clusters - Dallas (dal)

IBM Cloud Transfer Clusters - Frankfurt (fra)

IBM Cloud Transfer Clusters - London (lon)

IBM Cloud Transfer Clusters - San Jose (sjc)

IBM Cloud Transfer Clusters - Sao Paulo (sao)

IBM Cloud Transfer Clusters - Sydney (syd)

IBM Cloud Transfer Clusters - Tokyo (tok)

IBM Cloud Transfer Clusters - Toronto (tor)

IBM Cloud Transfer Clusters - Washington D.C. (wdc)

IBM Cloud Transfer Clusters - Osaka (osa)

Azure Transfer Clusters - East United States (ats-azure-eastus)

Azure Transfer Clusters - North Europe (ats-azure-northeurope)

Azure Transfer Clusters - West Europe (westeurope)

Azure Transfer Clusters - South East Asia (azure-southeastasia)

Azure Transfer Clusters - London (ats-azure-uksouth)

Google Transfer Clusters - United States Central 1 (us-central1)

IBM-Aspera API Services - api.ibmaspera.com

IBM-Aspera API Services - ats.aspera.io

Message

[AoC:API] - Monthly Maintenance Notice

Details

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb 24, 2024 - 09:00 PST

February 04, 2024 22:34 UTC

MAINT

30 minutes

[AWS,IBM Cloud,Azure,Google] - Emergency maintenance notice

See more
Start Time

February 04, 2024 22:34 UTC

Type MAINT
Affected Components

IBM Cloud Transfer Clusters - Tokyo (tok)

IBM Cloud Transfer Clusters - Dallas (dal)

IBM Cloud Transfer Clusters - Frankfurt (fra)

IBM Cloud Transfer Clusters - Milan (mil)

Azure Transfer Clusters - West United States (ats-azure-westus)

Azure Transfer Clusters - South East Asia (azure-southeastasia)

Azure Transfer Clusters - London (ats-azure-uksouth)

Google Transfer Clusters - United States Central 1 (us-central1)

Google Transfer Clusters - London (europe-west2)

Amazon Transfer Clusters - Frankfurt (eu-central-1)

Amazon Transfer Clusters - Ireland (eu-west-1)

Amazon Transfer Clusters - Oregon (us-west-2)

Amazon Transfer Clusters - São Paulo (sa-east-1)

Amazon Transfer Clusters - Singapore (ap-southeast-1)

Amazon Transfer Clusters - Sydney (ap-southeast-2)

Amazon Transfer Clusters - Tokyo (ap-northeast-1)

Amazon Transfer Clusters - Virgina (us-east-1)

Amazon Transfer Clusters - London (eu-west-2)

Amazon Transfer Clusters - N. California (us-west-1)

IBM Cloud Transfer Clusters - Amsterdam (ams)

IBM Cloud Transfer Clusters - London (lon)

IBM Cloud Transfer Clusters - San Jose (sjc)

IBM Cloud Transfer Clusters - Sao Paulo (sao)

IBM Cloud Transfer Clusters - Sydney (syd)

IBM Cloud Transfer Clusters - Toronto (tor)

IBM Cloud Transfer Clusters - Washington D.C. (wdc)

IBM Cloud Transfer Clusters - Osaka (osa)

Azure Transfer Clusters - West Europe (westeurope)

Google Transfer Clusters - Los Angeles (us-west2)

Azure Transfer Clusters - Central United States (ats-azure-centralus)

Azure Transfer Clusters - East United States (ats-azure-eastus)

Azure Transfer Clusters - North Europe (ats-azure-northeurope)

Message

[AWS,IBM Cloud,Azure,Google] - Emergency maintenance notice

Details

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb 04, 2024 - 14:30 PST

January 31, 2024 00:59 UTC

WARN

about 7 hours

[IBM-Aspera] - [IBM: ALL] - Service Disruption - Transfers not entering into a "complete" state.

See more
Start Time

January 31, 2024 00:59 UTC

Type WARN
Affected Components

IBM Cloud Transfer Clusters - Toronto (tor)

IBM Cloud Transfer Clusters - Amsterdam (ams)

IBM Cloud Transfer Clusters - Dallas (dal)

IBM Cloud Transfer Clusters - Frankfurt (fra)

IBM Cloud Transfer Clusters - London (lon)

IBM Cloud Transfer Clusters - Milan (mil)

IBM Cloud Transfer Clusters - San Jose (sjc)

IBM Cloud Transfer Clusters - Sao Paulo (sao)

IBM Cloud Transfer Clusters - Sydney (syd)

IBM Cloud Transfer Clusters - Tokyo (tok)

IBM Cloud Transfer Clusters - Washington D.C. (wdc)

IBM Cloud Transfer Clusters - Osaka (osa)

Message

[IBM-Aspera] - [IBM: ALL] - Service Disruption - Transfers not entering into a "complete" state.

Details

Investigating - We have identified an issue specific to our IBM Cloud transfer clusters. Customers may be experiencing an issue where transfers don't enter into a "complete" state, even though the transfer has finished. We are actively working on remediating the issue. Jan 30, 2024 - 16:56 PST

January 29, 2024 10:34 UTC

DOWN

about 8 hours

[IBM Cloud:AMS,SJC] - Service Disruption

See more
Start Time

January 29, 2024 10:34 UTC

Type DOWN
Affected Components

IBM Cloud Transfer Clusters - Amsterdam (ams)

IBM Cloud Transfer Clusters - San Jose (sjc)

Message

[IBM Cloud:AMS,SJC] - Service Disruption

Details

Investigating - We have been alerted to a service disruption affecting: ATS IBM Cloud cluster Amsterdam and Sane Jose. Our engineers are currently investigating the incident and will provide updates when more information is available. Jan 29, 2024 - 02:32 PST

2024-04-16 12:24:05 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-16 12:24:05 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-16 12:24:05 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-16 12:24:05 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-16 12:24:05 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

Sign Up for More IBM Aspera San Jose (sjc) History

StatusGator has almost 4 years of IBM Aspera San Jose (sjc) status history.

No outages or status changes in the last 24 hours

IBM Aspera San Jose (sjc) status, last 24 hours:

1:00 PM
7:00 PM
1:00 AM
7:00 AM
1:00 PM
1:00 PM
1:00 AM
1:00 PM
  • Up: 24 hours

  • Warn: 0 minutes

  • Down: 0 minutes

  • Maintenance: 0 minutes

IBM Aspera San Jose (sjc) Outage and Status History

We've been monitoring IBM Aspera San Jose (sjc) outages since June 9, 2020.
Here's the history of service outages we've observed from the IBM Aspera San Jose (sjc) Status Page:

  • Up

  • Warn

  • Down

  • Maintenance

Instant enriched data from
3,570 status pages

About Our IBM Aspera San Jose (sjc) Status Page Integration

IBM Aspera San Jose (sjc) is a Cloud Infrastructure solution that StatusGator has been monitoring since June 2020. Over the past almost 4 years, we have collected data on on more than 1,750 outages that affected IBM Aspera San Jose (sjc) users. When IBM Aspera San Jose (sjc) publishes downtime on their status page, they do so across 41 components and 6 groups using 4 different statuses: up, warn, down, and maintenance which we use to provide granular uptime metrics and notifications.

Many StatusGator users monitor IBM Aspera San Jose (sjc) to get notified when it's down, is under maintenance, or has an outage. We've sent more than 1,200 notifications to our users about IBM Aspera San Jose (sjc) incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.

If IBM Aspera San Jose (sjc) is having system outages or experiencing other critical issues, red down notifications appear on the status page. In most cases, it means that core functions are not working properly, or there is some other serious customer-impacting event underway.

Warn notifications are used when IBM Aspera San Jose (sjc) is undergoing a non-critical issue like minor service issues, performance degradation, non-core bugs, capacity issues, or problems affecting a small number of users.

IBM Aspera San Jose (sjc) posts separate notifications for planned maintenance work. StatusGator will notify subscribers when IBM Aspera San Jose (sjc) enters a pre-planned maintenance window, keeping you up to date.

Since IBM Aspera San Jose (sjc) publishes a feed of proactive maintenance events on their status page, StatusGator will collect information about these events. Maintenance events for all your services can be viewed within StatusGator as a unified feed.

When IBM Aspera San Jose (sjc) posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.

When IBM Aspera San Jose (sjc) has outages or other service-impacting events on their status page, we pull down the detailed informational updates and include them in notifications. These messages often include the current details about how the problem is being mitigated, or when the next update will occur.

Because IBM Aspera San Jose (sjc) has several components, each with their individual statuses, StatusGator can differentiate the status of each component in our notifications to you. This means, you can filter your status page notifications based on the services, regions, or components you utilize. This is an essential feature for complex services with many components or services spread out across many regions.

Frequently Asked Questions

Can’t find your question? Email us to arrange a time to discuss. We’d love to chat!

IBM Aspera San Jose (sjc) Down?

Are you experiencing issues with IBM Aspera San Jose (sjc)? Sign up to receive notifications when IBM Aspera San Jose (sjc) publishes outages.

IBM Aspera San Jose (sjc) Down or not working? Never be taken by surprise again.

StatusGator tells you when your cloud services have problems or their statuses change. We monitor the official status pages of more than 3,570 cloud services in real-time, aggregate the data, and send you alerts via email, Slack, Teams, SMS, and more.

Looking for recent downtime and outages of IBM Aspera San Jose (sjc)?

Sign up for StatusGator and see all historical information about IBM Aspera San Jose (sjc) outages and performance issues. Get free, instant notifications when IBM Aspera San Jose (sjc) goes down.